About The Reporting HubThe Reporting Hub is an intelligence orchestration platform built on Power BI. Power BI produces the analytics, and BI Genius, our AI engine, produces governed AI insights from Power BI semantic models. The Reporting Hub governs both and delivers them to audiences outside our customers' organizations, under the customer's brand and inside their own Azure tenant.

SaaS companies use it to turn their analytics into a product their customers pay for. Consulting firms use it to give each client its own branded platform. Regulated enterprises use it for external reporting with role-based access, audit trails, and no data leaving their tenant.

The Reporting Hub runs in more than 30 countries with over 300,000 active users, and Microsoft recommends it as a Power BI Embedded solution accelerator. We've grown without investors: we're bootstrapped and have been cash-flow positive since day one. That lets us grow responsibly instead of hiring fast to hit a valuation and laying people off later. Our headquarters is in Calgary, Alberta, and our team works from across North America, Europe, Asia, and Australia.

About the roleThe Reporting Hub is hiring a junior developer to split their time between customer support and engineering.

About half your week goes to support: you're the first technical contact for customer tickets, you solve what you can, and you escalate the rest to senior developers with a clear diagnosis. The expectation is you’ll work to automate this so it takes less and less of your week. The rest of your time goes to fixing bugs and building smaller features in The Reporting Hub, our Power BI Embedded portal, and BI Genius, our AI analytics product.

You'll join a small engineering team. Senior developers review your code, take your escalations, and help you grow. Support is how you'll learn the product fastest: every ticket shows you how customers really use it and where it breaks.

We work with AI coding agents every day, and we want someone who does too. You'll use them to investigate tickets, read unfamiliar code, and write fixes, and you'll check what they produce before it reaches a customer or a pull request.

Location: Remote

Working hours: At least 2–3 hours of overlap with Mountain Time (UTC−7) on workdays. A time zone outside North America is a plus as it extends our support coverage.

Type: You start full-time on contract.

What you'll do





- Be the first technical contact for customer support tickets. Most of this is in writing, with calls when a problem needs one.
- Diagnose issues across Power BI Embedded, Azure, and identity setups (Microsoft Entra ID, Okta, Auth0), often inside the customer's own Azure environment.
- Reproduce bugs, and escalate what you can't solve with a clear write-up: what's wrong, what you've ruled out, and what you think could be the cause.
- Fix bugs and build smaller features in our C# back end and HTML/JavaScript front end, with code review from senior developers.
- Turn recurring tickets into fixes, help articles, or improvements to our AI support agent.
- Follow our practices for secure development, change management, and customer data handling.

How you'll work with AIOur team builds with Claude Code and other tools every day. In this role you will:
- Investigate with AI. Use agents to read logs, search the codebase, and narrow down a customer's problem quickly.
- Check before you send. Verify what an agent tells you before it goes into a customer reply or a pull request. A confident wrong answer to a customer is worse than a slower right one.
- Own the fix. Hand agents well-scoped bug fixes and tests, review their changes carefully, and be ready to explain every line.
- Protect data. Know what can and cannot go into an AI tool under our data policies and customer agreements. Support tickets often contain customer data.
- Share what works. Show teammates the prompts and workflows that speed up support, so the whole team benefits.

This role isn't for you if
- You want to spend all your time writing code. To start, more than half this role is support, and it's what customers notice first.
- You don't enjoy explaining technical problems to people who aren't technical.
- You prefer to hand-write every line and see AI agents as a shortcut to avoid.
- You want to do ML research or model training. This is product engineering on top of existing models.

What you bring
- 1–2 years of professional experience with C# and .NET, plus JavaScript and HTML.



Co-op and internship experience counts.
- Experience helping software users: technical support, a help desk, or a customer-facing developer role.
- Regular use of AI coding tools (Claude Code, Copilot, Cursor, or similar) beyond autocomplete, with an example of something you built or debugged with one.
- Clear written English. You can explain a technical problem and its fix to a customer who isn't technical.
- A methodical approach to debugging: you reproduce, isolate, and confirm before you call something fixed.

Nice to have
- Power BI, Power BI Embedded, or DAX.
- Azure: App Service, Azure SQL, Azure Functions, or reading Azure logs.
- OAuth 2.0 / OpenID Connect basics with Entra ID, Okta, Auth0 or others.
- SQL.
- A ticketing tool such as Freshdesk, Zendesk, or Jira Service Management.

How we workOur team is global, like our customers. We don't have an office and don't plan to get one.

How we hireOur interviews test how you solve problems with AI, so bring your usual tools. We run a lot of experiments and talk openly about the ones that fail, which is why the first application question asks about a time AI led you astray. After an initial screening, successful candidates can expect the following:

1. Application questions. You'll receive a link to an application form where you'll answer three short written questions.
2. Support sample (about 20 min, on your own time). We will email you a sample customer ticket with some logs. You tell us what you think is wrong and draft your reply to the customer. Use your usual tools, AI included.
3. Intro call (30 min). Your background and a walkthrough of a problem you solved with help from an AI tool.
4. Paired session (60 min, on Teams). A few days before, we give you a small C# and JavaScript app so you can check it runs on your machine. On the call, you work through a customer-reported bug in it, sharing your screen: find the cause, fix it with your usual AI tools, and explain the fix as you would to the customer. A clear diagnosis beats a rushed fix.
5. Team conversation (45 min). You meet the team and talk through a support problem you've handled.
6. Paid contract. You work full time on support tickets and real fixes and features. The more you automate on Support, the more dev work you'll get to do.

If you need an adjustment at any stage, such as extra time or a different format, tell us and we'll arrange it.

📌 Junior Developer, Support + Engineering (Canada)
🏢 Reporting Hub
📍 Canada