Go Tech Lead

Position Responsibilities - End-to-end technical ownership of the Go microservices architecture: service design, inter-service communication patterns, and long-term technical direction - First technical review point for new product and feature requests — shaping service boundaries and integration patterns before implementation begins - Definition and evolution of backend engineering standards: API design conventions, Go idioms, code quality practices, testing approaches, and shared patterns - Backend system health across the fleet: reliability, latency, error rates, and the operational posture of services under production load - Cross-functional technical alignment with Product, Mobile, Frontend, QA, and DevOps - Mentoring of backend engineers — raising the technical bar across the team, not just within your own services - Technical decision-making on service decomposition, data ownership, inter-service contracts, third-party integrations, and infrastructure trade-offs Requirements Qualification and Experience - 8–12+ years of mobile engineering experience, with meaningful time on production consumer applications - Demonstrated experience in a technical leadership role — Tech Lead, Architect, or equivalent— where you set direction, not just delivered it - Deep production-grade expertise in Go — building, operating, and evolving backend services at scale - Strong understanding of Go concurrency patterns: goroutines, channels, context propagation, and the failure modes that come with each - Proven experience designing and operating microservices at production scale — service decomposition, ownership boundaries, and managing the operational complexity of distributed systems - Strong hands-on experience with inter-service communication: gRPC and Protocol Buffers, REST, and the trade-offs between synchronous and asynchronous patterns - Strong experience with relational databases (PostgreSQL or MySQL) — schema design, query optimisation, and migrations under a live system - Working knowledge of message queuing and event-driven architecture (Kafka, RabbitMQ, or equivalent) in a distributed service context - Practical experience with containerisation and orchestration (Docker, Kubernetes, or cloud-managed equivalents) - Strong awareness of observability at the distributed systems level: structured logging, metrics, distributed tracing, and alerting across service boundaries