Senior iOS Engineer – Learning Experience (all genders)
Babbel is hiring a Senior iOS Engineer – Learning Experience (all genders) for a remote role open to applicants in Germany. Level rates it ; you can apply on Babbel.
Level's read on this job
- On Level's scale, this software engineer role is Works on AI ●●●○: the daily work is on AI products, without building the model.
- This is listed as a remote role.
- The posting mentions Claude and Claude Code among its tools and skills.
- Level classes it as a senior role.
- Babbel has 10 other open roles on Level.
AI in this role
About Babbel Labs
Babbel Labs is building the future of language learning. We are an AI-first, independent company within the Babbel group, based in Berlin. Our teams bring AI, research and product together to ship experiences that set a new standard for how people learn.
The role
We are building Babbel's core learning experiences, from the learning path and exercise player to real-time speaking and conversation practice. This role helps change the future of language learning within our Learning Experience teams. You own the experience end to end: it ships as a distributable Swift package consumed by Babbel's main iOS app, and you follow it there, through integration points, A/B experiments, and rollout.
This is a hands-on senior individual-contributor role with team-level scope. You will work closely with product and engineering managers, designers, subject matter experts, and cross-platform engineers. And you will do this the Labs way: AI coding agents are a first-class part of how we design, build, test, and review.
How you'll make an impact
Take part in all product development phases: discovery, prototyping, proposing solutions, implementing, reviewing, testing, and deploying learning experiences.
Own the engineering side of our feature workflow: shape the PRD together with product, then pick it up. Write the technical spec, agree Interface Contracts with backend and partner teams, slice the backlog, and build.
Build quick prototypes to de-risk product ideas. The learnings feed the product, even when the code doesn't.
Design and evolve the public API of our Swift package with deliberate versioning and breaking-change discipline, and land it in the main app through integration points, A/B experiments, and rollout.
Collaborate closely with product managers, designers, and other cross-functional teams to define and implement features that enhance how learners progress through their learning path, exercises, and speaking practice.
Maintain and proactively improve the technology stack, build system, and the AI-agent conventions (skills, project rules, documentation) the whole team relies on.
Share what you learn: technical documentation for core features, and knowledge actively passed on to colleagues.
Your skills and qualifications
5+ years of experience building scalable iOS applications using Swift.
An AI-first mindset, which is a strong must for us. You have actively embraced AI coding tools in your own work, not just autocomplete but directing agents through real feature work and critically reviewing what they produce, and you treat prompts, skills, and project conventions as engineering artefacts maintained like code. Deep experience with our specific agent stack isn't required. Demonstrated adoption and genuine enthusiasm are.
Strong, up-to-date Swift, including Swift 6 strict concurrency (actors, Sendable, isolation) and structured concurrency.
Deep SwiftUI experience and a solid grounding in the Apple ecosystem and Human Interface Guidelines. You think in state-driven UI and know where the framework's sharp edges are.
Strong opinions on state management and testable architecture, experience with unidirectional-data-flow architecture, and willingness to go deep on ours.
Testing as a first-class habit: deterministic, exhaustive unit tests with controlled dependencies, and snapshot tests where the UI is the contract, not coverage theatre. You also bring the CI/CD discipline to keep them green.
Experience designing module boundaries, frameworks, or SDKs that other teams consume, ideally as distributable Swift packages, and the API-stability discipline that comes with it.
Experience designing or consuming evolving JSON APIs and collaborating with contract-first backend teams.
An eye for good architectural decisions based on feature requirements, and knowledge of how to balance technical debt against delivery speed.
Comfort with ambiguity and fast iteration: directions evolve as we learn, and prototypes are a tool, not a deliverable.
Clear, concise communication, an open mindset for feedback, and enjoyment in working closely with design and product in a lean environment.
Fluency in written and spoken English.
Nice to have
Hands-on experience with The Composable Architecture and the Point-Free ecosystem (swift-dependencies, swift-sharing).
Hands-on experience with agentic coding setups (e.g. Claude Code): agent skills, MCP servers, CLAUDE.md-style project conventions.
Experience with Tuist or other project-as-code tooling at scale (modular workspaces, binary caching).
Experience with Swift Testing (the modern successor to XCTest).
Experience with real-time client features, such as live audio capture, streaming over WebSocket/WebRTC, and low-latency interactions.
Comfort navigating a legacy RxSwift/MVVM-C codebase. You'll help integrate our package into Babbel's main iOS app while it migrates to the new stack.
Experience working in language learning, education technology, or consumer subscription products.
Ways of working
This is a hands-on individual-contributor role in our Learning Experience teams, which work agent-first. Our stack: Swift 6.2 with strict concurrency, SwiftUI, The Composable Architecture with the Point-Free ecosystem (swift-dependencies, swift-sharing), Swift Testing with exhaustive state assertions, and project-as-code with Tuist (modular workspace, binary caching). We ship our features as a distributable Swift package built with multiple consumers in mind, today Babbel's main iOS app. We work trunk-based with Conventional Commits driving automated versioning, plan in Linear (discovery → PRD → spec → issues), and build AI-first: coding agents, a curated skill library, and conventions good enough that even non-engineers on the team run and prototype in the app.
Success in this role is measured by the quality and impact of the learning experiences you ship, the health of the codebase and its public API, and the knowledge you share with your team and with iOS engineers across Babbel. It is remote and Berlin-friendly.
Diversity at Babbel
As part of our ongoing journey towards building a diverse, equitable, and inclusive company, we welcome everyone to apply, especially individuals who are underrepresented in tech. We are a learning company, inside and out, and we encourage you to apply even if you do not fit all the technical requirements — all candidates are assessed based on skills, qualifications, and our business needs. Please state your pronouns in your application, and let us know if you'd like to be addressed by a name other than the one appearing on your official documents. If you have a disability or special need, feel welcome to inform us so we can provide proper assistance in the application process.
How we rate this
Senior iOS Engineer – Learning Experience (all genders) at Babbel rates 66 out of 100 for how much of the daily work is AI. That makes it Works on AI (AI Level 3 of 4). The level is about AI in the job, not seniority.
Works on AI. The daily work is on AI products, without building the model.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Pay
- Typical software engineer job
- $168k
This posting doesn't list pay. Use the typical software engineer figure when pay comes up. See software engineer jobs
Questions you could be asked
- What's a project where you used Claude hands-on?
- Walk me through how you've used Claude Code in your day-to-day work.
- Describe a typical day in a role like this one: which parts run through AI directly?
- If you removed AI from this role, what would be left, and how do you decide what still needs a human?
Adapt your resume
- List these exact terms on your resume: Claude and Claude Code. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Show where AI is part of your daily process, not a one-off project. This role expects it to be a running habit.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. You get your review by email within 24 hours.
Get new remote software engineer jobs (Works on AI ●●●○ or higher) by email
One email a week with the new remote software engineer jobs (Works on AI ●●●○ or higher), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that work on AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step