Principal Backend Architect / Engineer (C#/.NET, Azure)
Principal-level backend architect/engineer owning backend architecture in C#/.NET on Azure: incrementally decomposing a monolith, designing APIs and event-driven systems on Service Bus, and mentoring engineers while championing daily hands-on agentic AI tooling. Senior IC role, remote in Brazil, USD 50/hr.
- Compensation
- $50 / hr
- Location
- Brazil
- Work setup
- Not specified
- Seniority
- Principal
- Employment
- Contract
- Experience
- 5+ years
- Category
- Backend
- Posted
Skills
Must have
- Advanced English (written and spoken, customer-facing)
- 20+ years backend engineering
- 15+ years C# / .NET
- 8+ years Microsoft Azure (Functions, Service Bus, Data Factory)
- 5+ years architecture or technical leadership
- Daily hands-on use of agentic AI tooling (Claude, Claude Code or equivalent), plus experience building agents, reusable skills, MCP servers and evaluations
- Deep expertise in C#/.NET across secure, scalable and resilient commercial backend systems
- Hands-on Azure with PostgreSQL, Cosmos DB and Snowflake, plus solid CI/CD and DevOps practice
- Proven experience incrementally breaking down a large monolith, favouring safe and reversible steps
- Strong event-driven and asynchronous architecture background: ordering, idempotency, poison messages, dead-lettering
- Solid API and contract design experience, including versioning and backwards compatibility
- Strong data access at scale instincts: query performance, zero-downtime migrations, messy customer data
- Production ownership: observability, alerting, incident response and root-cause analysis
Nice to have
- Experience partnering with dedicated Data and UI architects inside an established architecture function
- Experience designing customer and partner integrations where failures are visible and recoverable
- Track record of raising the AI capability of an engineering team
- Experience writing Architecture Decision Records and running technical office hours
Full description
Principal Backend Architect / Engineer (C#/.NET, Azure)
International job opportunity!!
USD 50/hr - Direct Hire
Remote — Brazil
Long-term, full-time
Required
- English – Advanced (written and spoken, customer-facing)
- 20+ Years Backend Engineering
- 15+ Years C# / .NET
- 8+ Years Microsoft Azure (Functions, Service Bus, Data Factory)
- 5+ Years Architecture or Technical Leadership
- Daily hands-on use of Agentic AI tooling — HARD REQUIREMENT
About the AI requirement: this is not "I have used ChatGPT". The client expects daily, hands-on work with agentic tooling such as Claude, Claude Code or equivalent, plus real experience building with AI: agents, reusable skills, MCP servers and evaluations. Candidates without this will not move forward.
Deep expertise in C#/.NET across secure, scalable and resilient commercial backend systems.
Hands-on Azure: Functions, Service Bus and Data Factory, plus PostgreSQL, Cosmos DB and Snowflake, with solid CI/CD and DevOps practice.
Proven experience breaking down a large monolith incrementally, favouring safe and reversible steps over rewrites.
Strong background in event-driven and asynchronous architecture: ordering, idempotency, poison messages and dead-lettering.
Solid API and contract design experience, including versioning and backwards compatibility for internal teams, front-end and external integrators.
Strong instincts for data access at scale: query performance, zero-downtime migrations and messy customer data.
Production ownership: observability, alerting, incident response and root-cause analysis.
Nice to Have
- Experience partnering with dedicated Data and UI architects inside an established architecture function.
- Experience designing customer and partner integrations where failures are visible and recoverable.
- Track record of raising the AI capability of an engineering team, not just your own.
- Experience writing Architecture Decision Records and running technical office hours.
Description / Responsibilities
What They'll Do
- Own the backend architecture across all products and drive the incremental decomposition of the monolith into well-bounded services
- Set and enforce backend standards, best practices and tooling, and build shared platform capabilities (libraries, service templates, cross-cutting concerns)