Senior Full Stack Engineer, LanguageWire

• This is a role for someone who takes genuine pride in the craft of building robust, well-designed systems and who wants to be a multiplier: raising the technical level of the team around them, not just shipping code
• 5+ years of backend engineering experience in production environments, with deep expertise in C#, .NET Core / .NET 8+, ASP.NET Web API, and microservices architecture
• Proven track record of owning and evolving production microservices: schema migrations, API versioning, backward compatibility, and long-lived service maintenance
• Strong experience with distributed systems concepts: event-driven architecture, message queues (Azure Service Bus, RabbitMQ), sagas, idempotency, and eventual consistency
• Deep proficiency with relational databases (MSSQL and/or PostgreSQL): complex query design, schema design, indexing strategies, and performance tuning
• Demonstrated experience making and documenting architectural decisions (ADRs, system design, trade-off analysis) with the ability to defend and adapt your choices
• Hands-on DevOps experience: CI/CD pipelines, Docker, Kubernetes, Azure — with the mindset that owning deployment and operations is part of the engineer’s job
• Experience designing robust, versioned REST APIs consumed by multiple teams, including security considerations (OAuth 2.0, API key management, rate limiting)
• Some frontend exposure (Vue.js and/or TypeScript) — enough to contribute when needed, but the primary focus here is backend and platform
• A track record of mentoring and uplifting more junior engineers — through code reviews, design sessions, and raising the quality bar organically
• Strong communication skills and the ability to articulate technical decisions to both engineers and non-technical stakeholders. English fluency required
• Agile, collaborative, and opinionated in a constructive way — you push back when needed and bring others along

Desirable

• As a Senior Full Stack Engineer in the Core Platform Team, you’ll be a principal owner of the foundational microservices that the rest of LanguageWire depends on
• That means driving the architecture, reliability, and evolution of services covering authentication, object storage, notifications, email delivery, and integrations with our ERP and CRM systems — the backbone of the entire platform
• You will set the technical direction for these services: defining how they scale, how they expose capabilities to other teams, and how they maintain the quality bar expected of infrastructure-grade software
• You’ll also contribute to our growing Agentic Roadmap, shaping the tool interfaces and integrations that allow AI agents to invoke platform capabilities across the business — a natural extension of the microservices ownership you already hold
• You’ll join the Core Platform Team, one of the foundational engineering teams at LanguageWire. The team owns and operates 12 microservices that underpin the entire organisation, covering file storage, authentication, notifications, email delivery, and integrations with our ERP and CRM systems, among others. These are the services every other team depends on
• As LanguageWire invests in AI, the Core Platform Team is also taking on a new function: building the tools and integrations that allow AI agents to interact with our services and automate workflows across departments. As a senior member of the team, you’ll contribute to shaping that roadmap while remaining the backbone of the platform’s reliability and technical integrity
• We value outcomes over output, shared ownership over silos, and continuous delivery over long release cycles. Our stack is built on .NET microservices, Azure, and modern API patterns
• Own and evolve foundational services: Take end-to-end ownership of platform microservices (authentication, storage, notifications, integrations), driving their architecture, reliability, and roadmap
• Lead backend architecture decisions: Author architecture decision records, define service boundaries, and ensure microservices are designed for scalability, resilience, and long-term maintainability
• Design and enforce API contracts: Define and maintain clean, versioned, well-documented REST APIs consumed by internal teams and, increasingly, by AI agents
• Drive technical quality: Own non-functional requirements — performance, observability, security, and availability — across the services you lead
• Own your services end-to-end: From architecture and coding to deployment, monitoring, and on-call support (“You build it, you run it”)
• Build AI agent tool interfaces: Design and expose backend capabilities as well-defined tool schemas (OpenAPI specs, MCP server definitions, function schemas) that AI agents and LLM orchestration layers can reliably consume
• Integrate platform services with agentic workflows: Extend existing microservices to support the tool-calling patterns needed for end-to-end AI-driven automation across departments
• Apply agent-aware design patterns: Ensure platform APIs are structured for deterministic, reliable invocation by AI agents — with proper input validation, idempotency, and audit trails
• Mentor and upskill the team: Support mid-level and junior engineers through code reviews, pairing, and hands-on architectural guidance
• Set and raise the engineering bar: Champion best practices in testing, code quality, incident response, and continuous delivery across the team
• Drive DevOps and operational excellence: Own CI/CD pipelines, deployment reliability, and ensure platform services are observable, resilient, and secure
• Collaborate cross-functionally: Work with product managers and domain experts across the business to shape the platform roadmap and translate real needs into sound technical solutions
• In one year, you’ll know you were successful if…
• The core platform microservices you own are more reliable, better documented, and better understood across the organisation than when you joined
• You have led at least one significant architectural improvement that measurably improved scalability, resilience, or developer experience for dependent teams
• Your APIs and tool interfaces are trusted by both internal engineers and the AI orchestration layer — well-defined, stable, and easy to consume
• Engineers on the team are measurably better for having worked alongside you — through code reviews, pairing, and the standards you’ve raised
• You’ve contributed meaningfully to the Agentic Roadmap, enabling at least one AI-driven workflow that saves real time for an operational team