• Designing, building and shipping .NET 8 microservices behind our API gateway — from data model to deployed pods.
• Migrating capabilities off the legacy estate onto the new platform (strangler-fig style), including the integration layer that keeps old and new consistent while both run in parallel.
• Building event-driven flows with MassTransit and Azure Service Bus, with the idempotency and eventual-consistency handling that actually survives production.
• Working across Azure SQL, Elasticsearch and Redis — schema design, query performance, index and cache strategy.
• Writing the unit and integration tests that prove your change works, and diagnosing issues in production via App Insights.
• Owning your slice of the delivery pipeline: Dockerfiles, Kubernetes manifests, Azure Pipelines.
• Reviewing peers' code, and reviewing and steering output from our AI-assisted development pipeline.

How we work

• Small team, short feedback loops, sprint-based delivery tracked in Jira.
• Every change goes through pull-request review — by humans and by our AI reviewer, which runs automatically on open PRs. Some tickets arrive with an AI-generated first draft; reviewing and correcting that is part of the job, and we treat it as a skill.
• Feature branches off development, PR back into development; release branches are cut from there.
• Documentation lives with the code and is expected to be kept current.