About The Position

InPost is one of Europe's largest out-of-home delivery networks, with a consumer app used by over 10 million people. We are consolidating our separate market applications into OneApp: one application on one codebase for the whole InPost group across Europe and beyond, with Italy live and Iberia in flight. This Staff role exists to make that happen. It sits above and between teams rather than inside one, setting iOS technical direction across several mobile teams and working across domain boundaries with product, backend, platform, QA and the other mobile disciplines. It does not own a feature backlog. It owns the decisions every team's code has to live with.

Requirements

  • 8+ years production iOS.
  • Staff or principal scope across multiple teams, or technical lead of a whole iOS platform or several parallel iOS projects.
  • Multi-market or white-label apps.
  • Proven record of shipping a single codebase across several markets or brands, with the variant, configuration and release complexity that brings.
  • Mobile architecture: MVVM, Clean Architecture, SOLID. Unidirectional and composable architectures, Apple's own or TCA. Deliberate, justified choice per problem. Tuist is a plus.
  • Modularisation and contribution model: Feature extraction from a monolith into meaningful modules. Publishing the architecture, onboarding other domains, ownership and review rules for shared code.
  • Deep Swift and modern concurrency: async/await, structured concurrency, actors, Sendable, cancellation. Experience introducing Swift 6 strict concurrency into a large mixed codebase, and a credible phasing plan.
  • UIKit and SwiftUI: Deep understanding of both, and proven incremental migration between them.
  • Data layer: Deep understanding of databases and their migration processes.
  • Mobile security: SSL pinning trade-offs behind a CDN, App Attest, App Check, DeviceCheck, native OAuth, Keychain and secrets management.
  • Dependency and build systems: SPM and CocoaPods, hybrid setups, vendor-locked binary SDKs.
  • ADRs, RFCs and technical proposals. Circulated beyond the team: iOS Guild, other domains, Engineering and Senior Engineering Managers.
  • Business judgement: Separates what must happen now from what can wait. Quantifies technical debt and argues remediation in business terms. Turns Apple platform deadlines into a costed plan. Proven record of roadmaps delivered and debt resolved.
  • Whole-problem thinking: Looks beyond the technical problem to product intent, process and delivery. Works across the whole SDLC, not only inside the code.
  • Advanced AI-assisted engineering: Claude, Copilot or Grok hands-on a strong plus. Harness, agentic, loop and graph engineering. Sets verification rules for AI-generated code and measures the return.

Nice To Haves

  • CI/CD and release automation with quality gates: GitLab CI, Fastlane, TestFlight, multi-market and multi-scheme pipelines. Gates in practice: coverage thresholds, static analysis, performance and binary-size budgets.
  • macOS CI infrastructure: Runner provisioning, Xcode versions, simulator runtimes, signing and certificates, fleet reproducibility. On-premise, cloud or hybrid.
  • Appearance and orientation migrations: Liquid Glass, or a portrait-locked app taken to landscape and adaptive layout: iPad, foldables, resizable windows.
  • Test strategy at scale: XCTest and Swift Testing, snapshot testing, UI test architecture (Screen Objects, accessibility-id registries), flaky-test control.
  • Observability: Crash reporting, MetricKit, cold-start and time-to-home budgets.
  • Design System: Reusable components, accessibility compliance.
  • Apple Watch and watchOS, including companion apps and complications.
  • CarPlay, App Clips, notification and app extensions.
  • Code generation (SwiftGen, Sourcery).
  • Payments or fintech SDK integration.
  • Performance profiling with Instruments, metrics and tracing.
  • Familiarity with the Android ecosystem.

Responsibilities

  • Setting iOS technical direction across several mobile teams.
  • Working across domain boundaries with product, backend, platform, QA and other mobile disciplines.
  • Owning the decisions every team's code has to live with.
  • Defining standards others adopt, such as quality gates and testing policy.
  • Mentoring senior engineers.
  • Mediating technical disagreement and building consensus without line authority.
  • Reviewing for standards, performance, and security.
  • Deciding under ambiguity and owning the outcome.
  • Working closely with Staff engineers in other disciplines across the domain: Android, backend and QA.

Benefits

  • Fulfilling careers with a range of benefits for people and investing in providing training opportunities for their development.
  • Excellent working environment and flexible hours
  • B2B type of contract
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service