Complex day at Pinterest

Recover purchases before the queue expires without counting them twice

Published Nov 3, 2026

You’re the solutions / forward deployed engineer. Your team is in the room.

The setting

serves people who use its app and the businesses that advertise there. is a self-service platform where advertisers create, target, bid on and measure ads shown to Pinterest users.

The purchase queue expires before every submission can be traced.

Preserving missing revenue conflicts with keeping uncertain purchases out of optimization.

Who you’d be doing this for

“Finance asked why yesterday's orders vanished from my numbers, and now I'm told retrying them could count them twice.”

Petra Nemec · Retail Performance Marketing Manager · a character in this brief

Runs the retailer's holiday campaigns and must explain reported revenue to finance while the integration team reconstructs the incident.

What is at stake

A retailer could lose 180,000 queued purchase events while its holiday campaigns keep spending. You must weigh permanent gaps against replaying revenue that may already influence bidding.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • purchase coverage vs duplicate revenue
  • retention expiry vs defensible reconstruction
  • historical recovery vs live ingestion
  • finance completeness vs engineering release controls

Why Pinterest

Server-side purchase signals connect the retailer's order systems to the measurement and bidding behind its holiday campaigns.

Written with these in mind

Enterprise integration engineersCustomer-embedded technical problem solversPartner engineers experienced in incident recovery

Not your kind of problem? 50 more at Pinterest, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Pinterest. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about losing track of what's happening in the field.

The same setting, from another role

Each is set around Pinterest’s Pinterest Ads, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to engineer security-critical controls whose correctness holds up even when carefully examined by skeptics.