Senior Fullstack Engineer — Mobile Healthcare Platform arbeitnow Snke München · 10/2/2026

Primetime; München; Hybrid; EUR 90.000 - 130.000; Vollzeit

Benefits dieser Stelle

30 vacation days

Hybrid work model within Germany

Hybrid onsite workspace

Parking and cafeteria facilities

Zusammenfassung

Primetime is building an AI-native platform used in patient care. We seek an engineer who moves between backend, mobile, integration and platform work, owning architecture and API contracts. You will guide AI agents, design robust data models, and ensure end-to-end service quality across cloud and on-prem deployments.

Android parity and hospital integrations are on the roadmap. You’ll work in a fast-paced, regulatory-friendly environment, collaborating with clinicians and engineers to ship safe,

Qualifikationen

• Experience building and operating software in production across frontend/mobile and backend
• Ability to decompose problems into modules with clear contracts
• Familiar with agentic AI development tools and safe review practices
• Strong fundamentals in concurrency, networking, and API design
• Experience with CI/CD, automated testing, and observability in production environments

Aufgaben

• Move across the stack as priorities shift (mobile UI, backend services, APIs)
• Own architecture and data models, API contracts
• Direct AI coding agents and review outputs with rigorous standards
• Maintain readable code with consistent conventions and tests
• Ensure end-to-end service quality (observability, diagnosability)
• Work with clinical data and healthcare interoperability standards
• Produce technical documentation for regulated development processes

Kenntnisse

Cross-stack development

Software architecture

AI tooling workflows

Android/Flutter mobile

CI/CD and testing

Tools

Docker

Kubernetes

Jobbeschreibung

We are a startup building a platform that is in daily use during patient care, and our direction changes as we learn. The engineer we are looking for is comfortable with that: someone who moves between backend, mobile, integration and platform work as the product demands, and who picks up new technologies quickly because their strength is in engineering fundamentals rather than any one stack.
Right now that means, among other things, bringing our clinical mobile app to Android, evolving how our product integrates with hospital systems, and keeping our services dependable across cloud and on-premise deployments. Six months from now the list will look different, and you will help decide what is on it.
We build AI-native: agents write a large share of our code, and the engineer's job is to design the system, specify the work precisely, and keep the codebase in a state where both humans and AI tools can understand and extend it safely. Your engineering judgement is the product here.

• Move across the stack as priorities shift: mobile UI, backend services, APIs, hospital integrations, platform and deployment work
• Own the architecture of the parts you touch: module boundaries, API contracts, data models, and the decisions behind them
• Direct AI coding agents to implement against your specifications, and review their output with the same rigour you would apply to a colleague's pull request
• Keep the codebase legible for readers without context: consistent conventions, small well-named units, documented rationale, tests that express intent
• Own service quality end to end: automated testing, CI/CD, observability, diagnosability in production
• Work with clinical data and healthcare interoperability standards
• Produce the technical documentation and evidence required in a regulated development process

Type: Onsite

What you’ll do

We are a startup building a platform that is in daily use during patient care, and our direction changes as we learn. The engineer we are looking for is comfortable with that: someone who moves between backend, mobile, integration and platform work as the product demands, and who picks up new technologies quickly because their strength is in engineering fundamentals rather than any one stack.
Right now that means, among other things, bringing our clinical mobile app to Android, evolving how our product integrates with hospital systems, and keeping our services dependable across cloud and on-premise deployments. Six months from now the list will look different, and you will help decide what is on it.
We build AI-native: agents write a large share of our code, and the engineer's job is to design the system, specify the work precisely, and keep the codebase in a state where both humans and AI tools can understand and extend it safely. Your engineering judgement is the product here.

• Move across the stack as priorities shift: mobile UI, backend services, APIs, hospital integrations, platform and deployment work
• Own the architecture of the parts you touch: module boundaries, API contracts, data models, and the decisions behind them
• Direct AI coding agents to implement against your specifications, and review their output with the same rigour you would apply to a colleague's pull request
• Keep the codebase legible for readers without context: consistent conventions, small well-named units, documented rationale, tests that express intent
• Own service quality end to end: automated testing, CI/CD, observability, diagnosability in production
• Work with clinical data and healthcare interoperability standards
• Produce the technical documentation and evidence required in a regulated development process

What we’re looking for

• Several years of professional experience building and operating software in production, spanning both frontend or mobile and backend work, and a track record of changing roles or stacks when the product needed it
• Strong grasp of software architecture: you decompose problems into modules with clear contracts, think about dependency direction and ownership of state, and can explain why a boundary sits where it does
• Fluency with agentic AI development tools (for example Claude Code, Cursor, Copilot agents). You can describe a concrete workflow you use, where it breaks down, and which guardrails you put in place. You know which code you would never hand to a model unreviewed
• A specification and review mindset: you define "done" before starting, treat generated code as a hypothesis to verify, and notice missing edge cases and error paths
• Grounding in fundamentals that transfer across stacks: concurrency, data consistency, networking, API design, relational data. You have switched languages before and can judge whether unfamiliar code is idiomatic. Our backend is built with Python, Go, .NET and Rust; our mobile app is native iOS today, with Android coming next, likely in Flutter
• Mobile development experience, ideally Android or Flutter, including app lifecycle, background execution and offline behaviour
• Hands-on experience with containers, automated testing and CI/CD pipelines
• A structured, quality-focused way of working, comfortable in a regulated environment
• Professional English communication skills; German is a strong advantage

Nice-to-have

• Experience with healthcare interoperability standards such as FHIR, HL7, or interface engines like Mirth or Rhapsody
• Knowledge of DICOM and medical imaging workflows
• Experience developing regulated medical software or working in other safety-critical industries
• Experience deploying software in customer-managed or on-premise infrastructures
• AWS experience

Why Snke

• A supportive, international team connected by shared values and a culture of trust
• Meaningfulresponsibilitieswithalastingimpactonglobalhealthtech,improvingmedicaldecisionsandpatientoutcomes
• 30vacationdays,plusDecember24thandDecember31st
• FlexibleworkinghoursandahybridworkmodelwithinGermany
• Bikeleasingviaourpartner BikeLeasing
• Parkinggarageandsecureundergroundbikestorage
• Subsidizedcompanyrestaurantandin-housecafé
• UrbanSportsClubmembershipwithemployercontribution
• Regularafter-work,team,andcompanyevents
• Centrally located, modern workspace with a 212 m² rooftop terrace

Contact person

Tatjana von Freyberg

This overview was written from the original listing to help you understand the role. Always confirm the specifics on the employer’s application page.