Backend Engineer (C# / .NET)

About the role

We build server-side systems on .NET. Our codebases use a CQRS architecture: changes to the system go through commands that are validated, transacted, and audited, and reads go through a separate query layer. We're looking for a mid-level C#/.NET engineer (roughly 2-5 years) to join us and grow with the team.

What you'll do

• Ship features end to end: a command and its handler, the validator, the domain model, the EF Core entity configuration and migration, the query that reads it back, and the test that proves it works.
• Work in a command/handler CQRS pipeline, where writes flow through one path (validate, transact, audit) and reads flow through another.
• Model the data: design the schema, write migrations you trust, and reason about relational integrity.
• Build long-running, multi-step processes as workflows and state machines, where the legal transitions actually matter.
• Own your work all the way down. When something is unclear, you trace it through the code and the domain, and you fix the whole problem in one pass rather than the one line that was pointed at.

What we need from you

These are the things you'd use across the work here, so we're looking for real comfort with them.

• Solid C# and .NET, building and maintaining server-side applications.
• CQRS / command-handler architecture: you get why writes go through commands and handlers, and you're comfortable working that way.
• Entity Framework Core and PostgreSQL: you can model a schema, write and review migrations, and reason about SQL and relational integrity.
• Workflow / state-machine modeling: you can think in terms of stages, transitions, and the rules that gate them, rather than flat CRUD.
• Background jobs: comfort with scheduled and asynchronous work (Hangfire or similar).
• Multi-tenant systems: you understand the data-isolation and scoping concerns that come with serving many tenants.
• A real testing habit: you write integration tests that catch actual regressions, and you treat a passing run as part of "done."
• Comfortable working in an agile environment: short iterations, regular check-ins, and adapting as priorities shift.
• You think a problem through before writing code, and you're honest about what you've verified.

If you meet most of these, we'd like to hear from you.

What we work with

• C# 12 on .NET 8, ASP.NET Core
• CQRS: command/handler write path (validation, transactions, audit) and a dedicated query + repository read path
• Entity Framework Core 8 + PostgreSQL: entity configurations, migrations, multi-schema data models
• Workflow / state-machine orchestration for long-running processes
• Background jobs (Hangfire), multi-tenant architecture
• FluentValidation, Autofac (module-based, assembly-scanned DI)
• xUnit + Testcontainers: integration tests against a real database

React experience is a big plus

Our products have React frontends, and engineers who can follow a feature across the line, or pick up frontend work when it helps, are especially valuable to us. If you're comfortable in React (and TypeScript), tell us; it's a real differentiator, even though the core of this role is backend.

Nice to have

• Reporting and document generation (HTML to PDF, Excel)
• Real-time (SignalR)
• Integrating external gateways, devices, or protocols
• Dapper or hand-written SQL where the ORM isn't the right tool

How to apply