Senior .NET Developer

About There’s a difference between developers who write code and developers who build systems. We’re looking for Senior .
NET Developers who can take ownership of backend systems end-to-end — from architecture discussions to deployment and production reliability. This role requires someone who has operated real systems under load, understands distributed system trade-offs, and writes code that remains maintainable long after it ships. You’ll work on high-concurrency backend services where scalability, observability, and reliability matter deeply. What You’ll Do
• Design, develop, and maintain backend services using .
NET Core and microservices architecture.
• Handle high-concurrency production systems and proactively identify bottlenecks before they become incidents.
• Contribute to architectural and system design discussions with strong technical reasoning.
• Mentor junior engineers through code reviews, design discussions, and engineering guidance.
• Improve production reliability, observability, and system maintainability.
• Work with REST APIs, distributed messaging systems, databases, and containerised deployments.
• Participate in CI/CD and deployment workflows.
• Help build systems that remain stable under scale, failures, and production pressure. Who Is The Right Fit
• Has strong hands-on production experience with .
NET Core (C#).
• Has worked with distributed systems or microservices architectures in production.
• Understands system reliability concepts like circuit breakers, retries, idempotency, tracing, and fault tolerance.
• Has experience with RabbitMQ, Kafka, SQL/NoSQL optimisation, Docker, Kubernetes, and CI/CD pipelines.
• Writes maintainable, readable, production-quality code.
• Can mentor other developers and elevate team quality.
• Thinks deeply about architecture, operational reliability, and long-term maintainability. Not a Fit If
• Your experience is limited to older .
NET Framework without .
NET Core.
• You haven’t worked on distributed production systems.
• Your experience is mostly greenfield development without operating live systems.
• You prefer purely individual contributor work without mentoring or collaboration.