Overview

Stacks: React/TypeScript, .NET Core, Java, Go The role

Qualifications

• Strong proficiency in the front-end stack — React and TypeScript, in production, at a level where you make architectural calls rather than follow patterns.
• Strong proficiency in at least one backend language — .NET Core, Java or Go.
• A genuine willingness to learn the others. You read unfamiliar code without flinching, and you expect to be useful in a second backend language within a quarter.
• Languages: React + TypeScript (strict mode, typed API clients). Then one or more of: ASP.NET Core / C# with EF Core; Spring Boot / JVM; idiomatic Go with goroutines and context.
• Architecture: Clean architecture or hexagonal, dependency inversion, clear service boundaries. REST API design with OpenAPI contracts. Event-driven patterns — queues, idempotency, retries with backoff. Judgment about when a pattern is overkill.
• Databases: Strong PostgreSQL — schema and index design, reading EXPLAIN ANALYZE, transactions and isolation levels, versioned migrations. Redis for caching.
• AWS: Production experience with ECS/EKS or Lambda, RDS, S3, SQS/SNS, Secrets Manager, CloudWatch, IAM least privilege. Terraform or CDK.
• Containers: Docker including multi-stage builds. Working Kubernetes knowledge
• CI/CD: Pipelines you have built and maintained (GitHub Actions, GitLab CI, Azure DevOps). Trunk-based development, tests as a real merge gate, migrations in the deploy path, blue/green or canary rollout with a rollback you have used.
• Observability: Structured logging, metrics, distributed tracing with OpenTelemetry.
• Security: OWASP Top 10, OAuth 2.0 / OIDC, JWT, role- and attribute-based access control, secrets out of source control.
• Testing: Unit, integration against real dependencies (Testcontainers), and contract tests between services.
• Git and agile: Rebasing, bisecting, clean commit history. Comfortable in Scrum or Kanban — refinement, story slicing, honest estimation.
• Hands-on experience with agentic coding tools — Claude Code, Cursor, GitHub Copilot or equivalent — used on real production work, not just tried once.
• The judgment to review AI output critically. You do not merge code you cannot explain, and you catch the plausible-but-wrong answer.
• A sense of where these tools pay off and where they cost more than they save.
• Bonus: experience building with LLM APIs, or setting up AI tooling and conventions for a team.
• English fluency. Stand-ups, design discussions, incident calls and code review all happen in English, daily, with a distributed team. You need to be able to disagree with a colleague about an architectural decision in real time, on a call, and be understood precisely.
• Strong written communication. Pull request descriptions, design documents and status updates that a reader in another time zone can act on without a follow-up meeting.
• Autonomy. You can take an under-specified problem, ask the three questions that matter, and make progress without daily direction.
• Ownership. You participate in on-call, respond to incidents, and write the follow-up that stops the same failure twice.
• Mentorship. You review code in a way that teaches, and you pair with mid-level engineers rather than letting knowledge concentrate in one person.
• Pragmatism. You push back on complexity that is not paying for itself, and you flag slippage early rather than at the deadline.
• 8+ years professional software engineering, at least five owning backend services in production
• Strong React/TypeScript plus at least one of .NET Core, Java or Go
• Production PostgreSQL, AWS, Docker and CI/CD experience
• Hands-on AI coding tool experience
• English C1+, spoken and written

Nice to have

• Workflow orchestration — Temporal, Camunda, Step Functions or similar durable execution engines
• Kafka or another event streaming platform at meaningful volume