Hire a pro

.NET Developer

C#, ASP.NET Core and Entity Framework, plus the older Framework applications nobody wants to open. The stack that quietly runs a large share of the internal software in finance, logistics, healthcare and manufacturing.

Shortlist within 24 hours · You interview every candidate · Flat monthly rate

ControllerServiceEF CoreSQL ServerN+1C#
Within 24 hoursShortlist
Inside 2 weeksDeployed
5+ years C#Seniority
Flat monthlyRate
Replaced, not billed twiceWrong fit
What they do

Most of this work is somebody else’s code.

Very little .NET work starts from an empty solution. It starts from a system that has been running for eight years, has one person who understands it, and cannot be stopped.

The controller is thin, the service holds the logic, and the ORM is where the performance goes to die. A good .NET engineer watches the generated SQL.
Day to day

Reads before writing

The existing solution has reasons for what it does, some of them good. Understanding which is most of the first fortnight.

Day to day

Watches what EF generates

Entity Framework is excellent until a lazy-loaded navigation property inside a loop turns one page into four hundred queries.

Day to day

Keeps async honest

Async all the way down, no blocking on results, and an understanding of why the mixed version deadlocks in the worst possible way.

Day to day

Handles the Framework to Core question

Some applications should be migrated, some strangled a piece at a time, and some left alone. This is a judgement, not a policy.

Day to day

Writes tests around the risky part

Not everywhere. Around the calculation the business depends on, before changing it.

Tell us the problem and we will shortlist against it.

Book a call
Shortlist within 24 hours
What they know

The tools, grouped by what they are for.

Nobody on the bench knows all of this. We shortlist against what your problem actually needs, and tell you where the gaps are.

Core
C#.NET 8/9ASP.NET CoreMinimal APIsBlazor
Data
EF CoreDapperSQL ServerPostgreSQLMigrations
Legacy
.NET FrameworkWebFormsWCFStrangler migration
Platform
AzureApp ServiceService BusDockerApplication Insights
Quality
xUnitMoqIntegration testsSerilog
How hiring works

From first call to a .NET developer on your team.

You make the decision at every step. We do the searching, the vetting and the paperwork.

  1. Day 1

    Describe the problem

    Thirty minutes on the constraint you are working against and what finished looks like. No job specification needed.

  2. Within 24 hours

    Get a shortlist

    Engineers already vetted for this role, with where each one is strong and where each one is weaker.

  3. Your process

    Interview and choose

    Your questions, your decision. The interview signals further down this page are yours to use.

  4. Inside 2 weeks

    Working on your team

    In your repository and your tools, on a flat monthly rate. If the fit is wrong, we replace them and do not bill the second ramp-up.

How we vet

Four exercises, all of them from real work.

No algorithm puzzles. Every exercise below is a task this role does in a normal week, and we watch the method more than the answer.

  1. Find the N+1

    A real controller action that issues hundreds of queries. We want the profiler or the logged SQL, not a guess.

    Around 40% never look at the generated SQL.
  2. Async deadlock

    Code that blocks on an async call. Explain why it hangs and fix it properly rather than with ConfigureAwait scattered everywhere.

  3. Modernisation judgement

    A described legacy system. Migrate, strangle or leave. A candidate who always says rewrite is expensive to employ.

  4. Domain modelling in C#

    Given a business rule, where does it live. We are watching for anaemic models with all the logic in a service.

Interview signals

Four questions for when you interview them yourself.

You interview every candidate we put forward, so these are yours to use. They separate somebody who has run this in production from somebody who interviews well.

Ask: how do you find a performance problem in an EF Core application?

A strong answer

Logs the generated SQL or attaches a profiler, and looks at query count before query duration. Knows that Include, projection and AsNoTracking each solve different problems.

A worrying answer

Suggests caching or a bigger database server. Both hide a query pattern that will come back at the next data volume.

Ask: async or sync for this data access?

A strong answer

Async throughout, and can explain that the benefit is thread pool availability under load rather than making any single request faster.

A worrying answer

Says async is faster. It is not, for one request, and an engineer who believes that will be surprised by their own benchmarks.

Ask: we are on .NET Framework 4.8. What now?

A strong answer

Asks what the application does and how often it changes before recommending anything. Often recommends strangling one module at a time rather than a big-bang migration.

A worrying answer

Recommends a full rewrite in the first two minutes. Sometimes correct, never knowable that fast, and usually the most expensive available option.

Ask: where do you put business logic?

A strong answer

In the domain or a service layer, with the controller doing routing and validation only. Can say why, in terms of testability rather than tidiness.

A worrying answer

In the controller, because it is fewer files. It is also untestable without spinning up the whole web stack.

Our work

Products our engineers built.

“

Each developer I had worked with from Zeki Experts was talented, efficient, communicative, and self-starting.

SWStuart Washington
Project Manager · Ipsen US
“

Zeki Experts’ team was exceptional: talented, efficient, communicative, and self-starting.

AJAlicia Jack
Director · Prospector Metals Corp.
Honestly

When this is the right hire, and what else we offer.

Ask for this when

Good fit

  • An existing .NET system that needs work and has one remaining expert.
  • A Framework application you need moved to Core without stopping the business.
  • Microsoft-shop internal tooling, integrations or line-of-business software.
We can also provide

Other roles

  • You are starting fresh with no Microsoft dependency. Ask for a full stack developer.
  • Your budget is tight. Start with a short, fixed piece of work and extend from there.
  • The real problem is the database. Ask for a SQL / database developer.
Questions

Before you ask for a shortlist.

Yes, and we screen specifically for it because the older applications are where the business risk usually sits. Engineers who only know modern .NET Core are common; ones comfortable in both are not.

No. A lot of .NET runs on IIS on a server in a cupboard, or on Linux containers, or on AWS. We match to what you actually run rather than what the certification assumes.

For an internal application in a .NET shop, often yes, because one language across both halves is a real saving. For a public site with strict performance requirements, we would usually still reach for a JavaScript framework and say why.

Next step

Describe the problem, not the job title.

Thirty minutes, and a shortlist within a day. If a .net developer is the wrong hire for what you described, you will hear that instead.