Requirements:

You’re a motivated self-starter with a bias toward action and the ability to run with poorly defined scopes. You can operate autonomously while being highly collaborative.
Strong mobile engineering experience (one or both): iOS (Swift/Obj-C) and/or Android (Kotlin/Java).
Demonstrated experience building or maintaining mobile SDKs, platform libraries, or other developer-facing platform code used by external developers.
Experience working with performance-sensitive code (startup time, memory, network efficiency) and making pragmatic tradeoffs.
Familiarity with OpenTelemetry (instrumentation, SDKs, collectors) or experience contributing to/maintaining OTel SDKs or similar telemetry libraries.
Excellent written and verbal communication
Comfortable working in a fully remote, globally distributed team.
Coachable, customer-focused, and passionate about developer experience, you can do more than code: you write docs, mentor others, and shape roadmaps.
Pragmatic and comfortable navigating ambiguity: you prioritize progress over perfection and iterate quickly based on feedback.

Nice to Haves:

Contributions to OpenTelemetry, crash reporting libraries, or other observability OSS.
Experience with cross-platform frameworks (React Native, Flutter) or building native bindings/bridges.
Experience with mobile security, privacy, or platform integration challenges.
Prior work on crash aggregation, session replay, or sampling for mobile telemetry.

Build and evolve mobile instrumentation SDKs for iOS (Swift / Obj-C) and Android (Kotlin / Java), prioritizing performance, stability, and a great developer experience.
Design and ship SDK features such as session tracking, crash reporting, sampling strategies, automatic context propagation, and OpenTelemetry integrations.
Own projects end-to-end.
Break large, ambiguous problems into incremental deliverables: design modular solutions, ship MVPs, gather feedback, iterate quickly.
Ensure quality: automated tests, CI, documentation, and smooth, backwards-compatible upgrade paths.
Collaborate cross-functionally with backend, frontend, product, and solutions engineering to ensure cohesive end-to-end observability workflows.
Engage with the open-source community: review PRs, discuss design proposals, and help guide external contributors.
Mentor teammates, participate in technical design discussions and help shape the mobile observability roadmap.