JobCubby JobCubby
Sign up
voize

Senior Android Engineer CI/CD - (Freelancer)

voize Berlin, Germany

Software Development · 51-200 employees

14 h ago
Remote android Senior (5-10 yrs) Contractor Germany
Create a free account to apply — email only, no card. You can also save this posting or score it against your profile with AI.

About the role

You will own the end-to-end health of the mobile CI/CD pipeline, including debugging failures and optimizing build performance. Additionally, you will define SLOs for CI health and implement strategies to reduce test flakiness and improve developer productivity.

What they look for

Android Development Kotlin Jetpack Compose CI/CD Gradle GitLab CI Kotlin Multiplatform Appium E2E Testing Build Optimization Debugging System Architecture Mobile Development Test Automation

Requirements

The role requires several years of experience building Android applications with Kotlin and Compose, along with deep knowledge of Gradle and CI/CD pipelines. Candidates must be fluent in English and comfortable working with complex, multi-module build systems.

Benefits

Travel expenses covered

Full description

🎤 Why voize? Because we’re more than just a job!

At voize, we believe the greatest gift to frontline workers is time - time to care, connect, and be present. Today, that time is lost to admin work that pulls nurses away from what matters most: people.

 

💡 Your Mission

As a Freelance Senior Android Engineer, you'll take ownership of building and evolving our Android application, creating features that have a real impact on the daily lives of healthcare professionals. We are open to candidates based in France, Germany, or England, with a willingness to travel to our Berlin office from time to time (travel expenses covered). The initial contract is for a minimum of three month

  • Own the health of our mobile CI/CD pipeline end to end: ~70 Kotlin Multiplatform jobs, from lint to end-to-end tests to store release
  • Be the person who unblocks a broken master: triage the failure, debug the app itself (not just the pipeline), get 40+ engineers moving again
  • Attack the structure, not the symptoms: define what healthy CI means for us as actual SLOs, decide which jobs to keep, combine or gate the rest, and take our P95 pipeline from ~90 minutes to something nobody complains about
  • Make test flakiness visible and owned — dashboards, quarantining, a clear owner per failing test
  • Leave a trail: what you tried, what worked, and what already exists, so we build the muscle into our dev culture

YOUR SKILLSET – WHAT YOU BRING TO THE TABLE

  • Several years building Android apps with Kotlin and Compose — you've shipped to real users, not just to CI
  • Deep Gradle knowledge: multi-module builds, build caching, task/configuration avoidance, and a real answer to "why does this build take 20 minutes?"

You've owned a CI/CD setup before (GitLab CI ideally): runners, caches, artifacts, change-based job gating

  • Comfortable in the unglamorous layers: emulators, macOS/iOS build agents, Appium/E2E flakiness, memory-hungry Kotlin compile jobs
  • Kotlin Multiplatform and/or iOS exposure is a plus, but most of the work feels like Android
  • You speak English fluently (C1) — German is a plus but not required

WHAT YOU'RE WALKING INTO ▎ We're not going to pretend this is greenfield. Our pipeline is ~70 jobs deep, P95 sits around 90 minutes, our two end-to-end suites fail ~16–18% of the time, and one test job once failed 600 runs in a row before anyone noticed. There's a #ci-alerts channel that needs someone who wants to be in it. If that reads as a mess, this isn't your role. If it reads as an unusually clear mandate with visible impact on every engineer in the company, we should talk.

 

✨ Ready to talk? Apply now! 🚀

We look forward to your application and can’t wait to meet you – no matter who you are or what background you have!

Similar roles