Tech Lead - Android Experience Engineering

Market insights

Stack

Free. Sign in with email.

Apply

Upload your CV — we will connect you with the employer directly through our pool.

Description

What You Will Own Architecture & technical direction Own the technical architecture for your squad's domain - system design, API contracts, data models, integration patterns, and the Architectural Decision Records that document why. Enforce the Watu engineering standards within your squad: GitHub for all code, mandatory PR review, coverage gates, OpenAPI documentation, runbooks, and secrets management. Be the squad's representative to the Platform General Architecture - escalate cross-squad concerns, contribute to shared standards, and ensure your squad's patterns align with the broader platform direction. Delivery & quality Review and approve all pull requests for your squad. Not as a bottleneck, but as the quality gate. Your name is on everything that ships. Define and maintain the squad's Definition of Done. Work with the embedded QA engineer to ensure quality is built in, not bolted on. Own the squad's release process. Nothing ships without your sign-off - including work from external partners where applicable. Drive sprint planning with the Product Owner - translate user stories into technical tasks, surface dependencies, flag risks early. Partner & vendor governance Where your squad governs an external partner, you are the technical point of accountability. The partner executes; you govern. Architecture decisions, code quality, and release timing are owned internally. Review partner code via PR access. Nothing a partner ships enters production without your review. Peopl

Full description, company and the link to apply — after you sign in. Sign in

Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.