Senior Android Engineer CI/CD - (Freelancer)

DUDE CHEM; Berlin; Vor Ort; EUR 96.000 - 165.000; Vollzeit

Zusammenfassung

voize is seeking a Freelance Senior Android Engineer to own and evolve our Android app. The role focuses on building features with Kotlin/Multiplatform, ensuring a reliable CI/CD pipeline, and shipping to real users. We welcome candidates from FR, DE, or England, who can travel to Berlin occasionally.

The contract starts at three months and may extend. Ideal candidates have deep Android experience, strong Gradle knowledge, and hands-on CI/CD with GitLab.

Qualifikationen

• Several years building Android apps with Kotlin and Compose.
• Shipped to real users, not just CI.
• English fluency (C1) required; German a plus but not required.

Aufgaben

• Own the health of our mobile CI/CD pipeline end to end.
• Unblock a broken master: triage failures, debug the app.
• Define healthy CI with SLOs and gate decisions for jobs.

Kenntnisse

Android development

English (C1)

Kotlin

Kotlin Multiplatform

Compose

Tools

Gradle

GitLab CI

Appium

Jobbeschreibung

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.

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

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 that reads as an unusually clear mandate with visible impact on every engineer in the company, we should talk.

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

Evidence from the posting

German required "C1"

Fully remote "open to candidates based in France, Germany, or England, with a willingness to travel to our Berlin office from time to time"