Trigger
$75M Series C closed February 2026, Goldman Sachs led, $700M valuation. Staff Product Designer posting is live. Lauren Abulaban, Senior Product Design Manager, is publicly signaling active hiring. High confidence on the trigger. Moderate confidence on the decision-maker.
The gate
Published base range is $180K–$210K. Your floor is $250K cash. That's a $40K–$70K annual gap, and positioning doesn't fix economics.
Fieldguide is pre-IPO at $700M. Equity could theoretically bridge: a four-year grant worth roughly 2.3–4.0 basis points of headline valuation gets you to $250K in nominal total comp, depending on where cash lands. But that number is gross, at preferred-stock valuation, before strike price, dilution, taxes, and the fact that options don't pay rent.
If your $250K rule is cash-only, stop here. If you're willing to evaluate a total-comp exception where equity carries real weight, the next section tells you how to test it before you spend prep time.
How to clear it
Ask the recruiter in the first conversation — before portfolio prep, before the cover letter:
Is $210K the firm cash ceiling for this level and location, or is there a compensation exception that reaches $250K in guaranteed cash? If cash is fixed, I'd need to evaluate the equity package seriously — could you share the grant as a fully diluted ownership percentage, the current 409A valuation and its date, strike price, vesting schedule, post-termination exercise window, refresh policy, and whether Fieldguide has any history of employee tender offers or secondary liquidity?
What clears the gate: cash reaches $250K, or the equity grant is large enough and liquid enough that you'd accept the total package with eyes open. What doesn't: a share count without a fully diluted denominator, or a dollar figure calculated at preferred-stock price with no 409A context.
If they can't answer the equity questions in the recruiter screen, that tells you something about comp maturity. Escalate to the hiring manager before portfolio prep.
If the gate doesn't clear, redirect energy. Everything below assumes it does.
Window
The Series C is six months old. Hiring velocity is still elevated — posting live, Abulaban actively promoting. Estimate 4–6 weeks before this search is deep in pipeline. Act within two weeks if the comp question resolves.
What this trigger means for the design org
Fieldguide's VP Product Dhruv Dhingra wrote in late July that as agents take over planning, execution, and documentation, the review experience becomes the product. They've already shipped agent-driven substantive testing where agents request evidence, extract data, evaluate results, and pause for human review. The Staff Designer they're hiring builds the surfaces where an auditor exercises professional judgment, records it, and can defend it later.
No VP or Head of Design is visible in public-facing leadership, blog bylines, or design community directories. Abulaban appears to be the highest design authority. Design influence runs through product leadership, not a parallel design executive. That could mean Dhingra gives design real strategic input, or it could mean design is a delivery function with a manager title ceiling. Find out which.
Your angle
Lead with Thermo Fisher. The parallel is direct: a regulated industry running critical workflows on manual processes, where you built the system that caught exceptions early enough to act on them — $20M+ in recovered margin, 100% partner adoption, six pharma partners across three continents. Fieldguide's auditors need the same architectural move Thermo Fisher's supply chain managers needed: exception-first surfaces that make the human review step an informed decision.
Support with the Trust essay. Fieldguide has already built signoff, send-back, and citations. The design problem ahead is the one you named in "Trust Is the New Interface" — the Decision Gate handoff, where the system's output becomes the human's professional commitment. You've published the framework for what their Staff Designer will spend the next two years building.
Who to contact
Lauren Abulaban — Senior Product Design Manager. LinkedIn. Her strongest public statement: designers at Fieldguide own problems end to end, make real tradeoffs, and ship work that gets used, with "clarity, ownership, and impact" as team values. No conference talks, podcasts, or long-form writing in the last 90 days.
Dhruv Dhingra — VP Product. LinkedIn. Richer public fingerprint. His July 29 article frames the product thesis explicitly — agents prepare, humans review, the review surface is where product value concentrates. He's the stronger hook source even if Abulaban is the closer hiring contact.
Warm path: None from public sources. This is cold.
Channel: LinkedIn DM to Abulaban. Use Dhingra's published framing as the hook.
Outreach messages
Warm message to Abulaban (use if you discover a mutual connection):
[Name] suggested I reach out — I spent a year at Thermo Fisher building exception-first workflow architecture for pharma supply chains, where the system caught problems early enough that reviewer signoff was informed rather than ceremonial ($20M+ margin recovered, 100% partner adoption). Fieldguide's challenge of keeping audit reviewer authority meaningful as agents handle more preparation is the same structural problem in a different regulated domain. I'm currently Head of Product at TinyFish (enterprise web agents, Series A), working through agent auditability and governance daily. Would 20 minutes on how the design team is approaching reviewer signoff as agent scope expands be useful?
Cold message to Abulaban:
Dhruv's recent piece on the review experience becoming the product landed for me — I spent a year at Thermo Fisher building exactly that inversion for pharma supply chains, where the system caught exceptions early enough that the human review step stayed informed and defensible ($20M+ margin recovered, 100% partner adoption). I wrote about the broader pattern in "Trust Is the New Interface" — the Decision Gate handoff where system output becomes professional commitment. Currently Head of Product at TinyFish (enterprise web agents, Series A), working through agent auditability and governance daily, and returning to design to apply that depth to a specific regulated domain. Would 20 minutes on how Fieldguide is thinking about reviewer authority as agent scope expands be useful?
What not to say:
- Don't frame Fieldguide's problem as "adding human oversight." They've already shipped signoff, send-back, and citations. The problem is keeping those mechanisms meaningful at scale.
- Don't lead with Agentic Labs. The currency here is regulated-workflow architecture. Labs supports; it doesn't headline.
Cover letter draft
Fieldguide's product has already moved evidence collection, sample testing, and documentation into agent execution. The design problem ahead is harder: keeping reviewer signoff an accountable professional decision — with provenance, exceptions, and correction history legible enough to defend — as agents prepare more of what auditors used to build themselves.
I built this pattern at Thermo Fisher, where I designed a 0→1 digital supply chain for the world's largest CDMO. Six pharma partners were running critical workflows on spreadsheets; exceptions surfaced at the delivery gate, 3–5× costlier than if caught a week earlier. I architected five modules — exception-first order management, batch kanban with at-risk flags, bidirectional KPIs, forecast portal, capacity heatmap — recovering $20M+ in annual margin with 100% partner adoption across nine sites, all built to make the human review step informed and defensible.
I'm currently Head of Product at TinyFish, an enterprise web agent platform (Series A), where I work daily with agent traces, auditability, and governance in production deployments. I moved to product to build AI-natively from zero and shipped three products in three months; I'm returning to design because I want to apply that technical fluency to a domain where design decisions carry professional and regulatory weight.
I'd welcome the chance to discuss how Fieldguide is approaching reviewer authority as agent scope expands. Portfolio and the Trust essay are at junochen.com.
Resume emphasis guidance
- Lead with Thermo Fisher — exception-first regulated workflow, 0→1, $20M+ margin, 100% adoption. Direct match.
- Trust essay prominently placed — Decision Gate handoff framework maps to Fieldguide's reviewer signoff problem.
- Alibaba third — enterprise scale credibility ($50B+ GMV, +20% transactions). Proves you operate at platform scale.
- TinyFish in the header — "Head of Product at TinyFish (enterprise web agent platform, Series A)." One line: shipped 3 products in 3 months, daily work with agent traces and auditability.
- Trim Equinox+ — consumer fitness doesn't earn space here.
- Keep Red Cross — mission-critical, regulated (FEMA compliance), 0→1. Secondary proof for the regulated-workflow pattern.
- Carrier IQ from Agentic Labs as supporting evidence — InsurTech quote automation demonstrates all five trust handoffs in a regulated context.
The non-obvious thing
Fieldguide's signoff documentation currently allows any user to sign a row as either Preparer or Reviewer. Role-based custom signoff workflows — with assigned roles and enforced states — are described as early-access. The gap between having a signoff button and enforcing separation of duties across every workflow is the design architecture problem underneath the UI. Fieldguide has shipped provenance, send-back, and review states. Whether reviewers have the time, training, and structural permission to actually override agent conclusions without penalty is publicly unestablished. That's where the Staff Designer's work starts. Bring this distinction into conversation and you've shown you've read the product past the marketing layer.
Warning signs
- Cash below floor. If the gate doesn't clear, this is a Watch.
- No visible design executive. Ask Abulaban directly: who does design report to, and does design have a seat when product strategy decisions are made?
- Staff IC scope ambiguity. A Staff Product Designer reporting to a Senior Product Design Manager is an unusual structure. Clarify whether this is a peer-level hire where the Staff Designer operates with independent scope, or whether the title carries a narrower mandate than it implies.
Competitive landscape
Regulated-workflow designer (moderate confidence): someone from healthtech, fintech compliance, or govtech with domain-specific audit experience. Likely outperforms you on audit vocabulary but underperforms on AI-native credibility. Your counter: the Trust essay and TinyFish production experience with agent traces give you the AI layer they almost certainly lack.
AI-native IC (moderate confidence): strong craft candidate from an AI startup. Likely outperforms on pure AI design brand but underperforms on regulated-domain proof. Your counter: Thermo Fisher's regulated 0→1 is a credential this archetype cannot match, and Fieldguide's core problem is regulated judgment, not AI novelty.
Enterprise design director (speculative): Big Four consulting or enterprise SaaS background. A Staff IC posting signals Fieldguide wants hands, not org charts.
Post-outreach signals
Response within 3–5 business days is normal for this stage. Silence past 7 days: one follow-up at day 8 with a new signal hook — a Fieldguide product update, a Dhingra post. No reply after the follow-up, close the loop and redirect. A recruiter screen scheduled from first contact means the search is moving fast; have the comp question ready for the first five minutes. Calendar availability in the first reply: move Fieldguide to the top of the daily queue.
- Signoff enforcement is early-access: Fieldguide's signoff documentation shows role-based custom workflows with assigned Preparer/Reviewer states are still in early access — ask in conversation how widely firms have adopted enforced separation of duties versus the default any-user signoff.
- Dhingra's product thesis keeps publishing: His July 29 article on the Agent Review Experience is the freshest executive language on where product value concentrates — monitor his Fieldguide byline for new pieces that could sharpen a follow-up hook.
- Carta's equity benchmarks shifted: Carta's H2 2025 compensation report shows median IC equity grants rose nearly 11% over two years, which gives you context for evaluating whatever Fieldguide offers — but the exact Staff Designer/Series C cell remains behind a paywall.
- Field Orchestrator scope is expanding: The initial disclosed workflow covers Search for Unrecorded Liabilities with agent-driven evidence collection and human exception review — watch for additional audit procedures entering agent execution, which would change the scale of the reviewer-authority problem you'd be hired to solve.