You will join the Engineering team of a fast-growing international B2B SaaS platform. In a high-impact startup environment, you are the technical authority: you write code every day, design the architecture, mentor developers, and leverage AI as a productivity multiplier. Every decision you make ships to production and reaches millions of end users. • *WHAT YOU WILL DO :** – Design and build Go microservices with clean architecture (hexagonal, DDD, well-defined domain boundaries) and ship to production daily – Develop and evolve frontend applications in Next.js / React (App Router, SSR/SSG, design systems, accessibility) – Own critical technical decisions: data modeling, API contracts, concurrency patterns, error handling strategies – Drive the distributed, event-driven architecture of the platform (pub/sub, CQRS, event sourcing, saga orchestration) – Conduct thorough code reviews focused on correctness, readability, and long-term maintainability – Design for multi-tenancy: per-tenant data isolation, tenant-aware routing, cross-tenant analytics – Build and maintain CI/CD pipelines and implement observability as a first-class concern (structured logging, distributed tracing, alerting) – Own production reliability: incident response, post-mortems, SLA monitoring – Mentor a team of 3 to 4 developers through pairing, reviews, and structured feedback, and run an effective Agile process – Integrate AI tooling into the development workflow — from code generation to agentic pipelines — and help define quality guardrails • *WHO YOU ARE :** – 7+ years of software development experience — you still write code every day and you excel at it – Strong proficiency in Go and/or a systems-level language, and in Next.js / React / TypeScript – Deep experience with distributed systems, event-driven architecture, and Domain-Driven Design – Proven technical leadership: code reviews, mentoring, full ownership mindset – Genuine curiosity about AI-augmented development — you have experimented, you have opinions – Comfortable with autonomy and ambiguity in a fast-moving startup context