Who Gets Hired and Onto Which Teams
The Zero G Talent board lists eight Sprig openings across six functions, but the records do not provide one universal hiring bar. The openings span product, marketing, research, software engineering, customer success and sales. The practical question for a candidate is not whether Sprig hires people like them. It is which team needs work they can prove.
That question governs more than résumé tailoring. A candidate needs to know which role fits the evidence, what a posted salary can—and cannot—tell them about an offer, which competencies recur in reported interview loops, and whether the job’s city label describes a workplace or merely a location attached to a contract. This guide follows those decisions through Sprig’s teams, pay, hiring process, locations and employee evidence.
The Zero G Talent board supplies the starting point. It is a snapshot of recent postings rather than a map of every Sprig function. The board does not provide an employee count. A Built In profile that includes recent Sprig postings lists 2019 as the founding year and 50 employees—according to Built In—while Indeed’s undated company profile lists 2013 and a workforce of 2 to 10. Treat those directory figures as estimates rather than a precise org chart. The board also identifies Kevin Mandich, Ryan Glasgow, Matt Kent, Gagan Biyani, Neeraj Berry and Morgan Springer as founders. That roster supplies company background, not reporting lines; it cannot show that every hire reports directly to a founder or that Sprig has few management layers.
The team map
The board separates its vacancies into the lanes below. The final column translates the titles into the kind of record a candidate should prepare; it does not add requirements absent from the postings.
| Function | Opening | Signal in the title |
|---|---|---|
| Product | Lead Product Manager, Core | Core-product decisions |
| Marketing | Senior Manager, Marketing | Marketing management |
| Research | Research Partner (Contract) | Contract research delivery |
| Software engineering | Senior Software Engineer, Developer Productivity | Developer tools and workflows |
| Marketing | Marketing Events Lead | Event execution |
| Customer success | Senior Customer Success Engineer | Technical customer implementation |
| Sales | Director of Sales, Mid-Market (Zero G Talent’s board data) | Mid-market commercial leadership |
| Research | Research Strategy Lead | Research strategy |
The title is a routing label, not an interview plan. It identifies the lane a candidate should evidence; the vacancy remains the controlling document.
Product and software need different proofs
Built In’s Lead Product Manager description says the role owns Sprig’s core survey product, including survey creation, advanced logic, distribution, permissions, integrations and team management. The Senior Software Engineer title points to Developer Productivity, but the available extracts do not provide that role’s duties.
Make that distinction concrete. A product applicant can show how they set priorities, defined outcomes and explained tradeoffs. A developer-productivity applicant can show how they improved engineering systems or removed friction from development work. The available extracts name no programming language, framework, degree requirement or minimum years of experience. Anyone who says Sprig uses one fixed technical screen fills a gap with guesswork.
Research is tied to a rebuilding effort
Sprig said:
“The research platform is being rebuilt. Help define what comes next.”
For a research applicant, that mission supplies context rather than a method. The titles separate a strategy lead role from contract delivery, but the available extracts do not identify the research subject, methods, expected credentials or deliverables. Read the full posting before choosing evidence. A broad research résumé may not fit either opening.
A strong application can show how you have done research, not merely list topics. An example should define a question, choose a method, handle incomplete information and produce a decision others can use.
The commercial teams are not one go-to-market pool
Sprig’s commercial roles cover different work. The Senior Manager, Marketing description assigns ownership of integrated B2B SaaS marketing programs across events, content, campaigns and thought leadership. The Marketing Events Lead owns end-to-end field-event execution, including venues, vendors, budgets, timelines and onsite delivery. One generic campaign story will not necessarily show the work required by the other role.
The Senior Customer Success Engineer title narrows the target. Show technical troubleshooting or implementation work and the judgment needed to handle a customer problem. The Director of Sales, Mid-Market opening points to commercial leadership in a defined customer segment. A candidate can distinguish that role by presenting sales-management evidence rather than relying only on individual closed deals.
The available extracts do not state quotas or the technical requirements for every commercial role. Treat each vacancy as the source for evidence, but do not mistake its title for a full interview plan. Answer in the same terms as the vacancy rather than recite a general list of skills.
Team fit without pretending the evidence is stronger than it is
Sprig has not published a selection rubric in the available records, so any list of ideal candidate traits would exceed the evidence.
A January 2026 Bar Jobs hiring guide concerns bar hiring rather than Sprig, but it said dependable colleagues who can work at the team’s pace and fit with existing coworkers often matter more than job skills, which managers can sometimes assess and teach more easily. It cannot establish Sprig’s standard, but it offers a useful distinction: some skills can be taught, while reliability and team pace reveal themselves in behavior.
Show how work landed, how you handled disagreement and what you would change on a second attempt. Replace unsupported claims about being collaborative or strategic with specific behavior. A recruiter can evaluate concrete behavior; adjectives do not tell the recruiter what you did.
Before applying, make a role-to-evidence sheet: choose the exact opening, write down the problem that role appears to own, then match it to one measurable example from your record. If your résumé says only “customer-facing” or “technical,” rewrite it; the hiring team cannot match a generic claim to one of Sprig’s distinct lanes. Once that lane is chosen, compensation is the next filter—and the company-wide headline is not enough.
What It Pays
Zero G Talent’s Sprig company page publishes a company-wide salary summary, but the individual vacancy figures provide the more useful comparison. The board is the authoritative source for the eight recent postings, so its role-specific figures should be used rather than an older directory estimate. The salaried openings target lead, senior, director or strategy-level work, so the figures describe a senior hiring slate rather than entry-level pay.
Ask not what Sprig pays generally, but which band applies to the team, level and location.
Use the individual postings to compare roles:
| Posted role | Location | Published annual salary |
|---|---|---|
| Marketing Events Lead | San Francisco, CA | $115,000–$140,000 |
| Senior Customer Success Engineer | San Francisco, CA | $140,000–$180,000 |
| Research Strategy Lead | San Francisco, CA | $165,000–$200,000 |
| Senior Manager, Marketing | San Francisco, CA | $180,000–$230,000 |
| Senior Software Engineer, Developer Productivity | San Francisco, CA | $180,000–$260,000 |
| Lead Product Manager, Core | San Francisco, CA | $200,000–$255,000 |
| Director of Sales, Mid-Market | San Francisco, CA | $300,000–$350,000 |
| Company-page aggregate | Company-wide | $133,000–$323,000 typical band; $243,000 median |
The individual bands overlap, but not evenly. The Senior Manager, Marketing and Senior Software Engineer openings share a starting point while their ceilings separate; the product and sales roles occupy different rungs. Title alone does not identify pay; scope and level also differ.
The company aggregate describes the board’s eight salaried roles. It does not set a floor and ceiling for every offer. Individual roles extend below and above that summary, and the information does not show how years of experience affect placement. A San Francisco label also does not mean the same band applies in another state or country.
The Research Partner (Contract) role sits outside the annual comparison. Its New York City posting pays $120 to $150 per hour. The board aggregate covers eight salaried roles, while this engagement is paid hourly. Confirm expected hours, contract length, deliverable expectations and whether the engagement can become salaried before you annualize the rate.
Salary is only part of the offer. A Built In profile lists company equity and an employee stock purchase plan, but the board data gives no dollar values. The available records also do not show whether bonuses, equity or other compensation sit inside or outside the published salary range. Settle that before comparing one offer with another.
Before the first recruiter call, put your target role, location and expected salary beside the matching posting. Then ask where your experience falls within that band, whether Sprig adjusts pay by address and what else the company includes in total compensation. That answer gives you a band; the next uncertainty is how the company decides whether your evidence clears it.
How the Hiring Process Works and What Gets Candidates Through
For Sprig, Glassdoor and Dataford each draw on candidate-reported interview records. Glassdoor catalogs 48 interview questions and 43 reviews, while Dataford separately aggregates 44 interview reports. The sites may cover some of the same submissions, and neither discloses a selection method, so their totals cannot be added.
Glassdoor describes a lengthy, multi-stage process involving phone screenings, technical interviews and panel discussions. Dataford has separate guides for software engineering and account executive roles, but its material does not establish one fixed sequence for every opening. Prepare for several conversations without assuming that every role includes the same number of rounds. Learn which competencies the opening will assess, then be ready to discuss them with people from the hiring team.
“About 50% of candidates who interview go on to receive an offer.”
— Dataford
Dataford bases that figure on 22 offers across 44 reports with a stated outcome. The sample does not reveal the full applicant pool, role mix or calculation method, so it cannot serve as a Sprig-wide acceptance rate. Reaching an interview does not guarantee an offer. Prepare around role fit and the competencies each opening names.
The screening signal candidates can actually use
The sources do not identify a recruiter or publish a company-wide screening rubric. A January 6, 2021 Indeed entry asked, “What are your qualifications?” That question is too general and old to define Sprig’s current screen. The available material also does not confirm a degree requirement, take-home assignment, coding-test format or automated rejection rule. Any guide that presents one as settled Sprig policy exceeds the evidence.
The usable signal is the set of skills that recurs in candidate-reported loops. Dataford’s prominence scores rank skills; they do not set pass rates or cutoffs, and they do not show that every interviewer asks every question.
| Role guide | Skills in Dataford’s topic breakdown relevant to the role | Evidence to prepare and make visible |
|---|---|---|
| Software engineering | API design; general coding and problem solving; React; schema design and data modeling; React Hooks; data structures | API decisions, database tradeoffs, a code solution and React implementation choices |
| Sales | Sales prospecting; cold outreach by email; cold outreach by phone; deal lifecycle from discovery to close; sales messaging and copywriting; ideal customer profile definition | Target selection, written outreach, phone prospecting, discovery-to-close examples and a clear account profile |
The table groups the topics in Dataford’s companywide breakdown by the role guide to which each belongs; the extract does not provide separate role-level percentages. Treat the table as an index, not a scorecard. Rehearse the reasoning behind the artifact, not a list of tool names. An interviewer should be able to follow a decision, a constraint and a result; a list of product names gives the panel nothing to test.
Dataford provides no equivalent skill breakdown for customer success, research, product, design or marketing. Do not import the software or sales signals into a cover letter. Extract the core work from the posting, connect past performance to it and ask the recruiter which competency each round will assess.
What gets through, and what the evidence cannot prove
No source names a universal disqualifier. Do not assume that a degree, a specific coding test or a take-home project applies across Sprig. The evidence also does not explain why other interviewees did not receive offers.
The practical risk is an application that gives the reported interview loop little to assess. If the examples cannot be examined under pressure, the panel has less to test. These are preparation risks, not verified company rules, but they follow from the reported loops.
Candidate reviews add another reason to manage the process deliberately. Dataford’s aggregate sentiment is about two-thirds positive, but Glassdoor candidates also report a disorganized or impersonal process and a consistent lack of feedback after interviews. Ask for a clear explanation of the next round, its format and the competency it covers. Keep your own notes on questions, assessments and promised follow-up rather than relying on a debrief that may never arrive.
Turn the role-to-evidence sheet into a one-page loop sheet for the exact role: list the recurring skills named in the vacancy, attach two proof points for each, select one work sample and note the stages confirmed by the recruiter. Rehearse until you can explain each proof point without notes. That preparation addresses what the sources support: interviews vary by role, and reported loops emphasize role-specific competencies.
A precise loop still assumes a particular working arrangement. The city labels in the postings are the next fact to interrogate.
Where the Work Happens
The current Sprig board attaches roles to San Francisco and New York City.
| Location named in posting | Openings | What the listing supports |
|---|---|---|
| San Francisco, California | 7 | A broad functional base |
| New York City, New York | 1 | A contract research connection |
These figures locate jobs; they do not establish a physical workplace count. The board records city and salary but no addresses or office layouts. Separate Built In listings label the Lead Product Manager, Senior Manager, Marketing and Marketing Events Lead roles as hybrid, but do not specify office days, addresses or layouts.
San Francisco: where most listed roles are located
The San Francisco slate covers product, engineering, go-to-market, customer success and research strategy. That mix makes the city Sprig’s main functional center in the listings, but it does not establish that those groups work in the same building or even the same time zone. A city label alone does not show how often employees attend, and a hybrid label does not supply that detail either.
The practical question is how often the team gathers in San Francisco, which functions are based there and whether the office is the operational center of the role or merely its listed headquarters.
New York: where the research work is attached
New York appears through the Research Partner (Contract). The record supports a contract research connection, not a broad permanent-office footprint comparable to San Francisco’s spread.
For a contractor, the practical questions are whether the engagement is remote and which Sprig team the partner will support. The posting does not describe a New York office, identify an address or say whether contract partners attend onsite sessions.
What teams can build and test
The available record describes software and AI development, not physical production. Sprig’s platform turns raw user feedback into useful product data, and its former AI Squad brought design, product and engineering together around AI features. In a July 1, 2026 profile, Kevin Mandich’s model-evaluation rule is to test models against actual customer data and the real task, then switch only when a new model produces a durable improvement. That is software evaluation: access to messy inputs, repeatable tests and a way to review uncertain outputs.
The same profile says Sprig grounds models in specific user-provided datasets, uses review loops and source-of-truth data, and exposes underlying source data so users can verify recommendations. It also links customer-data privacy to user skepticism. The available record does not describe a hardware lab, an on-premises model-training cluster or specialized physical facilities.
A city label tells a candidate what the company tracks, not what they can access, test or build from a desk.
Before applying, get clear answers to five location-sensitive questions:
- Is the role remote, hybrid or onsite, and how many office days are expected?
- Which team and manager are based in the listed city?
- What safeguards protect the customer data the team uses?
- What review and evaluation systems support its AI work?
- Does the role require specialized equipment or facilities that the posting does not describe?
Those answers define the work environment. The employee evidence raises a separate question: whether that environment is a good fit.
Who Thrives Here
One Blind reviewer in an April 9, 2025 post described “lots of ownership” and said work “moves fast, sometimes too fast.” That pairing raises two practical questions for a candidate: how much room there is to make decisions and how quickly priorities can change.
The available source set contains no formal Sprig competency model or interview rubric, so the reviews are fit signals rather than hiring rules. The Blind reviews also raise staffing and management concerns. A candidate can test whether those concerns apply to the specific team instead of treating one review as a verdict. Thriving depends less on enjoying rapid change than on turning shifting priorities into action without waiting for every answer.
Employee ratings from Glassdoor and Blind split the picture between daily experience and management.
| Source | Review base | Overall | Work-life balance | Culture and values | Career opportunities | Management | Would recommend |
|---|---|---|---|---|---|---|---|
| Glassdoor | 43 reviews | — | 3.9/5 | 4.5/5 | 4.4/5 | — | 81% |
| Blind | 3 reviews | 3.0/5 | 4.0/5 | — | — | 2.3/5 | — |
Glassdoor's data shows an 81% recommendation rate.
Review totals can change, so treat these figures as a snapshot. The Glassdoor data supports a positive view of day-to-day experience and room to grow, but it does not resolve the management complaints found elsewhere. Blind’s sample is too small to settle a culture question. Even so, the contrast shows how a workplace can score well on work-life balance and still leave people frustrated by priorities or decisions. Do not treat one company-wide score as a verdict.
Review feedback dated March 4, 2025 said customers “LOVE the products.” The same entry criticized leadership decisions about product direction, a refusal to increase headcount and teams described as extremely lean. Because this is one dated review, treat it as a single signal. It points to an interview question: how much authority will I have, and what happens when a product decision goes wrong? The review establishes that at least one employee saw teams as extremely lean; it does not say how staffing decisions are made.
A separate April 9, 2025 review said company direction changes frequently and management “doesn’t always listen to feedback.” It is the newest dated Sprig review in the Blind sample. A candidate can accept that not every idea will be adopted while still needing to know how dissent gets recorded and who can reverse decisions. In an interview, ask the hiring manager for a recent priority change and how the team handled disagreement about it. The answer will reveal more than a polished claim about autonomy.
An older March 20, 2024 post said “Constant layoffs,” “Way too many processes,” and “No company vision because of poor management.” It deserves less weight than the 2025 feedback, but it echoes the low management rating. The risk is not simply an intense pace; it is contradictory priorities. Clear decision ownership and trust through a reset may matter more than a stable charter promised in a listing.
MIT Sloan Management Review’s synthesis of 11 meta-analyses said leadership was the strongest predictor of toxic culture. The synthesis also placed employee autonomy close to workload reduction in predicting lower toxic behavior. Applied cautiously to the reviews, it suggests that ownership and management criticism cannot be assessed separately from decision rights and work design. For a candidate, manager behavior, workload and decision rights are useful topics alongside ownership.
A candidate cannot inspect a company’s culture from a job listing. The hiring manager’s record of feedback and decision rights offers better evidence.
The customer praise suggests that people who build products can take pride in direct user response. Working close to customer evidence may be energizing, especially when internal priorities are noisy. The review does not establish that Sprig hires for a particular personality, so test the point in conversations with the team.
An aggregate career-growth rating cannot promise growth in every role. Boston University’s job-hunting guidance asks whether a role will build the skills a new graduate wants to learn or let them use skills they already have. At Sprig, tie that test to the actual job. Ask what you would own early in the role and which skill you expect to sharpen. Then ask how the team judges performance.
Prepare with the same evidence standard used elsewhere in this guide. Bring an ownership example, a case where user feedback changed a decision and an example of moving after priorities shifted. Then ask what you would own early, which skill you expect to sharpen, how the team judges performance and who owns decisions after a priority shift. That last question matters because ownership without a clear decision owner is the recurring risk in the review evidence.
Before the first interview, put the exact vacancy beside one measurable result and one moment when the plan changed. Those are the answers a hiring team can test; a list of startup adjectives is not.
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.