Key Notes
C# and modern .NET experience sits at the centre of this backend position, supported by AWS, Terraform, microservices and production observability. The London role publishes £85,000–£90,000 and requires 60% office attendance over a twelve-week period. Its domain examples include customer accounts, notifications, journey search, bookings, payments, carrier integrations and real-time timetable information.
What You'll Work On
- Deliver backend features within an assigned domain, with team areas including accounts, notifications, search, bookings, payments, carrier integrations and timetables.
- Own C#/.NET changes from code through deployment and monitoring, using the team’s cloud infrastructure and delivery tooling.
- Improve the codebase, contribute to technical decisions and identify blockers or repeated work affecting the team’s delivery.
- Coach and mentor colleagues working on backend services, sharing technical knowledge through the development lifecycle.
Why This Role Matters
- Trainline’s journey-search and ecommerce services depend on backend features moving reliably from code into monitored production, where failures would affect customer booking paths.
- Connections with more than 270 transport operators across 45 countries use carrier integrations and timetable services, making maintainable interfaces and production observability important to service coverage.
What They Are Looking For
- Technical: Relevant technical skills include hands-on C# and current .NET experience and Terraform; cloud-platform experience is sought with AWS preferred and Azure or GCP also valued.
- Technical: Relevant technical skills include microservices, distributed systems, event-driven architecture and asynchronous messaging experience.
- Technical: Relevant technical skills include CI/CD pipeline design with GitHub Actions, TeamCity, Spacelift or comparable tooling.
- Technical: Relevant technical skills include observability and production-support experience using logging, monitoring, alerting, New Relic or ELK equivalents.
- Technical: Relevant technical skills include identity and authentication work with IdentityServer, OpenID Connect or OAuth2.
- Stakeholder: Relevant stakeholder skills include mentoring, pair programming and cross-functional feature delivery.