Technical Product Manager

Your work will help shape the business logic layer that powers our product — workflows, task runners, state machines, rules engines, and orchestration.

• Owning PRDs and RFCs for larger features, and maintaining a clean, structured Product documentation folder that clearly captures intent, scope, and decisions
• Mapping logic flows: outlining step-by-step behaviors, edge cases, and decision paths
• Modeling state: defining key states, transitions, and triggers (including retries and failure modes)
• Capturing validation rules: both field-level and conditional, across sync and async flows
• Handling exceptions: specifying how to surface, log, or recover from system errors
• Tracing data dependencies: documenting inputs, transformations, joins, and sync logic across services
• Acting as a primary contributor to API documentation and helping ensure our Postman collections are accurate and aligned with shipped behavior
• Serving as first eyes on Sentry reports across repositories and actively monitoring feature releases for regressions
• Acting as an active PR reviewer, helping protect us from sub-optimal code and future technical debt

Your job is to remove blockers before they slow things down, making sure problems are well-defined before they reach engineering, and helping ensure the product we ship is as useful and reliable as possible for our users.

You’ll also help ensure our product help and API documentation remains up-to-date, structured, and reflective of the current system. Where documentation is missing or fragmented, you’ll take initiative to improve it.

This role will see you work along the following tracks:

• Translating complex ideas and customer needs into structured and well documented engineering tickets
• Turning Slack discussions into actionable GitHub tickets with clear ownership and next steps
• Know when to push for answers and when to leave things alone
• Maintaining clean, well-scoped backlogs with clear labels and status comments so Makers can focus on building
• Helping prioritize the ticket queue to maximize velocity and impact, and setting clear weekly Maker plans — what’s being worked on and why