You will make the decisions that are expensive to reverse: service boundaries, data model, tenancy, how the thing degrades when a dependency is down. We build on .NET and Azure for clients who need the system to still make sense in year three, so the reasoning behind a decision matters as much as the decision.

What you ll do

- Own the architecture of .NET platforms on Azure, from discovery through to production
- Write the decision records - what was chosen, what was rejected, and what would change the answer
- Design for multi-tenancy, auditability and data residency where the client s regulator requires it
- Set the standard for testing, observability and release safety, then hold the team to it
- Work directly with client architects and CTOs as the technical counterpart in the room
- Mentor engineers: the goal is a team that no longer needs you on every call

What we re looking for
- Eight or more years in .NET,



several of them designing systems rather than only building them
- Deep Azure - App Service, AKS, Functions, Azure SQL, Service Bus and the cost model behind them
- Fluent in distributed-systems failure: retries, idempotency, eventual consistency and their costs
- Able to say no to an architecture that is more engaging than the problem requires

Nice to have Not required. Apply if the section above fits.
- Regulated-domain experience - lending, payments or healthcare
- Event-driven or CQRS systems in production
- Azure certification

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 Dotnet Solution Architect (India)
🏢 ITLabz Technology
📍 India