Tactiq - Staff Software Engineer, Product Surfaces

• Strong evidence of owning important user-facing products or product areas end-to-end. • A history of turning ambiguous or incomplete ideas into production systems. • Strong product judgement and the ability to make decisions without continuous specification or approval. • Broad technical judgement across system boundaries, with the ability to go deep where needed. • Strong modern software engineering fundamentals and production debugging ability. • Substantial hands-on use of AI coding agents as part of normal development. • Familiarity with modern AI application patterns such as tool calling, MCP, agents, evals, context and permissions. • Evidence that you've created leverage around yourself through automation, tooling, observability or systems that eliminated recurring manual work. • The ability to learn unfamiliar domains quickly. • This Is Probably Not For You If • You want work to arrive as well-defined tickets. • You primarily want to advise on architecture while others build. • You consider the job finished when the code merges. • You need a team underneath you before you can have substantial impact. • You love prototypes but lose interest in production ownership. • You prefer staying inside a narrow technical speciality. • How We Work • Under the hood, a TypeScript monorepo: Node.js/GraphQL with Temporal, Firebase, Elasticsearch, React, a Chromium extension, native macOS and Windows apps, and an increasing number of AI and agent-driven systems. • We ship in small, reversible changes, often many times a day. Tests, evals, observability, feature controls and automated review help us move quickly without outsourcing engineering judgement. • We use Linear, Mixpanel, Datadog, Claude Code, Cursor and whatever else earns its place. • We're also deliberately moving important context out of individual heads and into code, documentation, skills, telemetry, evals and explicit constraints so both humans and agents can work effectively across the system. • We handle sensitive meeting data, so privacy, permissions, access control and safe AI behaviour are first-class product requirements. • What Success Looks Like • In your first month, you're productive enough in the product and codebase to ship useful production changes safely. • In your first month • Within three months, you've taken a materially ambiguous problem from product shaping through implementation, rollout and observation without requiring detailed specification. • Within three months • Within six months, there is an important product area that is clearly yours. You're independently discovering and closing important problems within it. • Within six months • Over time, that area becomes increasingly self-observing and easier to operate. Routine problems require less manual attention, agents can safely make more progress, and your time shifts toward novel opportunities and difficult judgement calls. • Over time • Growth From Here • One path is to expand your technical and product scope: identify new problem spaces, establish new product surfaces and govern a larger part of the product. • An alternative path is to expand through people and organisational capability: develop exceptional engineers, identify capability gaps, hire great people and increase the leverage of the engineering organisation. • Neither path requires giving up being technical.