About the Role :

Senior Software Engineer (Backend / Angular)

This role is backend-first, but frontend isnt a checkbox. We need real full-stack depth someone who can own a distributed system and ship a maintainable frontend feature without needing a guide.

The non-negotiables :

Backend is the core. You need real experience with :

- .NET / C# - this is the job, not a checkbox

- Microservices and event-driven systems you know when to split, how services talk to each other (REST, queues, events), and what breaks when the boundaries are wrong.

- Dependency injection, clean architecture, modular design - things you care about, not things the style guide forces on you

- Message brokers : RabbitMQ, SNS/SQS, or similar

- Relational databases (Postgres, SQL Server) and NoSQL (DynamoDB experience is useful)

- Testing at all levels : unit, integration, contract. The goal is to actually trust your changes, not just satisfy CI.

- Infrastructure. Real cloud experience. We use AWS, but Azure background is fine if you know the underlying concepts. The point is youve actually deployed and debugged production workloads, not just clicked around a console. CI/CD is not someone elses job here. You should be comfortable building pipelines, writing infrastructure as code (we use Terraform), and automating the things that slow teams down. Observability should be part of how you build, not something you add after the fact. We use OpenTelemetry.

- Frontend. Angular is the framework, but thats not the whole picture. You should understand component design, state management, reactive patterns, and what makes a frontend codebase actually maintainable. Know when to split a component, how to keep things testable, and why your choices matter beyond it works. UI/UX instincts arent required, but you should know what makes a UI brittle.

What senior means here :

Not years. Whether you can design a system and explain why you made the decisions you made. Whether you can work without someone breaking down every task for you. Whether the code you write is still readable six months later, and whether you know when a pattern is the wrong call for the situation rather than just technically correct.

How you work :

You explain your thinking without being asked. You push back when something doesnt make sense, and you dont say yes just to get through a meeting. You can take feedback on your code without taking it personally, and give it the same way.

You should be able to pick up a task and run with it. But this isnt a heads-down, work-alone setup. If somethings off, you say so.

Who wont fit :

Backend engineers whove never touched a frontend. Frontend-heavy candidates with thin service-layer fundamentals. Anyone who gets vague when asked to explain a design decision, or whose cloud experience is mostly theoretical. If the hardest system youve designed is a monolith with a single database and no async workloads, thats going to be a gap. Were not after resume complexity but you should have dealt with real failure modes : race conditions, eventual consistency, service boundaries that didnt hold up.

Useful to have :

- Some familiarity with AI-assisted dev tools (Claude Code, Copilot, Codex, or similar) is useful. The bar is simple : you review what it generates, you catch when its wrong, and you dont ship code you cant explain.

- Familiarity with security at the service level : OAuth, JWT, secrets management, the basics of threat modelling. You dont need to be a specialist, but you should know what questions to ask.

- Prior experience in an agile team not the ceremonies, just the mindset : ship small, learn fast, adjust.