Specialised, not generic.
Six courses, deliberately — chosen because Canadian employers can't fill these roles, and because we've shipped every one of them ourselves.
We didn't pick these six because they're easy to teach.
We picked them because Canadian employers are struggling to fill them — and because almost nobody else teaches them.
Specialised beats generic. Nearly every coding school in the country teaches the same general web stack, which is exactly why that queue is the longest one to stand in. Dynamics 365, Power Platform governance and Azure infrastructure are taught almost nowhere — and that is precisely why those roles stay open, and why the people who can do them are paid accordingly.
None of which is a promise. Demand is not the same as a job offer, and we won't pretend otherwise. But it does mean that when you finish, you'll be competing in a much shorter line.
How every track is ordered
You build before you understand. The first several weeks are spent making real things work — and only then do we go back and teach the fundamentals underneath them. It's the opposite of how most courses are sequenced, and it's the reason people stay: abstract theory is unbearable before you've felt why it matters, and obvious once you have.
Backend DevelopmentWeb API + database + web app, in C#
Path
The broadest track and the most common starting point. You finish able to design a database, build an API on top of it, and put a working web application in front of it.
Weeks 1–6 · Build first
- Ship a working Web API in your first fortnight — before you understand all of it
- Connect it to a real database and see your data move
- Put a simple web front end on top and deploy it somewhere public
- Git from day one: branches, commits, pull requests
Then · Fundamentals
- C# properly: types, classes, interfaces, generics, LINQ, async/await
- Object-oriented design — and when not to use it
- Relational modelling, normalisation, indexes, and reading a query plan
- Entity Framework Core: migrations, relationships, tracking, performance traps
Then · Professional practice
- REST design, versioning, validation, error handling
- Authentication and authorisation with ASP.NET Core Identity and JWT
- Testing: unit tests with xUnit, integration tests against a real database
- Clean architecture, dependency injection, configuration and secrets
Finally · Portfolio
- One substantial application, built end to end and deployed
- Code review on everything — the way it happens in a real team
- You explain your own architecture out loud, repeatedly, until it's easy
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
Mobile DevelopmentFlutter, Kotlin, and shipping to real devices
Path
Mobile is the track where progress is most visible — the thing you built is on your own phone by the end of the first month. We'll show you apps we've shipped and take them apart with you.
Weeks 1–6 · Build first
- A working app running on your own phone in the first fortnight
- Screens, navigation and layout by building, not by reading
- Wire it to a real API and show live data
- We walk you through apps we've built in the past — architecture, mistakes and all
Then · Fundamentals
- Dart properly: types, null safety, async, streams
- How Flutter actually renders — the widget tree and why rebuilds matter
- State management: setState, Provider, then Riverpod or Bloc
- Kotlin and native Android with Jetpack Compose, so you're not locked to one toolkit
Then · Professional practice
- Local storage, caching and offline behaviour
- Authentication, secure storage, deep links, push notifications
- Testing widgets and business logic
- Publishing: signing, store listings, review process, staged rollout
Finally · Portfolio
- One app of your own, published to a store
- A second smaller app to prove the first wasn't luck
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
Azure & DevOpsCI/CD and infrastructure as code with Bicep or Terraform
Path
For people who'd rather build the machine that ships software than the software itself. Strong demand, less crowded than application development, and the skills transfer across every stack.
Weeks 1–6 · Build first
- Deploy a real application to Azure in your first week — by hand, so you feel the pain
- Then automate that same deployment and never do it by hand again
- Your first pipeline: build, test, deploy, on every commit
Then · Fundamentals
- Azure core: resource groups, App Service, Storage, SQL, networking basics
- Identity: Entra ID, managed identities, service principals, RBAC
- Secrets done properly with Key Vault
- What the cloud actually costs, and how to stop it surprising you
Then · Infrastructure as code
- Bicep from first principles: modules, parameters, what-if deployments
- Terraform: state, providers, workspaces — and when to prefer it
- Multi-environment setups: dev, test, production, with approvals between them
- Rollback, blue-green and why every deployment needs an undo
Then · Operations
- Monitoring and alerting with Application Insights and Log Analytics
- Containers and Docker fundamentals
- Incident response: reading logs under pressure without panicking
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
Dynamics 365 — DeveloperDataverse, plug-ins, PCF controls and solution ALM
Path
A specialised, well-paid corner of the Microsoft ecosystem with far fewer candidates than general web development. If you already have business-software experience, this is often the fastest route in.
Weeks 1–6 · Build first
- Build and ship a working model-driven app in your first weeks
- Customise tables, forms, views and business rules until it feels ordinary
- Your first real plug-in, deployed and firing
Then · Fundamentals
- Dataverse properly: tables, relationships, choice columns, alternate keys
- The security model — business units, teams, roles, row-level sharing
- The platform event pipeline, and where your code fits in it
- C# refreshed and sharpened for plug-in development
Then · Professional practice
- Plug-ins and custom workflow activities, written to be testable
- Web API and the Organization Service, including batch operations
- PCF controls with TypeScript for custom UI
- Power Automate and custom connectors where code isn't the right answer
- ALM: managed vs unmanaged solutions, environments, deployment pipelines
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
Power Platform AdministratorGovernance, environments, security and tenant health
Path
Every organisation that adopted Power Platform quickly discovered it needed someone to govern it. Comparatively few people do this well, and it suits people who are organised and careful more than it suits natural coders.
Weeks 1–6 · Build first
- Stand up a properly governed environment from scratch
- Write and apply your first data loss prevention policy
- Break something deliberately in a sandbox, then work out why
Then · Fundamentals
- Environments, capacity and how licensing actually works in practice
- Dataverse security: roles, teams, business units, column-level security
- Entra ID groups, conditional access and how they meet the platform
- Tenant settings and what each one really controls
Then · Governance at scale
- The CoE Starter Kit: installing it, and reading what it tells you
- Monitoring, analytics and capacity planning
- Managed Environments, sharing limits and maker onboarding
- ALM: solution pipelines, environment strategy, release governance
- Writing the policies humans will actually follow
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
Dynamics 365 — FunctionalConfiguration, business process and consulting
Path
The track for people who are good with people. You'll configure rather than code, and the hardest skill is working out what a business actually needs as opposed to what it first asked for.
Weeks 1–6 · Build first
- Configure a working sales process end to end in your first weeks
- Forms, views, dashboards and business rules — no code
- Automate something genuinely useful with Power Automate
Then · Fundamentals
- The Dynamics 365 data model and how the modules fit together
- Sales and Customer Service in depth
- Security roles and what different users should actually see
- Data migration and import: the part that sinks real projects
Then · Consulting practice
- Running a requirements workshop without losing the room
- Writing specifications a developer can build from
- Reporting and dashboards with Power BI
- UAT, training end users, and go-live support
- Knowing when the honest answer is ‘the platform shouldn't do that’
Jira and Azure Boards, what a story, a bug, a spike and an operational item really are, sprints, standups, estimation, pull requests, CI/CD, environments and incidents — the part of the job nobody teaches. See what's covered
You'll also learn how a software team actually runs.
New developers rarely come unstuck on the code. They come unstuck in the first fortnight, staring at a board full of tickets written in a vocabulary nobody explained — stories, spikes, points, refinement, sev‑2. We've spent years on the management side of exactly that, watching capable people struggle for reasons that had nothing to do with programming. So we teach it deliberately, alongside the technical work, in the same tools you'll be handed on your first day.
- What a story, a task, a bug, a spike and an operational item each actually mean — and why using the wrong one irritates everybody
- Epics, and how a piece of work too big to start gets broken into pieces you can start
- Acceptance criteria, and why “done” is agreed before you write a line
- Reading a ticket somebody else wrote, and knowing what to ask before you pick it up
- Jira: boards, backlog, sprints, workflow states, and moving your own ticket along without being chased
- Azure Boards, since a great deal of the .NET world lives there rather than in Jira
- Confluence and wikis — writing it down so the next person doesn't have to ask you
- Reporting progress honestly, including the part where you're blocked
- Why sprints tend to be two weeks, and what Scrum and Kanban each feel like to work inside
- Standup: what to say in sixty seconds, and what nobody in the room wants to hear
- Refinement and estimation — story points, why they aren't hours, and planning poker
- Review and retrospective: giving and taking criticism about the process rather than the person
- Branching, pull requests, and code review as a conversation rather than a verdict
- What a CI/CD pipeline is doing, and what to do first when the build goes red
- Dev, test, staging and production — and why you don't fix it in production
- Releases, rollbacks, hotfixes, incident severities, and the post-mortem that blames the system
Included in every track. We don't charge extra for it.
Choosing between them
I have no technical background at all.
Backend Development or Dynamics 365 Functional. Backend if you want to write code for a living; Functional if you're strong with people and processes and would rather configure than program. Both are common starting points from zero.
I work in IT or infrastructure already.
Azure & DevOps, or Power Platform Administrator. Both build directly on what you already know, which usually means a shorter path than starting from scratch.
I've used CRM or ERP systems in a business role.
Dynamics 365 — Functional or Developer. Your understanding of how businesses actually work is genuinely valuable here, and it's the part that's hardest to teach.
Can I switch tracks partway through?
Yes. It happens, usually in the first month or two once the work stops being theoretical. Tell us and we'll re-plan rather than push you through something that isn't fitting.
Why only six?
Because we teach what we've built. Every one of these is something our teachers have shipped professionally. We'd rather do six things properly than list thirty and be shallow at all of them.
Start with a conversation, not a commitment
Free, about thirty minutes, no pitch. We'll tell you honestly whether we can help.