Staff Software Engineer, Browser Extension & Persistence

You're the owner of Tactiq's capture and persistence reliability domain: the extension-to-backend contract, the transcript durability model, observability, rollout safety, and the engineering mechanisms that keep capture reliable as meeting platforms change. THE ROLE This role lives in the browser and the meeting platforms, and a lot of it is investigative. Its centre of gravity is the browser extension and the capture path across Google Meet, Zoom, and Teams, but it spans the extension-to-backend API and the persistence path through durable storage. Most systems you will work with don't document how they really behave, so you work it out from evidence and build capture mechanisms that survive their changes. You own that domain end-to-end, and the reliability bar you set here is inherited across the product. WHAT YOU'LL ACTUALLY DO DAY-TO-DAY - Frame the problem: clarify ambiguous product and system problems with product: the user or system failure, the success metric, and the smallest reversible path to learn. - Design and ship: the extension and capture pipeline across Meet, Zoom, and Teams, and the save path that gets each transcript into storage. Done means rolled out and observable, and either moving the metric or clearly reverted, not just merged. - Run experiments: change one thing, then measure (Datadog for production behaviour, Mixpanel for user behaviour), and revert or iterate. - Raise the bar: review designs and code, mentor engineers, and reduce single-person dependencies. - Reliability: a dropped capture is a meeting a user never gets back, so you own reliability by design for this domain: SLOs, prevention, and durability. REQUIRED EXPERIENCE - Deep experience owning user-facing systems end to end, ideally a browser extension (MV3) or a comparable constrained client: service workers, cross-context messaging, permissions, WebRTC, and the failure modes that only show up in the field. - Strong TypeScript/Node, or the ability to ramp fast in a TypeScript-heavy codebase. - System design across APIs, data flows, reliability, and observability. - Sound judgment on durable storage and data modelling: you design persistence that stays correct and fast as data grows. We use Firestore; the judgment matters more than the specific store. - Product judgment: connecting technical work to activation, retention, quality, cost, or reliability, and using telemetry and product metrics to guide iteration. HOW WE WORK Under the hood: a TypeScript monorepo — Node.js/GraphQL backend with Temporal, Firebase, Elasticsearch, a React web app, a Chromium extension, and a native macOS app. We ship in small, reversible slices, often many times a day; bigger bets land as stacked PRs, not one big drop. TO APPLY: Send us at engineering2026 at tactiq io a brief note (1-2 sentences each) covering: 1. Why Tactiq? 2. Describe the last feature you built or significantly improved. What was your approach? 3. What was the result of that change?