Senior Software Engineer, Rust

Responsibilities

• SDK Observability Pipeline: Design, build, and maintain the client-side telemetry system in the Rust core. Metrics, structured logging, and tracing that work across all platforms the SDK targets, with configurable verbosity, sampling, and export.
• Support Bundles: Evolve our current log bundle system into comprehensive support bundles that capture device state, recent telemetry, configuration, and diagnostic metadata — giving our support engineers (and customers) the context they need to resolve issues quickly.
• Logging System Performance: Reduce the I/O and compute overhead of our current logging infrastructure. The SDK's observability should be near-invisible to the host application's performance.
• Rust SDK Ownership: Own feature development and customer support for our Rust SDK, including direct engagement with customers debugging production integration issues.

Requirements

• Systems-level Rust experience (3+ years) — You've built production-grade Rust libraries or systems. You're comfortable with unsafe, FFI boundaries, async runtimes, and reasoning about memory layouts and performance at the microsecond level.
• Observability and telemetry design experience — You've designed or significantly contributed to instrumentation, logging, metrics, or tracing systems. You understand the tradeoffs between signal granularity and overhead, and you've thought about what makes telemetry useful, not just voluminous. Experience with OpenTelemetry is a strong plus.
• Library/SDK development mindset — You've built software that other developers consume as a dependency. You think about API design, backward compatibility, developer experience, and the principle that your library is a guest in someone else's application.
• Cross-platform and FFI fluency — The Rust core ships via FFI to Swift, Kotlin, C#, JavaScript, and more. You need to be comfortable working across language boundaries and understanding how your Rust code behaves when called from a different runtime.
• Strong written communication — We're an async-first, distributed team. Your design docs, RFCs, and code reviews are your primary communication tools. You can explain complex systems decisions clearly to both engineers and non-technical stakeholders.
• Customer empathy — You're willing to engage directly with customers, debug production issues on their devices, and translate field experience into engineering improvements.

Nice to Haves

• Android/Kotlin or mobile platform experience
• Experience with embedded databases, data sync, or offline-first architectures
• Background in developer tooling or developer experience teams
• Networking fundamentals: TCP/UDP, Bluetooth Low Energy, mesh networking
• Open-source contributions in relevant ecosystems (Rust observability, FFI tooling, cross-platform SDKs)