Native / Desktop Engineer

Native / Desktop Engineer

The role. Build Desktop Intercept — the native Windows driver and app that acts as a virtual mic/speaker, replaces audio in real time, and (Phase 1 Phase C) reads the DOM and drives Computer Use. This is the hardest engineering on the platform and the deepest moat. Everything you build feeds a high-efficiency, event-driven, low-latency distributed platform — voice, desktop, intelligence, and AI combined — so you think in latency budgets, throughput, and efficiency, not just features. Startup environment: 1-week sprints, Friday demos, fail fast and move forward.

What you'll own. Windows native driver (WASAPI, virtual audio devices, kernel-adjacent hooks) · real-time bidirectional audio routing · the user-space app (audio router, DOM scraper, MCP server) · the desktop-to-cloud path onto the event bus (NATS-class, WebSocket) under a sub-300ms budget · AV co-existence and mass-deployment · your committed timelines.

Who you are. Self-starter, hacker, grit. You consider yourself exceptional at the systems level and can show it. You love new technology, adapt fast when it changes, demonstrate ideas with working code, and use AI tools daily to multiply your velocity. Team player who makes and hits committed timelines. Loves solving the problems nobody else can — and winning.

Requirements

• 8+ years systems / native development; shipped a Windows desktop agent at real scale (>10k seats) with audio.

• Strong C/C++ — mandatory. Strong Go for the service side — mandatory.

• Comfortable building and interacting with drivers — virtual audio devices, virtual microphones/speakers, WASAPI / Core Audio, kernel-adjacent hooks.

• Real-time audio pipelines under a sub-300ms budget — buffering, resampling, drift, glitch-free capture/playback.

• Understands high-efficiency systems end-to-end — event-driven architecture, pub/sub, WebSocket streaming, and what state, race conditions, and locking mean at the native layer (lock-free audio buffers, real-time threads, priority inversion).

• macOS / Linux native experience is a huge +++++ — cross-platform desktop is where this goes next.

• Browser / DOM internals and process injection a strong plus (Phase C).

• Enterprise mass-deployment craft — MSI/installer engineering, silent deploys, fleet upgrades across 10k+ locked-down seats.

• Driver/code signing and AV/EDR co-existence — WHQL, EV certs, and staying invisible to CrowdStrike-class agents without tripping them.

• Crash-dump and telemetry discipline — WinDbg/minidumps, symbolized crash reporting from the field; you debug machines you'll never touch.

• Security posture — least-privilege service design; this app hears customer audio and reads screens, so it must be provably tight.

• A master debugger at the systems level — kernel logs, crash dumps, audio glitches, AV interference; you see it.

• SIP / RTP a strong plus. Mid-tier or better hands-on AI-in-product experience a plus (the desktop app hosts an MCP server and drives Computer Use).

Originally posted on Himalayas