Description du poste
You may not meet every requirement, and that’s okay. If this role excites you, we’d love you to raise your hand for what could be a truly career-defining opportunity You have worked on performance-sensitive code (startup time, memory, battery, network efficiency, background execution limits) and make pragmatic tradeoffs You use AI tools as a natural part of your engineering workflow, for exploration, code review or reasoning through design tradeoffs, and you are thoughtful about where they help and where they don’t You take a user-centered approach, and you build understanding of customers’ context and goals so you build the right thing You have deep native mobile engineering experience on Android (Kotlin/Java) or iOS (Swift/Obj-C). We are building Android first, so Android depth is a priority for the first hire. We are hiring across both platforms, and we do not expect you to be an expert in both, but you are willing to learn and contribute across platforms over time You are comfortable working in a remote-first, globally distributed company. Communication is key, and you write and speak clearly in English You have built or maintained mobile SDKs or platform libraries used by external developers, and you care about developer experience, API design and safe upgrade paths You are comfortable owning a product from 0 to 1 in ambiguous problem spaces. You can break large problems into increments and work autonomously You are collaborative, friendly, kind and respectful. We operate by consensus: you can contribute, disagree constructively, and commit to the team’s decision You are thoughtful about privacy and security on user devices, including handling of sensitive data You are comfortable with media and rendering pipelines on mobile: capturing screen content, working with frames or bitmaps, and encoding or handling video Prior work on mobile session replay, screen recording, or sampling for mobile telemetry Experience with video encoding (H.264, MediaCodec, AVFoundation) or on-device masking and redaction Familiarity with rrweb or web session replay concepts Experience with OpenTelemetry, crash reporting libraries or other observability open source Experience with cross-platform frameworks (React Native, Flutter) or building native bindings and bridges Experience with observability or debugging tools (Grafana, Datadog, New Relic, Sentry, etc.) Familiarity with mobile privacy, consent and platform policy requirements Experience with Go or TypeScript, since the work crosses into our ingest and player
We are building Mobile Session Replay: a way for teams to see what users actually experienced in their iOS, Android, Flutter and React Native apps, inside Grafana Cloud Session Replay connects frontend signals to session-level evidence, so engineers can investigate production issues faster and with more confidence. Web replay is already available publicly. Mobile replay extends the same story to native apps as part of our Digital Experience Monitoring (DEM) strategy We are starting with Android. A working prototype already exists, and you will help turn it into a product customers can trust. The plan is to push ahead from there: iOS next, then our Flutter, React Native and OpenTelemetry mobile SDKs, so customers get a consistent replay experience across platforms As a company we are remote-first and global, we embrace people of different experiences and backgrounds to build diverse teams where every person brings a new perspective to the software. We are looking for Staff Mobile Engineers who are passionate about working with data and providing seamless experiences for our customers to join our growing team! As a Staff Mobile Engineer you will be the technical lead for mobile capture and replay, working across the device, the ingest path and the player. Specifically, you will: Own the on-device replay library end to end, starting with Android and extending to iOS Make privacy a default, designing masking and consent controls so sensitive data never leaves the device Keep the overhead low and measure it on real devices, protecting startup time, UI responsiveness, battery, memory, network use and disk, and profiling the impact of capture and masking while the app is actively being used. Give customers controls to trade fidelity against cost Build the integration layer so customers do not copy demo glue code: adapters that tie replay to the active RUM session, sampling decisions and screen or navigation changes Work across the stack with Frontend and Mobile Observability teams on the capture, upload and storage pipeline, session inactivity handling, the timeline player and the mobile sessions and replay experience in Frontend Observability. Evaluate the format and API tradeoffs rather than assuming the current prototype approach is final Define quality and compatibility: automated tests, CI, device and OS coverage, and backwards-compatible upgrade paths for an SDK that customers cannot easily update Engage directly wi