About the role
You’ll work on backend services for our delivery engagements — most run on .NET, most are regulated workloads (financial reconciliation, healthcare apps, document-management systems), and most have to last. We optimize for code that survives team changes, not for the framework du jour.
You’ll work alongside a small senior team, on-call rotation kicks in after onboarding (one week every six), and code review is a genuine practice — not a formality.
How we hire
One intro call → a paid short take-home (real-shaped problem, not Leetcode) → a 90-minute working session on your submission → an offer. About two weeks end to end.
What you'll do
- Build and ship ASP.NET Core services, REST APIs, and background workers in production.
- Own features end to end — schema design, business logic, tests, and deployment.
- Write code other engineers can read in six months without you in the room.
- Participate in code review and design discussions — pull requests are how we share standards here.
- Investigate and fix production issues in services you build, not just the ones you broke.
What we're looking for
- 3–5 years of professional experience building backend systems in C# / .NET (Core, 6, 7, 8).
- Solid working knowledge of ASP.NET Core, Entity Framework Core, and REST API design.
- Comfortable with relational databases (SQL Server, PostgreSQL) — you can write a non-trivial query without an ORM.
- Experience writing unit and integration tests as part of normal development.
- Git, pull-request workflows, and CI pipelines are second nature.
Nice to have
- Cloud experience on AWS or Azure.
- Background with messaging (RabbitMQ, SQS, Service Bus) or event-driven architectures.
- Familiarity with CQRS / MediatR, Dapper, or vertical-slice architecture.
- Observability work — structured logging, OpenTelemetry, tracing.