What Sprig's Open Roles Reveal
Sprig lists six open roles on its Ashby-hosted careers page: three in marketing, one each in engineering, customer success, and sales — a targeted set that signals the company's pivot to an agent-first survey platform and concentrates candidate attention on a narrow screening criteria. That breakdown is deliberate. Five are full-time; one research partner role is contract. Five sit in San Francisco, one in New York. Four are tagged hybrid. One role arrived in the past week: a Senior Marketing Manager posted 15 hours ago. The other five have been live for two months or more.
The engineering hire is a Senior Software Engineer, Developer Productivity. The title signals internal tooling and infrastructure, not a feature engineer shipping customer-facing AI. The Senior Customer Success Engineer carries an engineering compensation band (common where implementation requires writing code against the product). Sales gets a Director of Sales, Mid-Market, the only role above $300K. Marketing takes three slots: the new senior manager, a Research Strategy Lead, and the contract Research Partner in New York.
| Role | Compensation | Type | Location |
|---|---|---|---|
| Senior Marketing Manager | $175K–$200K | Full-time | San Francisco (hybrid) |
| Senior Software Engineer, Developer Productivity | $180K–$260K | Full-time | San Francisco (hybrid) |
| Senior Customer Success Engineer | $140K–$180K | Full-time | San Francisco (hybrid) |
| Director of Sales, Mid-Market | $300K–$350K, Ashby's figures put | Full-time | San Francisco (hybrid) |
| Research Strategy Lead | $165K–$200K | Full-time | San Francisco (hybrid) |
| Research Partner (Contract) | $120–$150/hr | Contract | New York City |
Sprig's company page shows 51–200 employees, $85M raised from Andreessen Horowitz, Accel, and First Round Capital, FewerJobs's data shows, and customers including Microsoft, DoorDash, Notion, Figma, Coinbase, and TripAdvisor. The company calls itself the product development lifecycle research platform, now rebuilding around AI agents — the "Analyze Agent" is in preview. The stated goal: $100M ARR, FewerJobs reported.
The hiring plan reflects that rebuild. Three marketing roles, two research-titled, show a go-to-market motion shifting toward research-led content and buyer education. One engineering role in developer productivity signals investment in platform velocity. One customer success engineer signals technical enterprise onboarding. One mid-market sales director signals a funnel moving upmarket.
The founders (Kevin Mandich, Ryan Glasgow, Matt Kent, Gagan Biyani, Neeraj Berry, Morgan Springer) have kept the headcount plan tight. Six roles at this stage is not a hiring sprint. It is a targeted set of hires for a specific product inflection.
What the Screen Actually Tests
Sprig's interview funnel moves fast on paper. Glassdoor logs an 11-day average across three interviews, but candidates describe a process that feels longer because it spreads across disconnected stages. The sequence starts with a recruiter phone screen, advances to a technical or functional interview, and often ends in a cross-functional panel. Internship candidates report five days; customer service applicants saw 17. The variance signals a bar that shifts hard by function: engineering and product roles demand deeper technical validation; go-to-market tracks add commercial scenario work.
Every listing targets experienced ICs or leaders. No junior titles appear. The Senior Software Engineer, Developer Productivity seat weights production-grade infrastructure experience over feature velocity; you'll build tooling other engineers depend on. The Senior Customer Success Engineer demands a hybrid of technical fluency and enterprise account management. The description leans hard on "technical advisor" language. The Director of Sales, Mid-Market requires quota-carrying history.
Two contract research roles (Research Partner (Contract) and Research Strategy Lead) reveal a parallel track. These sit inside the product org and feed the agent pipeline. The Research Partner description calls for a "dynamic, influential contract Research Partner to serve as the face and voice of our brand within the UX research community." The hourly band suggests project-based engagement.
Glassdoor reviewers flag two friction points: disorganization between stages and radio silence after final panels. That's not noise — it's a signal about how Sprig operates. A company building agent-first survey infrastructure will test whether you can operate without a rigid playbook. The product's actual mechanics are public: the Native AI docs detail the Design, Field, and Synthesize agents; the Zero Data Retention agreement with OpenAI is documented; session replays, heatmaps, and micro-surveys feed the same insight loop.
The salary bands themselves filter. A $300K+ sales director role implies enterprise deals with multi-stakeholder cycles. The $260K engineering ceiling means they're not chasing FAANG compensation; they're filtering for people who choose the problem space (live-product insight, agent orchestration) over the package. Resumes leading with "scaled a survey platform" or "shipped LLM features with ZDR compliance" speak their language; "managed Jira boards" does not.
Where Job Boards Disagree
Ashby, Sprig's applicant-tracking system of record, lists the same six open positions detailed above (that same distribution) with identical titles and locations. Each carries a San Francisco hybrid designation except the Research Partner contract role, marked part-time in New York City. Compensation bands appear on Ashby detail pages for three roles. The two engineering roles and the customer-success role show no public range.
Indeed's Sprig landing page returns a generic "View all Sprig jobs in San Francisco, CA" link with no role count in the snippet. The page aggregates San Francisco listings and surfaces a salary-search widget for "Research Strategy Lead salaries in San Francisco, CA," but does not disclose how many distinct requisitions it indexes for Sprig. That opacity makes it impossible to verify whether Indeed mirrors Ashby's six roles, suppresses filled positions, or duplicates postings across locations.
ReqHunt and startup.jobs appear in the section plan as comparison points, yet neither appears in the research corpus with Sprig-specific data. No ReqHunt URL, role count, or title list was captured; startup.jobs returns no Sprig entries. Absent those feeds, any claim about their alignment or divergence from Ashby would be fabricated. The only verifiable third-party source is Indeed, and it offers a count of zero in the visible snippet.
Zero G Talent's first-party board (ingested directly from Sprig's Ashby feed) confirms the same six roles and salary bands. The board itemizes the same six titles Ashby publishes, including the Research Partner contract role at that hourly rate in New York City. One role, Senior Marketing Manager, was added in the past seven days per the board's timestamp. This count matches Ashby's "Open Positions (6)" label exactly, confirming Ashby as the canonical source and Indeed's opaque aggregate as either stale or filtered.
The contradiction is not between Ashby and the first-party board — they agree. It is between Ashby's transparent six-role ledger and Indeed's "View all" placeholder. ReqHunt and startup.jobs remain unverified for Sprig. Applicants relying on Indeed alone cannot know whether they see the full slate, a subset, or ghost listings. The only reliable signal is the Ashby feed, mirrored without alteration on Zero G Talent's company page for Sprig.
What the Roles Reveal About Sprig's Agentic Architecture
Sprig's product is not a survey tool with AI sprinkled on top. Its architecture centers on specialized agents — Field Agent for conversational deployment, Analyze Agent for synthesis, and a study-design agent that turns research goals into runnable instruments. The company's documentation describes a system where agents "support study design, deployment, fielding, and synthesis" end to end. That framing tells you what the hiring screen weighs: evidence you have built, shipped, or operated agentic workflows in production, not just prompted a large language model in a notebook.
The open roles on Sprig confirm the priority. That same seat asks for someone who can accelerate the internal loop that produces those agents. The Senior Customer Success Engineer role sits at the intersection of enterprise SDK integration (Web, iOS, Android) and the omnichannel distribution layer Sprig sells. The Research Strategy Lead and Research Partner (Contract) positions signal that Sprig treats research methodology as a first-class engineering discipline, not a support function.
Portfolio work should mirror the problems Sprig's enterprise customers face. Microsoft's Dynamics 365 Customer Insights team, building parallel agentic primitives (Journey Creation Agent, Outreach Optimization Agent, a consent-aware MCP Server) frames the same constraint: "When customer data is fragmented, outcomes are fragmented." Sprig's Field Agent solves fragmentation by meeting participants in context across email, panels, websites, and mobile apps from a unified platform. A portfolio piece demonstrating a multi-channel data-collection pipeline (a conversational survey deployed via in-app SDK, email trigger, and panel link, with AI-generated follow-ups that adapt to prior responses) maps directly to the Field Agent's documented capabilities. If you have reduced hallucination or compliance risk in a generated-output pipeline, cite the metric. DoorDash's internal agent platform achieved a 90% reduction in hallucinations through a two-tiered guardrail framework; that pattern is recognizable in agent-first evaluation.
Outreach moves should reference the product's documented constraints. The job posts describe legacy competitors (Qualtrics, Medallia, SurveyMonkey) as "built for a slower era, with manual setup, fragmented workflows, and insights that arrive too late." The metric that survives an agent-first screen is speed: show you have collapsed the design-to-insight loop.
When the Senior Marketing Manager role appeared on Ashby 15 hours ago, it propagated to Zero G Talent. Indeed still shows only a "View all" link. The gap between the canonical feed and the aggregators is where candidates either learn the agent-first language or don't — and Sprig's six-role ledger doesn't wait for them to catch up.
Working in frontier tech? Zero G Talent tracks the openings: see every open Sprig role, browse frontier tech jobs, the companies hiring, and the people building the field.