Lead Golang Developer

We are looking for a Lead Golang Developer to lead a backend team, design high-load services, and ensure technical quality while aligning technical goals with business objectives.

• •Gather and prioritize technical requirements, translate them into engineering tasks, synchronize technical goals with business objectives, and advocate for technical quality.
• •Lead a team of backend engineers: hiring, onboarding, task distribution, employee development, fostering a code review culture, mentorship, and knowledge sharing.
• •Design, develop, and ensure the reliability of high-load services with a target availability of 99.95%, measurable SLOs (latency P95/P99, throughput, RTO/RPO), and be responsible for technical quality and system stability in production.
• •Develop the architecture of a distributed microservices system: identify bottlenecks and risks, design scalable solutions, and prevent incidents.
• •Enhance development, testing, delivery, and operation processes of services, including CI/CD, on-call, incident response, blameless postmortems, architectural and code reviews, and internal technical sessions.

• •Office work in Limassol.
• •Flexible start of the workday.
• •Lunch compensation.
• •Health insurance for employees and family members.
• •External and internal training, development budget.
• •Menu of internal benefits for employees.
• •Corporate and sports events of various formats.

• •6+ years of commercial experience in Go development, including 1-2 years in a Team Lead / Tech Lead role.
• •Deep understanding of multithreading.
• •Designed and operated high-load distributed microservices systems.
• •Knowledge of distributed system patterns (Saga, Outbox, Circuit Breaker, Bulkhead, CQRS, etc.) and typical issues in microservices architectures (distributed transactions, eventual consistency, cascading failures, data duplication) and their solutions.
• •Experience with REST, gRPC, and asynchronous communication (Kafka, RabbitMQ, WebSocket, Pub/Sub, SSE), understanding the application scenarios for each mechanism.
• •Knowledge of SQL and NoSQL databases, experience in query profiling and schema migrations, understanding when each data model is appropriate.
• •Worked with microservices infrastructure (Docker, Kubernetes) and built CI/CD pipelines.
• •Understanding of observability principles: metrics (RED/USE, SLI/SLO, health checks), logging, tracing, and monitoring (Prometheus/Grafana, distributed tracing, centralized logging).
• •Ability to argue architectural decisions to both technical and non-technical audiences.