# Parallel Web Systems — GTM Finance | application short-answers (2026-06-09)

Role: GTM Finance (Ashby `parallel`, jid cfaa0f6a) · SF/Palo Alto, in-person · $175–225K + equity
Resume: `final resumes/2026-06-08/Parallel/GTM Finance/Darsh Shah - Parallel GTM Finance Resume - 2026-06-08.pdf`

## In-office question
Yes — happy to be in the Palo Alto office at least 3 days a week, with the rest split between the SF and Palo Alto offices.

## Why Parallel? (2 sentences)
I've actually built on Parallel — I used your web API as the retrieval backend for a deep-research agent I made — so I've felt firsthand why "the web for AIs" is foundational infrastructure, not a feature. Coming in as the first GTM Finance hire to own pricing, quota, and unit economics for a usage-based AI-infra company at this inflection point is, genuinely, the finance problem I'd most want to be working on.

## Why you? (2 sentences)
I've stood up the GTM finance engine before — quota and sales-capacity planning (scaling a team from 50 to 200 reps against a $300M plan), rep commissions, deal-desk pricing on $50M+ deals, and the funnel and forecast tracking around it — most recently owning consumption-based pricing for AI tooling at Epic. And I don't just analyze AI, I build with it (I run an agentic finance stack and made that research agent on your API), so I can sit between GTM leadership and engineering and speak both languages.

## Tighter alternates (if the boxes are small)
- **Why Parallel:** I've built on Parallel's API (it backs a deep-research agent I made), so I already believe in "the web for AIs" as infrastructure — and owning pricing, quota, and unit economics as the first GTM Finance hire at a usage-based AI-infra company is the finance problem I'd most want.
- **Why you:** I've built the GTM finance engine before — quota/capacity (50→200 reps vs a $300M plan), commissions, $50M+ deal-desk pricing, and consumption pricing for AI tooling at Epic — and I build with AI, not just analyze it, so I speak both GTM's and engineering's language.

## Truthfulness flag
The "ran your API" line is the strongest differentiator — keep it ONLY if literally true (you ran Parallel's API, not just Tavily). If it was a light test, soften to "evaluated your API against Tavily for a research agent I built."