The hiring map
Pump.co has 18 salaried roles open with a median base of $180k across five distinct titles, all located in San Francisco. The roles a company posts reveal its operating model. At Pump.co, the pattern from recent openings shows hiring across go-to-market, engineering leadership, legal, and infrastructure functions.
Four distinct hiring vectors run in parallel: Account Executive, Engineering Manager (two postings), In-House Counsel (two postings), DevOps Engineer. That spread signals a team hiring senior individual contributors alongside functional leads. The Account Executive role, banded at $290k–$430k per Zero G Talent's board data, carries a compensation structure implying enterprise sales motions with significant variable upside. Only one AE posting appears versus two Engineering Manager slots.
Two Engineering Manager postings at $180k–$250k, per Zero G Talent's figures, indicate either team splitting or deliberate redundancy to cover domain separation. The DevOps Engineer role at $140k–$200k, as Zero G Talent's data shows, sits beneath that layer, confirming operational maturity requirements.
Legal and compliance carry equal weight. The duplication points to distinct mandates, though the specific focus areas are not documented in available sources.
Product management and customer success do not appear in the current posting set. The engineering manager duplication and the DevOps role imply product leadership may be already seated or embedded in the engineering manager remit, but this is inference.
What ties these functions together is the domain. The counsel needs cloud contract fluency. The DevOps engineer needs AWS Organizations and Control Tower depth. The AE needs to speak FinOps with CFOs and engineering leads simultaneously. The hiring mix reflects a company where domain credibility in every function appears to be the bottleneck.
No current or former employee has gone on record in the available sources describing culture, conflict handling, promotion cadence, or whether the culture rewards specialization or breadth. The only reliable signal is the roles they keep reopening.
Compensation at a glance
Pump.co's compensation data, drawn from live postings, clusters around a $70k–$250k base band with a median near $180k across 18 salaried roles. Every role listed below is San Francisco–based.
| Role | Level / Scope | Base Salary Range (USD/year) |
|---|---|---|
| Account Executive | Full-cycle sales, SF | $290,000 – $430,000 |
| Engineering Manager | People + delivery lead, SF | $180,000 – $250,000 |
| In-House Counsel | Commercial/regulatory, SF | $150,000 – $200,000 |
| DevOps Engineer | Platform/infrastructure, SF | $140,000 – $200,000 |
The Account Executive band sits notably higher than the rest, consistent with early-stage companies tying a large variable component to quota attainment. The $290k floor suggests a substantial guaranteed base before commission; the $430k ceiling implies on-target earnings competing with Series B–C SaaS peers. Engineering Manager and In-House Counsel share a similar width ($70k and $50k spreads respectively), signaling that Pump.co prices experience and scope granularity within each function rather than flattening titles. DevOps Engineer tops out at the same $200k ceiling as Counsel, reflecting the premium on platform reliability.
Only five distinct titles appear in the current posting set, though the board notes 18 salaried roles overall. That gap means the median band likely includes individual-contributor engineering, product, and customer-success positions that haven't surfaced in recent listings. Pump.co's equity structure isn't disclosed in the board data.
Separately, a different company (pump.fun, a Solana-based token launchpad) operates a $PUMP token buyback program funded by 50% of protocol revenue. That program is unrelated to Pump.co.
Inside the funnel
A widely referenced six-stage funnel model, described in a 2022 walkthrough by John Miller (The Deliberate Engineer) based on 30 years at Google, Amazon, and Microsoft, breaks down the time and decision logic at each gate. The wider the stage, the more candidates it evaluates; the taller, the deeper the scrutiny. By the final stage the pool is one or two people wide. This model is common across high-growth tech companies hiring engineers, product managers, and go-to-market roles.
Stage 0: Sourcing and keyword filtering
Applications and cover letters pass through automated keyword matching before a human sees them. The system flags whether a profile warrants a recruiter's time. Candidates who make it easy — clear headers, standard role terminology, skills listed in plain language — survive this filter. Dense paragraphs, unconventional titles, or missing core keywords get dropped in seconds.
Stage 1: HR screen (≈1 hour)
A recruiter asks baseline questions supplied by the hiring team: "What is a loop?" "What is an x.509 certificate?" "What is HTTP?" "How would you make a list in JavaScript?" Anyone with a realistic shot at the role should answer cleanly. The recruiter isn't evaluating depth; they're verifying the candidate isn't a mismatch before burning engineering hours.
Stage 2: Technical screen (30–60 minutes)
A single engineer runs a focused conversation: coding, system design, debugging, or a domain-specific walkthrough. The bar is lower than the full loop: the goal is deciding whether a full day of interviews is justified. The screener writes a summary and a binary "interview" or "no interview" decision. A "no" ends the process.
Stage 3: Full interview loop (½–1 day to schedule)
Candidates who clear the screen meet 4–6 interviewers across disciplines. Each session runs ~60 minutes plus prep and feedback writing. Question types rotate: coding, architecture, testing, "soft" skills, leadership scenarios. Every interviewer submits a hire/no-hire verdict with written rationale: strengths, concerns, red flags.
Stage 4: Debrief (≈1 hour)
The hiring manager leads a discussion of the packet. Strong-consensus hires or clear rejects are quick; split decisions take 30–45 minutes. The process is deliberately conservative: if an interviewer cannot find positive evidence, they must vote no-hire. Absence of signal equals rejection.
Stage 5: Offer construction (½–1 day)
If the debrief yields a hire, the recruiter assembles the package: compensation, equity, start date, and any team-matching step.
What gets candidates through
- Readable, keyword-rich applications that survive automated parsing.
- Clean answers to fundamentals in the HR screen — no hedging, no "I'd Google it."
- High-bandwidth technical conversation in the screen and loop: the interviewer needs evidence, not charm. Candidates who drift into side topics waste the signal budget.
- Consistent "hire" votes across the panel. One or two no-hires can be debated; a majority is usually fatal.
What disqualifies
- Insufficient evidence at any stage. The process defaults to no.
- Inability to demonstrate core knowledge (loops, certs, HTTP, basic data structures) when asked directly.
- Feedback arguments: the company does not share detailed rejection reasons. The recruiter sends a standard "not a great fit at this time, reapply in six months" note.
The economics behind the rigor
Running a single candidate through the full loop costs ~30 hours of company time (roughly $25k–$50k in fully loaded cost for a high-tech hire). Filtering aggressively at stages 0–2 cuts that to ~108 hours per hire (≈$11k) for a 100-applicant funnel. Every engineer interviewing is an engineer not shipping.
Pump.co's live board shows active requisitions across engineering, legal, and sales.
One room in San Francisco
Every role on Pump.co's board in recent months carries the same location: San Francisco, California, United States. The Account Executive, two Engineering Manager postings, two In-House Counsel listings, and the DevOps Engineer role all point to a single hub.
Public floor plans, square-footage figures, or lab inventories don't exist in the sources. The board data shows a team built around roles that typically demand close collaboration: an Engineering Manager overseeing developers, a DevOps Engineer managing infrastructure, an Account Executive closing deals, and In-House Counsel handling compliance, all posting from the same address.
San Francisco's commercial real estate market pushes early- and growth-stage companies into subleased floors, WeWork-style buildouts, or shared offices in SoMa, the Financial District, or Mission Bay. Commute patterns — Caltrain, BART, Muni, bike lanes — dictate when people are in the room together. The board data doesn't specify a neighborhood, but the salary bands align with companies maintaining a physical presence rather than fully remote setups. Fully distributed teams at this compensation level often list "Remote (US)" or multiple metros; a single "San Francisco, California, United States" tag across six postings suggests an office anchor.
The absence of satellite locations — no New York, Austin, London, or Bangalore postings, reinforces a single-site model for now. That model has trade-offs: hiring is limited to the Bay Area talent pool or candidates willing to relocate; collaboration is synchronous by default.
Working in frontier tech? Zero G Talent tracks the openings: see every open Pump.co role, browse frontier tech jobs, the companies hiring, and the people building the field.