Skip to content

Power BI · Enterprise reporting · Requirements

I make careful changes to reports people rely on every day.

Business Data Analyst and Computer Science co-op student. I work inside an enterprise Microsoft Fabric and Power BI environment, taking reporting requests from investigation through implementation, validation, and QA, to deploying the approved change to production.

Open to BI, data analyst, and technical BA internships, co-ops, and entry-level opportunities

Vaughan, Ontario

Validation check

Source vs. report

3 of 4 matched
MetricSourceReport
Distinct agents412412Matched
Offered8,9408,940Matched
Answered8,6128,612Matched
Avg handle4m 32s4m 51sInvestigating

Illustrative — synthetic values. Average handle time differs between source and report; investigating filter context.

report enterprise BI suite
27report enterprise BI suite
records automated weekly
14,000+records automated weekly
surveys inventoried
188surveys inventoried
ServiceNow BA bridge
3 orgsServiceNow BA bridge

About

I like inheriting systems I didn't build.

Most of my Power BI work hasn't started with a blank canvas. It started with a report that already existed, already had users, and already had decisions baked into it — aggregation levels, filter defaults, grading rules, metric definitions that someone chose for a reason. Before I change anything, I want to know what those reasons were.

That's usually where the interesting part is. The one-sentence requests — “add a distinct count of agents” — are the ones that turn out to have a real question hiding inside them.

My Computer Science background shows up less in writing code than in how I read systems — following a value from a source table through a semantic model into a visual, and staying sceptical of a number until I've seen where it came from. The other half of the job is the opposite skill: most requests arrive as one sentence, and turning that sentence into defined behaviour — in a report, or in a requirements list — is where most of the work actually is.

  • Enterprise Power BI

    Report enhancements built, tested, and deployed to production

  • Validation

    Checking outputs against source data before anything ships

  • Requirements

    Discovery and stakeholder work across the organization

  • Computer Science

    Specialized Honours Co-op at York University

Selected work

Selected work

All examples are anonymized. No proprietary data, internal system names, or confidential figures are included. Visuals are recreated using synthetic data.

Queue

Offered

Answered

Forecast

Variance

+ measures added at report level

Enterprise Power BI · Sustainment & Enhancement

Enhancing an Enterprise Contact-Centre Reporting Suite

Stakeholders raised reporting changes as tickets; I worked out what each one actually required inside an existing report, wrote or modified the DAX behind it, tested the result, and deployed reviewed changes from non-production to production. The suite covered queue performance, daily operations, IVR, and monthly agent and team scorecards used to run a contact centre.

27-report suite · 8–9 reports worked in · 6 delivered, 4 detailed

  • Power BI
  • DAX
  • Microsoft Fabric
  • Deployment Pipelines
  • QA Support
  • Jira

Read case study

Survey inventory

188

  • Active
  • Archived
  • Draft

Categories shown without figures

Business Analysis · Requirements

Discovery for an Enterprise Survey Platform Migration

Before a replacement platform can be chosen, someone has to establish what's on the current one and what each team actually needs. I built the survey inventory, ran outreach across the organization, and gathered and consolidated requirements — surfacing a gap between what different groups need that shapes the whole decision.

188 surveys inventoried across the organization

  • Requirements Gathering
  • Stakeholder Analysis
  • Inventory & Retention
  • Process Documentation

Read case study

14,000+ records

Weekly raw feed

VBA automation

Sort and enrich

CMDB lookup

Ownership mapping

Structured output

Actionable tracker

Manual → automated

Automation · Data Operations

Cybersecurity Vulnerability Triage Automation

Every week, 14,000–16,000 vulnerability records had to be enriched with system ownership and assigned to the right remediation owner before a Tuesday review. I mapped the manual process, automated the mechanical parts with Excel VBA and reference lookups, and built a tiered assignment path so only the genuinely ambiguous records needed a person.

14,000–16,000 records weekly · Monday-to-Tuesday turnaround

  • Excel VBA
  • Process Automation
  • CMDB Lookup
  • Data Processing

Read case study

Electric · 2026

Sample Vehicle

Compare

Range

512 km

