Associate Product Manager

Tint

4d•$79,475 - $110,000•Remote

About The Position

Tint enables SaaS platforms and marketplaces to unlock growth and improve profitability through embedded insurance. We offer plug-and-play and white-labeled integrations, equipping brands we partner with a sophisticated mix of technology infrastructure, services, and deep industry expertise. Embedded insurance can transform insurance from a product bought separately to a feature of brands consumers love and we are on a mission to make that happen. Happy Tint customers include Turo, Deel, uShip, Guesty, Neighbor, BabyQuip, and CitizenShipper, among others. We've raised $30M and are backed by world-class investors such as Y Combinator, QED, Deciens, Nyca, Plug and Play, WIN, Soma Capital, and Pioneer Fund. We're hiring a Associate Product Manager to support one of our largest and most operationally complex product programs. You'll report to the Staff Product Manager who owns the program, and work day to day with a small pod of engineers plus ops, data, and partner-facing teammates. This role sits at the operational core of the product. You'll support the product and the projects moving through it on the operational side: watching the data behind it, tracking the issues that come in, QA'ing what engineering builds against its acceptance criteria, and keeping everyone, both internally and on the partner side, current on what changed and why. This is a first product role. You don't need to know our domain, our partners, or our stack, and we're not expecting prior PM experience or a technical background. We're looking for someone curious enough to dig, disciplined enough to close the loop, and unintimidated by unfamiliar systems. The rest we will teach you.

Requirements

Evidence you've worked somewhere with real stakes and standards, whether that's a substantive internship, a first job where you owned something, or time in support, QA, ops, coordination, or analytics.
Curious, and knows when to stop. You pull the thread when something doesn't add up, and you ask what something actually means rather than nodding along. Much of this work happens around people who've been here years and talk in shorthand — asking costs you nothing here, guessing wrong three weeks later costs everyone. The other half matters just as much: recognizing when you've hit the edge of what you can resolve alone, and escalating cleanly instead of disappearing into an investigation for two days.
Thinks in workflows, not screens. The expensive gaps are the ones nobody considered until QA: the state that only shows up on a renewal, the case where something gets cancelled halfway through, the step that quietly assumes someone else already did their part. You read a spec and trace the process end to end, then ask what happens when it doesn't go that way. You're also often the last person to see something before a user does, so you notice when a flow is confusing or an error message reads like it was written for an engineer rather than a customer - and you say so, even when the ticket technically passes.
Works out the how. You'll be told what matters this week. You won't be told what the item actually requires, who needs looping in, or what has to be true before it's done. You work that out, come back with questions rather than a blank stare, and notice the thing that's been sitting untouched for a week without anyone pointing at it. When the tooling doesn't do what you need, you find another way to get the answer.
A creative problem solver. A lot of this work has no established playbook yet. When the tooling doesn't do what you need, you find another way to get the answer.
Unintimidated by technical things. You don't need to code or have a technical degree. You do need to be the kind of person who opens the dashboard, reads the spec, clicks into the log, and works out what it's telling you - and then can talk to an engineer about what broke without getting lost.
Writes things down by default. Much of this job is written: tickets, changelogs, bug reports, escalations, call notes. Precise and brief beats thorough and vague. The instinct we're hiring for treats a decision as unfinished until it's documented somewhere the team can find it.
Someone people can count on. Most of this role is in service of other people — ops needs an answer, an engineer needs context, your PM needs to know where something stands. On a fully remote team that means giving a straight answer, saying so when you don't know, and coming back when you said you would. The defining trait of a good PM early in their career is simply that things don't get dropped.

Nice To Haves

Exposure to insurance — carrier, broker, MGA, claims, underwriting, policy admin, or an insurtech product or ops team. You don't need to know the industry, but knowing what a policy, a premium, and a cancellation are will save you a few weeks
Hands-on time with an observability tool — Datadog
Experience in a QA or test role, formal or informal
Familiarity with issue trackers as an owner rather than a user — Linear, Jira, or similar
Exposure to insurance, fintech, marketplaces, or another regulated domain
Previous exposure to working with a recurring data feed from an external system.

Responsibilities

Stay on top of the data. Track how the data the product runs on is behaving — volume, gaps, anomalies, and the issues that surface from it. You'll be the person who notices when something looks off before anyone reports it, and who can say what changed and when.
Keep the written record true. The part of the job we care most about. Capture is automated notes, transcripts, and summaries generate themselves. Keeping the record correct is not. You'll maintain one source of truth per thing, reconcile the doc against what was actually agreed in the thread, and keep internal and customer-facing changelogs current after every release, so that when someone asks "why does it work this way?", the first place they look has the right answer.
Be the bridge to ops. Ops sees the product in the wild. You'll be their first stop for bug reports and UI feedback — intaking it, reproducing it, sharpening it into something engineering can act on, and closing the loop back so ops knows what happened.
QA engineering work. Before anything ships, you'll verify it does what the ticket said it would. That means understanding the acceptance criteria well enough to test against them, catching gaps between intent and implementation, and pushing back when the two don't match.
Keep the board honest. Ticket hygiene and project maintenance: tickets written clearly, statuses accurate, stale work surfaced, nothing quietly rotting in a column. When something is blocked, you flag it to the staff PM early — not after it has already cost the sprint.
Investigate. Dig into logs, dashboards, and observability tooling (Datadog and similar) to answer "why is this happening?" You won't be expected to diagnose every issue yourself, but you should be able to gather enough evidence that the engineer who picks it up starts three steps ahead.