Dot Net Developer interview questions
Common interview questions and sample answers for Dot Net Developer roles in IT & Technology across Oman and the GCC.
The 10 questions below are compiled from interviews our consultants have run with IT & Technology employers across Oman and the wider GCC. Each comes with a sample answer and what the interviewer is really listening for.
Category
Opening & warm-up
How interviewers test your communication and preparation right from the start.
Walk me through your .NET career.
I've been a .NET developer for nine years, four in Oman. Started in ASP.NET Web Forms at an Indian product company, transitioned through MVC to .NET Core / .NET 6/7/8, and for the past four years I've been senior .NET developer at an Omani enterprise. Stack: .NET 8, ASP.NET Core, Entity Framework Core, SQL Server, deployed on Windows Server and increasingly Azure. I work on internal business applications. Microsoft certified developer.
Stack depth.
Category
Behavioural (STAR)
Past-experience questions. Use the STAR framework: Situation, Task, Action, Result.
Tell me about a complex application you built.
Last year I led the build of a procurement workflow application: complex approval rules per category and value, integration with our finance ERP and SharePoint, role-based access, audit logging. .NET 7 backend with React frontend, six months of work. Application replaced a paper-and-email process; procurement cycle time reduced significantly. Real enterprise .NET delivery has many moving parts; discipline holds it together.
Enterprise delivery.
Describe a performance issue.
Procurement application had slow load times on dashboards. Profiled with the diagnostic tools: N+1 query patterns from EF Core lazy loading, plus large payloads. Refactored: explicit Include() statements, projection to DTOs reducing payload, async patterns throughout. Load time dropped from 4 seconds to 1.2 seconds. EF Core makes development fast but unaware usage produces slow apps; explicit query design matters.
EF Core depth.
Tell me about pushing back on a design.
Architecture team proposed a microservices breakdown for an application that was actually well-served by a modular monolith. I pushed back: microservices have operational complexity (deployment, observability, distributed system challenges) that didn't fit our team size or business need. Adopted modular monolith instead. Years later the choice still serves; we can split modules to services if/when scale demands. Architectural conservatism is often the right call.
Pragmatic architectural thinking.
Category
Technical & role-specific
Questions that test your specific skills for this role.
Walk me through your application architecture.
Clean architecture as default: separation of concerns through layers (presentation, application, domain, infrastructure). Dependency injection extensively for testability. Async/await throughout for scalability. Entity Framework Core with proper change tracking discipline. Caching with IMemoryCache or Redis depending on scope. Background services for async work. Logging via Serilog with structured logging. Architecture serves maintainability; over-architecting small apps wastes effort.
Real .NET architecture.
Describe your testing approach.
xUnit for unit tests, integration tests with WebApplicationFactory for API testing. Mocking with Moq where appropriate. Coverage on business logic; less aggressive on infrastructure code. Test fixtures and builders for setup. CI runs tests on every PR. Test naming convention focused on behaviour (Should_DoX_When_Y). Tests document expected behaviour as much as they verify it. Test quality is part of engineering quality.
Real test discipline.
How do you handle deployment?
CI/CD via Azure DevOps or GitHub Actions: build, test, package, deploy. Environments separated: dev, staging, production. Configuration externalised via environment variables and Azure App Configuration or appsettings. Database migrations applied with EF Core migrations through controlled scripts. Deployment slots for zero-downtime. Monitoring with Application Insights. Modern .NET deployment is mature; legacy patterns (manual MSI installs, file copies) shouldn't be the default.
Deployment maturity.
Category
Situational
Hypothetical scenarios designed to test your judgement and approach.
You need to make an urgent fix to production. How do you handle it?
Verify the issue first (don't fix the wrong thing). Understand root cause; if not fully clear, document hypotheses. Make minimal fix focused on the issue, not surrounding cleanup. Write a test that would have caught it. Get review from another developer even under pressure. Deploy through proper channels with rollback ready. Post-incident review the next day on root cause and process. Urgency isn't an excuse for sloppy engineering; the cost of urgent-bad-fixes is usually worse than the cost of careful-slower-fixes.
Disciplined urgency handling.
Category
Cultural fit & motivation
Why this role, why this company, and how you work with others.
How do you work with the team?
Code reviews with respectful, specific feedback. Pair programming when learning curves are steep. Documentation maintained for non-obvious decisions. Mentorship for juniors. Direct feedback when needed, with the goal of team improvement, not personal correction. I share knowledge actively; team value increases when expertise spreads. Healthy team culture matters more than individual heroics.
Team mindset.
Category
Closing
The final stretch. Often where deals are won or lost.
What are your salary expectations?
For a senior .NET developer role at an Omani enterprise I'd target OMR 1,600 to 2,200 total package depending on application scope and team responsibility. Cloud-modern .NET work pays a premium over legacy. I'd value training budget and certification investment. I'm on 60 days' notice. Beyond pay I'd value the team's stack modernity; .NET 8 vs .NET Framework 4.x produces very different career trajectories.
Researched range and career-trajectory thinking.
Practise these with AI
Get 5 fresh questions tailored to Dot Net Developer, type your answers, and get per-answer feedback from AI. Free, 10 minutes.
Start AI mock interview