0–100

3.8s

Drive

AWD

Illustrative — synthetic vehicle

Product Design · Frontend · Quality Assurance

ApexAuto — Electric Vehicle Marketplace

A full-stack e-commerce application for browsing, comparing, financing, and purchasing electric vehicles, built by a four-person team. I established the visual direction and prototype, implemented selected frontend pages, and tested user journeys to find functional and usability defects.

4-person team · Original UI direction · React frontend · Live demo

  • UI/UX Design
  • React
  • TypeScript
  • Prototyping
  • Functional Testing
  • Spring Boot

Read case study

Experience

Where I've worked

  1. Hydro One

    Current role

    Business Data Analyst Co-op

    May 2025 – Present · Markham, ON

    • Delivered six enhancements to an enterprise Power BI reporting suite, working directly in eight to nine of its 27 operational and performance reports
    • Authored and modified DAX measures at the report level, and configured visuals against measures already present in the shared semantic model
    • Built and tested changes in a non-production Fabric workspace, supported QA cycles with testers, and deployed reviewed changes to production through the deployment pipeline
    • Led the discovery work for an enterprise survey platform migration: a 188-survey inventory, stakeholder outreach across the organization, and consolidated requirements documentation
    • Served as business analysis bridge between Hydro One and an external vendor on a ServiceNow integration, supporting cross-organizational requirements alignment across three organizations
    • Automated weekly triage of 14,000–16,000 cybersecurity vulnerabilities using Excel VBA and CMDB enrichment, assigning solution owners and maintaining the tracker
    • Maintained a monthly small-projects financial tracker by ingesting and reconciling SAP actuals, documenting the process for handover
    • Configured contact-centre speech and text analytics topics and phrase libraries, and produced monthly application performance reporting for senior stakeholders
  2. Me Va Me

    Customer Service Associate

    January 2022 – August 2022 · Maple, ON

    Customer-facing operations work in a high-volume environment: handling transactions, coordinating driver scheduling, and resolving issues in real time. Early practice at the part of analyst work that isn't technical — reading what someone actually needs from an incomplete request, and staying accurate under time pressure.

Education

Academic background

Lassonde School of Engineering

York University

Bachelor of Science

Specialized Honours Computer Science Co-op

2022 – 2027

Selected coursework

  • Introduction to Database Systems
  • Applied Linear Algebra
  • Elementary Probability
  • Design & Analysis of Algorithms
  • Software Design
  • User Interfaces

In progress

  • Big Data Systems
  • Database Management Systems
  • Building E-Commerce Systems
  • Advanced Data Structures
  • Human-Computer Interaction

Recognition

  • Best UI/UX Award - CS Hub Local Hack Day
  • York University Entrance Scholarship
  • Lassonde Entrance Scholarship

How I work

Three things I hold to

  1. Learn the report before changing it.

    I read how a report already behaves — its aggregation levels, filter context, and existing measures — before adding anything. Most of the risk in a small change lives in what it quietly touches.

  2. A number isn't finished until it reconciles.

    I check new measures against source data and against what the result is supposed to be before I call something done. If I can't explain where a figure came from, it isn't ready for someone to make a decision from it.

  3. Design for the person opening it Monday morning.

    A filter that technically works but confuses a manager at 8am isn't done. Given the choice between the clever implementation and the obvious one, I'll take obvious — including when that means more work.

Skills

Tools and capabilities

  • Reporting & data

    • Power BI
    • DAX
    • SQL
    • Excel
    • Microsoft Fabric
  • Analysis & delivery

    • Requirements
    • Data validation
    • Process analysis
    • QA / UAT
    • Jira
  • Development & automation

    • Python
    • Excel VBA
    • React
    • TypeScript

Enterprise environments

Worked within; platforms maintained by others

  • Genesys Cloud
  • ServiceNow
  • SAP
  • Dynatrace
  • Microsoft Entra ID

Languages

  • English
  • Hebrew
  • Russian

Get in touch

Let's talk about reporting that needs to be right.

I'm looking for roles in business intelligence, data analysis, and technical business analysis — particularly on reporting that people depend on operationally.