Product Manager at Tratta

About Tratta

Tratta is the platform that powers credit and collections at scale, and we try to make it enjoyable to work on.

Our clients are collection agencies and law firms recovering debt from consumers. Their account data lands in Tratta and is mapped and validated on the way in. They run email and SMS campaigns off it. Consumers land on a payment portal carrying the client's brand, where they can pay, negotiate a plan or sign an agreement electronically without ever speaking to a collector. Payments clear through us by card, ACH or check, and it all feeds back into reporting that shapes the next campaign.

Campaigns, data and payments as one closed loop instead of four vendors stitched together. Every week that loop moves millions of dollars in payments, ingests nearly 100 million rows of client data and serves almost 10 million API requests.

About the Product Team

The product team is small: two PMs, one designer and a distributed engineering team of about ten. You would be our second product hire. There is no product ops layer, no analyst and no one sitting between you and the client, or between you and the code.

The role

You will own a set of topics end to end. Not "manage a backlog" in the abstract, but pick up messy input from clients and customer success, turn it into something the team can build, get it shipped, and then make sure it actually gets used.

Turn requests into work. Client and CS requests arrive as symptoms, not specs. You dig into what is actually being asked, decide whether it is a bug, a gap, a training problem or a real product need, and write it up so a developer can pick it up without a meeting.

Prioritize. You decide what gets built next among a lot of competing, legitimate asks, and you can explain the reasoning to a client, a developer and a founder in three different ways.

Firefight. Bugs and urgent client issues will land on you. You triage, reproduce, escalate the real ones, and close the loop with whoever raised it.

Discovery. You help figure out what we should build next, from client conversations, usage data and your own read of the market.

Data. You are comfortable with data end to end: getting it, questioning it, and deciding what to do about it.

Own outcomes, not output. Shipping is the midpoint, not the finish line. If a feature launches and nobody knows it exists or nobody adopts it, that is your problem to solve. You will write the client email, record the walkthrough, check the numbers a month later and tell us honestly whether it worked.

Wear multiple hats. Small changes you can do yourself with Claude, you do yourself. Otherwise: specs, debugging, data and dashboards, release notes, client emails, whatever the topic needs. There is no one to hand it to.

What this role is not

It is not a role where you write requirements and hand them to someone else. It is not a role with a defined scope that stays defined. And it is not a role where you can be effective while waiting to be told what to do.

How we work

Very little process and very few meetings. No planning ritual that exists to justify the previous planning ritual. If something is not working, we change it the next day.

The tradeoff is that nothing will be handed to you. There is no queue of pre-groomed tickets, no one checking whether you did the thing, and no process to hide behind if a topic quietly stalls. Autonomy and accountability come as a pair here.

We use Claude heavily across product work: analysis, drafting, prototyping, bulk operations across Linear, Slack, HubSpot and our data. Being fluent with AI tooling is not a bonus point, it is how the job gets done at this team size.

You will do well here if you

• Have shipped real product in a small team

• Are comfortable being close to the technical detail: reading logs, querying data, understanding an API contract, reproducing a bug before you file it

• Write clearly and briefly

• Prefer deciding with 70% of the information over waiting for 100%

• Are direct. You push back when something does not make sense, and you say when you were wrong

• Can hold several unfinished topics in your head without dropping any of them

What we offer

This is a full-time position, 40 hours per week, with at least 4 hours of overlap with the UTC+1 time zone.

Compensation is up to $80,000 USD per year, depending on experience.

Please note: Tratta is based in the US, with an office in the Midwest and a small team across Europe and South America. We don't have a legal entity in Europe, so this role is a B2B contract. You work as an independent contractor through your own business and handle your own taxes and insurance.

You get 40 paid days off per year: 15 vacation days, 14 paid holidays, 8 sick days and 3 personal days.

Tratta provides company laptop after your first 30 days.