Tech stack (current / relevant)
Language & backend
Backend-heavy role.
- .NET is a plus, but not mandatory if senior backend experience is solid.
Architecture
- Distributed systems.
- Event-driven patterns.
- API-first mindset (contracts, versioning, backward compatibility).
Data
- Relational databases (MSSQL) at production scale
Automation & delivery
- CI/CD as a first-class concern.
- Reusable workflows (GitHub Actions is a strong plus).
- Automated promotion across environments.
Infrastructure
- Infrastructure as Code (Terraform is a strong plus).
- Cloud providers experience (Azure is a strong plus).
Quality
- Automated testing as part of design, not an afterthought.
- Enforce code standards, specially in the era of AI agents
Capabilities
The person must be able to:
- Own and evolve the technical direction of the solution.
- Design systems that are pragmatic, maintainable, and scalable.
- Make end-to-end technical decisions:
design → implementation → deployment.
* See the system as a whole, not just isolated services.
* Drive automation instead of compensating with process or documentation.
* Anticipate technical risks and act before they escalate.
* Translate business and product goals into concrete technical strategy.
* Push back when something adds complexity without enough value.
Soft skills
- Strong critical thinking; challenges assumptions constructively.
- High ownership and accountability.
- Comfortable working with ambiguity.
- Clear, direct communication with technical and non-technical stakeholders.
- Influences through reasoning, not hierarchy.
Working style
- Prioritizes long-term system health over short-term speed.
- Makes deliberate decisions and explains trade-offs clearly.
- Maintains high technical standards even when not explicitly asked.
- Balances pragmatism with technical excellence.
What this role is not
- Not an Engineering Manager role.
- Not a ticket-execution role.
- Not a role for someone who needs constant direction.