Tactiq is a rapidly growing Sydney-based, remote-first SaaS startup

Tactiq leverages generative AI to capture and extract valuable insights from conversations. With over 1,000,000 users and teams relying on our platform, we help process more than 3 million meetings every month. We foster a collaborative culture built on rapid feedback, empowerment, and openess.

Explore exciting career opportunities at Tactiq, where innovation meets collaboration.

Staff Software Engineer, Product Surfaces

Location

Sydney; Auckland

Employment Type

Full time

Location Type

Remote

Department

You own a meaningful part of Tactiq's product.

You take incomplete product direction and turn it into something real: make the missing product and technical decisions, build the first comprehensive version, get it into production, learn from what happens, and keep owning it as it grows.

Your initial area could be our MCP and AI-assistant experience, native desktop/mobile apps, AI Dictation, or another important product surface. We care more about finding the right person than matching someone to a narrowly predefined charter.

The Role

Product might give you a direction, an opportunity, or a rough prototype. They will not give you a detailed specification covering every state, integration and edge case.

That's part of your job.

You should naturally notice the surrounding product system: onboarding, permissions, failure states, analytics, rollout, observability, billing, supportability and how we'll know whether it worked.

Then you build it.

This is a deeply hands-on role. We expect you to ship substantial product areas through your own judgement, engineering ability and effective use of agents.



You don't need a team assigned underneath you to have significant impact.

And once something ships, it remains yours. You own its production behaviour, improve it, discover opportunities within it and make it easier for agents and other engineers to contribute safely.

Over time, you should also make your area require less continuous human attention: recurring investigation, implementation, testing and operational work should increasingly become part of the system itself.

What You'll Actually Do

Own a product area end-to-end: users, architecture, metrics, economics, failure modes and production behaviour.

Turn intent into product: independently close the many decisions between a product direction and something users can rely on.

Shape the what as well as the how: discover problems and opportunities within your area instead of waiting for them to be enumerated.

Build across boundaries: frontend, backend, APIs, data, infrastructure, native clients, AI systems or third‐party platforms - wherever the outcome takes you.

Use agents as execution capacity: delegate implementation, investigation and testing aggressively while retaining responsibility for judgement and results.

Increase safe autonomy: improve context, tooling, evals, observability and guardrails so more useful work can happen without constant human supervision.

Own production: measure what happens,



investigate failures and iterate based on evidence.

Finish things: reduce ambiguity, resist unnecessary scope expansion and get useful results into users' hands.

What Makes This Role Different

We're not looking for someone who needs the problem boundary supplied to them.

Given incomplete intent, you can work out what actually needs to be solved and make sensible decisions across product and technical concerns.

And success isn't simply doing more work personally. As your area matures, routine work should increasingly stop requiring your attention.

Your leverage should grow over time.

Required Experience

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 contemporary 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.<

📌 Staff Software Engineer, Product Surfaces (Perth)
🏢 Tactiq
📍 Perth