Staff Software Engineer, Browser Extension & Persistence
Sydney, New South Wales, AustraliaAll locationsSydney, New South Wales, AustraliaAuckland, New Zealand Remote
Salary not listedJobFig found this opening at its original source and checks that it remains available.
About 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. Tactiq is growing fast, and so is the set of problems where the right answer isn't obvious in our context yet. You own the how (the technical approach and execution) outright; you shape the what (priorities and scope) with product; and review, automated and human, is a quality gate that catches defects, not an approval gate on your calls. This role is for you if you like making a critical, already-in-production system more reliable and faster, want to own a domain end-to-end, and expect to grow your remit from it into more product areas over time. It's probably not if you're after greenfield, want a team to manage, like tasks that arrive well-defined, or would be frustrated building against platforms that change without notice. you lead one ambiguous problem from framing to production rollout, including instrumentation and iteration.
What you'll bring
- Deep experience owning user-facing systems end to end
- Strong TypeScript/Node, or the ability to ramp fast in a TypeScript-heavy codebase.
- System design across APIs, data flows, reliability, and observability.
- You don't need equal depth across browsers, backend, and infrastructure, but you reason across the boundaries and go deep where a project needs it.
- 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.
- Real-time or distributed systems at scale.
- Native desktop experience, macOS or Windows (an adjacent capture surface).
- 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.
- You don't need prior experience with every part of the stack, but you should be comfortable becoming productive in a TypeScript-heavy system.