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.
Concurrent reporting protects the morning deadline but retries mix up the retailer's account positions.
The retailer needs complete campaign results without giving up the speed of its existing reporting job.
Who you’d be doing this for
“I opened the report at eight and half our campaigns weren't there. Now I'm checking each account before the budget meeting.”
Kipchoge Ngugi · Retail Performance Media Manager · a character in this brief
Uses the retailer's combined account reports to prepare daily campaign spending changes.
What is at stake
A retailer's eight account reports omit campaigns despite successful API requests. You must weigh a targeted retry repair against slower, sequential reporting that also delivers complete results.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reporting speed vs simpler execution
- targeted code change vs configuration certainty
- morning deadline vs runtime headroom
Why Pinterest
Enterprise advertisers depend on the Pinterest API to carry campaign results into the reports they use to move spending.
Written with these in mind
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.
- Sr. Technical Support Engineer (opens in a new tab)
- As a Partner / Technical Support Engineer, you’ll work with a variety of Tier 1 clients across Pinterest products (Enterprise, Adtech, Shopping, Growth, etc.) to define and build scalable partner solutions, helping hundreds of millions of people find ideas and inspiration.
- Sr. Technical Program Manager (opens in a new tab)
- Solutions Engineer Intern 2027 (USA) (opens in a new tab)
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on keeping a recurring promise on time.
A source event is causing 2.8% of Pay in 4 plan rows to appear twice in merchant reports.
You have to restore accurate counts without changing valid historical reporting.
A payroll application has 18,000 workers due for payment and 2,400 uncertain outcomes.
You must weigh the customer's deadline against commitments that could trigger irreversible duplicate payouts.
A retry is causing 0.8% of settled refunds to reduce cardholder balances twice.
You have to protect fast refund recovery without letting a delayed response create another adjustment.
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.
Fashion agency contacts are waiting on follow-ups because key call details remain buried in notes.
You have to decide where the system's proposed next step ends and the seller's own word to the agency begins, from the call record to the account record.
Fashion agencies are pulling Visual Search Ads budgets back when no test covers creative learning and finance scrutiny.
You have to weigh a repeatable package against the flexibility each advertiser needs to trust the first test.
A $1.5 million Performance+ agreement is stalled because the ads dashboard and the Clean Room results support different ROAS claims.
You have to weigh a fast annual commitment against measurement terms finance can defend.
Other problems with a similar purpose
In each of these, as in this one, the aim is to trace a strange, repeatable failure back to its root cause and leave behind a fix that quietly holds.
Completed repeated assay tasks remain open in Worklists after their workflow record closes.
You must weigh a fast status correction against preserving the execution history reviewers rely on.
Amended container bookings can hold uploaded documents in the Document Platform while customers see none in the Client Application.
You have to weigh a quick recovery against preserving document access boundaries.
6.8% of completed audio jobs now wait more than ten minutes for a Flow status.
You must weigh a targeted retry correction against a rollback that restores speed but removes newer recovery behavior.
