Since .NET MAUI went GA in 2022, the number of developers listing it as a skill has grown rapidly — faster than the number of developers who've actually shipped a production app with it. That gap creates a real problem for teams hiring right now.
I've interviewed 60+ MAUI developer candidates over the past two years and helped companies make the final call on dozens of hires. Here's the framework I use to tell the difference between a developer who genuinely knows MAUI and one who watched a tutorial and updated their LinkedIn.
The Core Skills a Real MAUI Developer Should Have
Before you open a job description, get clear on what "good" looks like. A mid-to-senior MAUI developer should demonstrate fluency in all of these areas:
1. .NET and C# Fundamentals
MAUI is a C# framework. Weak .NET fundamentals always surface in MAUI code — poor async patterns, overuse of static state, ignoring IDisposable. A strong MAUI developer is a strong C# developer first. Look for comfort with async/await, LINQ, generics, and dependency injection.
2. The MVVM Pattern — In Practice, Not in Theory
Every MAUI developer claims to know MVVM. The real signal is how they implement it. Do they know why ViewModels shouldn't reference the navigation stack directly? Can they explain the difference between data-binding modes? Do they use CommunityToolkit.Mvvm source generators or hand-write INotifyPropertyChanged? The answers reveal how many production apps they've actually maintained.
3. Shell Navigation
Shell is the recommended navigation system in MAUI. A developer who doesn't know how to register routes in MauiProgram.cs, pass query parameters between pages, or handle deep links hasn't built a real multi-screen app.
4. Platform-Specific Code Patterns
The ability to write platform-specific code cleanly — via interfaces and partial classes, not #if directives — is a reliable marker of seniority. If a candidate can't articulate why the interface approach is better, they've probably never maintained a MAUI codebase long enough to feel the pain.
5. Handlers — Not Just Renderers
If they come from Xamarin, ask specifically about migrating custom renderers to handlers. If they can't explain the architectural difference, they're either new to the ecosystem or haven't done a real migration. Either way, that's important information.
6. Deployment and App Stores
Building an app and shipping an app are two different skills. A developer who has only run apps on simulators hasn't wrestled with code signing, provisioning profiles, App Store review guidelines, or Google Play's data safety declarations. Ask whether they've personally submitted to the App Store or Google Play — and what surprised them.
The Interview Questions That Actually Work
Avoid questions with memorisable answers. These open-ended questions reveal how a candidate thinks about real problems:
"Walk me through how you'd handle a feature that needs to behave differently on iOS and Android, without using #if directives in shared code." — Listen for: interfaces, DI registration in MauiProgram, partial classes.
"Our app has a list page that feels slow on older Android devices. How do you approach diagnosing and fixing that?" — Listen for: CollectionView vs ListView, compiled bindings with x:DataType, item template complexity, image optimisation, profiling with dotnet-trace.
"Tell me about a bug that only appeared on one platform and how you found and fixed it." — This question separates developers who've shipped from developers who've only developed. Platform-only bugs are a rite of passage — if they can't describe one, they probably haven't shipped.
"How do you register and consume platform-specific services in MauiProgram.cs?" — Demonstrates whether they understand MAUI's built-in DI container and the single-project architecture.
Red Flags to Watch For
- They've only worked in sample or tutorial apps. Ask for links to published apps (App Store or Google Play). Not a requirement for juniors, but a strong signal for mid-to-senior roles.
- They can't explain why they'd use CollectionView over ListView. This is a basic and common performance decision — not knowing it suggests shallow hands-on experience.
- They confuse MAUI with Blazor Hybrid or misexplain the Handler architecture. These are distinct features. Confusion here usually means surface-level knowledge.
- No opinion on project structure. Developers who've built real apps have strong opinions about how to organise a MAUI solution. Those who haven't tend to shrug.
- They've never submitted to an app store. Cross-platform development includes deployment. A developer who hasn't navigated the App Store or Google Play review process will need hand-holding on production deployments.
Junior vs. Senior — What to Actually Expect
| Skill Area | Junior MAUI Dev | Senior MAUI Dev |
|---|---|---|
| MVVM implementation | Understands concept, uses boilerplate | Uses source generators, explains tradeoffs |
| Platform-specific code | Uses #if directives | Uses interfaces + DI, explains why |
| Performance | Knows CollectionView exists | Profiled real apps, applied compiled bindings |
| App store submissions | Little or no experience | Has submitted, handled rejections |
| Handlers | Knows they exist | Has written and migrated handlers |
| CI/CD | Relies on others | Set up GitHub Actions pipelines independently |
How to Skip the Vetting Process Entirely
Everything above is useful if you're building an in-house hiring process from scratch. But if you don't have a MAUI expert on staff to assess candidates, you're essentially grading papers without an answer key.
That's exactly the scenario where a pre-vetted developer pool makes the most sense. Every developer in our network has been assessed against the criteria in this article — code review, architecture questions, and a review of actual shipped apps — before they ever appear in a shortlist.
You still conduct a technical interview (we encourage it), but you're evaluating fit and working style, not trying to reconstruct a MAUI curriculum from scratch. See available developer profiles.
"Hiring a MAUI developer through a general job board is like hiring a surgeon from a general staffing agency. The credentials might check out on paper, but the only way to know if they've actually operated is to ask the right questions — or talk to someone who already has."
David has designed the architecture for 20+ enterprise mobile applications and interviewed hundreds of .NET developers over his career. He advises companies on building and scaling cross-platform mobile teams and contributes to engineering hiring frameworks for MAUI-focused projects.
