Android Team Lead

Jobtailor; Dublin; On-site; EUR 90,000 - 130,000; Full time

Job summary

Jobtailor is seeking an experienced Android Lead to steer a growing engineering team in Dublin. You will set technical direction, own delivery across the Android roadmap, and stay hands-on with Kotlin and Jetpack Compose while mentoring engineers.

You will own the CI/CD pipeline in GitHub Actions, drive a culture of high-quality testing, manage technical debt, and collaborate with Product, Design, QA and Backend to ship features end-to-end. Excellent English required.

Qualifications

• 3+ years in an Android Lead or Engineering Manager role or significant senior-level Android development with leadership ambition.
• Proven track record delivering and scaling consumer-facing Android applications.
• Kotlin is a must — deep, idiomatic command including coroutines, flows, and modern Kotlin patterns.
• Jetpack Compose is a must — production experience building Compose-based UI with state management, navigation, and performance tuning.
• Strong experience with CI/CD in GitHub Actions — building, signing, testing, and releasing Android apps through automated pipelines.
• Demonstrable experience managing and reducing technical debt in a long-lived codebase.
• Strong experience with unit testing and end-to-end testing on Android (JUnit, MockK/Mockito, Espresso, Compose testing, etc).
• Proven experience managing the performance of engineers across levels and developing senior talent.
• Strong understanding of Android architecture patterns (MVVM/MVI, clean architecture, modularisation) and dependency injection (Hilt/Koin).
• Able to balance delivery speed, code quality, and long-term maintainability.
• Excellent written and spoken English and the ability to communicate clearly with technical and non-technical stakeholders.

Responsibilities

• Lead the Android engineering team — setting technical direction and owning delivery across the Android roadmap.
• Write production Kotlin code and build UI in Jetpack Compose; remain hands-on and lead by example in code reviews.
• Own and evolve the CI/CD pipeline in GitHub Actions — builds, signing, automated testing, distribution, and release automation.
• Drive a healthy testing culture across the team — unit testing, integration testing, and end-to-end testing.
• Actively manage and reduce technical debt — track it, prioritise against feature work, and advocate with stakeholders.
• Manage the performance and growth of engineers at all levels — 1:1s, clear expectations, feedback, career progression.
• Partner with Product, Design, QA, and Backend to scope, plan, and deliver features end to end.
• Own Android app performance, crash-free rates, startup time, and Play Store quality — instrument and act on data.
• Recruit, interview, and onboard Android engineers as the team grows.
• Stay current on the Android ecosystem and bring changes (Compose updates, Kotlin features, AGP, policy) into practice.

Skills

Android leadership

Kotlin

Jetpack Compose

CI/CD

Testing (Unit & E2E)

Technical debt management

Mentoring / people management

Stakeholder communication

MVVM/MVI architecture

Dependency injection (Hilt/Koin)

Delivery ownership

Tools

GitHub Actions

Job description

Responsibilities

• Lead the Android engineering team — setting technical direction, defining architectural standards, and owning delivery across the Android roadmap.
• Write production Kotlin code and build UI in Jetpack Compose; remain hands‑on in the codebase and lead by example in code reviews.
• Own and evolve the CI/CD pipeline in GitHub Actions — builds, signing, automated testing, distribution to internal tracks and production, and release automation.
• Drive a healthy testing culture across the team — unit testing, integration testing, and end‑to‑end testing — ensuring meaningful coverage and reliable release confidence.
• Actively manage and reduce technical debt — track it, prioritise it against feature work, and make the case for it with stakeholders.
• Manage the performance and growth of engineers at all levels (junior through senior) — running 1:1s, setting clear expectations, giving direct feedback, and supporting career progression.
• Partner with Product, Design, QA, and Backend to scope, plan, and deliver features end to end.
• Own Android app performance, crash‑free rates, startup time, and Play Store quality — instrumenting what matters and acting on the data.
• Recruit, interview, and onboard Android engineers as the team grows.
• Stay current on the Android ecosystem and bring relevant changes (Compose updates, Kotlin language features, AGP, target SDK requirements, Play Store policy) into the team's practice.

Requirements

• 3+ years of experience in an Android Lead or Engineering Manager role, or significant senior‑level Android development experience with the ambition and capability to step into a leadership position.
• Proven track record of delivering and scaling consumer‑facing Android applications.
• Kotlin is a must — deep, idiomatic command of the language including coroutines, flows, and modern Kotlin patterns.
• Jetpack Compose is a must — production experience building and maintaining Compose‑based UI, including state management, navigation, and performance tuning.
• Strong experience with CI/CD in GitHub Actions — building, signing, testing, and releasing Android apps through automated pipelines.
• Demonstrable experience managing and reducing technical debt in a long‑lived codebase.
• Strong experience with unit testing and end‑to‑end testing on Android (JUnit, MockK/Mockito, Espresso, Compose UI testing, or equivalent).
• Proven experience managing the performance of engineers at all levels — setting goals, giving feedback, handling underperformance, and developing senior talent.
• Strong understanding of Android architecture patterns (MVVM/MVI, clean architecture, modularisation) and dependency injection (Hilt/Koin).
• Comfortable making pragmatic trade‑offs between delivery speed, code quality, and long‑term maintainability.
• Excellent written and spoken English and the ability to communicate clearly with both technical and non‑technical stakeholders.