Who Gets Hired and Onto Which Teams
Pocket is listing roughly ten salaried roles across at least five functional areas on the Zero G Talent board right now — and the company's hiring philosophy starts from a hard proposition: your credentials don't get you past the door, your ability does.
Pocket spreads its hiring across engineering, research, data, customer support, and recruiting, with a sixth area likely absorbed within or adjacent to those already visible. Engineering carries the heaviest load: a Full Stack Engineering Generalist focused on Product Impact and a Backend Engineer both appear in San Francisco, the latter with a remote option. A Research Engineer specializing in Voice Intelligence anchors the research side, while a Founding Data Lead covers analytics and infrastructure. On the non-technical side, a Customer Support Lead and a Founding Recruiter round out the visible openings.
This spread is unusual for a company of Pocket's size. Rather than clustering around engineering, the norm at many small frontier-tech startups, Pocket posts meaningful demand in non-engineering functions. Customer support and recruiting appear alongside research and engineering as co-equal priorities. The practical implication: Pocket is building something closer to a full-stack organization than a pure product shop. The people who write the code are hiring the people who answer customer emails, and the recruiter carries the same organizational weight as the data lead.
That structure shapes who gets hired and where they land. Pocket does not organize around rigid job ladders or pedigree filters. The company's public materials describe an interview process designed to test technical limits across multiple dimensions, and its own staff have encouraged candidates to ask "as many questions as you like, no subject is off limits" during interviews. Pocket selects on demonstrated skill over credentials. For a reader deciding whether to apply, the takeaway is direct: the functional areas are open, but entry into any of them depends on showing you can do the work — not where you went to school or what title you held last.
Reading the Pay Band
Pocket pays across a single wide band: roughly $94,000 to $300,000, with a median around $155,000, across its ten salaried roles. That range covers everything from customer support to frontier-model research, and the spread maps to scope, seniority, and competition for each skill set rather than a fixed tier.
The company's most recent postings make that structure visible. Below is a table of real posted roles with their current bands, drawn from live board data:
| Role | Location | Salary Band (USD/year) |
|---|---|---|
| Engineering Generalist - Product Impact (Full Stack) | San Francisco, CA | 200,000–300,000 |
| Research Engineer - Voice Intelligence | San Francisco, CA | 200,000–300,000 |
| Backend Engineer | San Francisco, CA / Remote | 110,000–160,000 |
| Founding Data Lead | San Francisco, CA / Remote | 150,000–180,000 |
| Customer Support Lead | San Francisco, CA | 100,000–180,000 |
| Founding Recruiter | San Francisco, CA / Remote (US) | 130,000–150,000 |
The two highest-paying roles, Engineering Generalist and Research Engineer, top out at $300,000, the ceiling of Pocket's overall band. These are not entry-level positions; they demand deep expertise in domains where talent is scarce and competition is fierce. The Research Engineer role in voice intelligence, for example, requires familiarity with frontier-model deployment and real-time inference systems, skills that command top-of-market rates in San Francisco.
The middle bands tell a different story. The Backend Engineer ($110,000–$160,000) and the Founding Recruiter ($130,000–$150,000) reflect roles that are critical but more established in terms of market supply. The Customer Support Lead range stretches $80,000 wide, which suggests Pocket treats support as a leadership function with real growth potential rather than a flat-tier position. The Founding Data Lead ($150,000–$180,000) splits the difference, positioning data work as foundational without yet reaching parity with the most specialized engineering tracks.
Pocket's compensation philosophy centers on capability, not title. A candidate who can prove they ship impactful product code, regardless of whether they came from a FAANG background or built something from scratch, can land in that $200,000–$300,000 tier. The flat functional mix means there is no hidden hierarchy inflating certain roles while capping others; the band is the band, and candidates earn their place within it through what they deliver. A candidate who clears the technical bar for the Engineering Generalist role will not be offered $155,000 because that is the median — they will be offered what the role commands in the market.
Inside the Hiring Funnel
Pocket's hiring process runs through four rounds and typically spans three to five weeks, though the timeline can compress to as little as one to two weeks depending on the team's immediate needs and whether technical rounds are combined. Candidate-reported interview difficulty sits at average to difficult.
The process is not a single gate but a sequence of filters, each designed to surface a different dimension of candidate capability. Candidates encounter written testing, live coding environments, and oral interview panels, each of which can make or break the opportunity to advance. Multi-stage funnels like this one, where each round eliminates candidates, are well-documented in hiring research, and Pocket's structure follows the same pattern.
The oral interview panel is often the defining moment. Candidates face a panel of three to seven evaluators who assess composure, judgment, and responsiveness under pressure. More organizations are including oral interviews as part of the candidate selection process, and Pocket's structure follows this trend. These panels aim beyond technical evaluation: interviewers are judging honesty when candidates face what may seem like detrimental information, and they want to understand how a candidate manages their own weaknesses rather than whether they are flawless.
Recruiters at Pocket are not simply looking for a skill match; culture fit carries equal weight in the evaluation. Career analysts who have studied Pocket's pipeline note that the candidates who advanced were not those with the strongest credentials but those who understood the process and prepared for it. Pocket's team reinforces this: culture fit is just as important as technical skill.
A strong application shows rather than tells. Candidates who prepare deliberately, attending every available session to understand each part of the assessment, shoring up weak areas like mathematical reasoning, and making genuine connections throughout the pipeline, position themselves to move through the stages. Career experts recommend describing the steps you have taken to mitigate a known problem, which signals proactivity and self-awareness. When given a task, candidates who avoid overthinking and execute with clarity tend to fare better than those who spiral into optimization — a tip from those who have been through the process: if you receive a task, don't overthink it. For technical roles, preparation should include optimizing from brute-force approaches and getting comfortable with live coding environments, as these are explicit parts of the technical screen.
Certain behaviors trigger immediate disqualification. Failing any single component of the technical screen eliminates a candidate from the entire selection process — there is no partial credit or remediation round. Dishonesty in the interview, particularly when confronted with potentially detrimental information, will end a candidacy on the spot. One failed component removes you from consideration entirely.
The process is demanding, but it is transparent. Pocket's structure rewards candidates who prepare thoroughly, present themselves honestly, and demonstrate capability across the full range of assessed skills — not just the ones that flatter their resume. For a company that claims to value demonstrated ability over background, the process itself is the proof: it is built to find the people who can actually do the work, not the people who polish their credentials.
The Office Question
Pocket's operational footprint splits across two modes: a San Francisco headquarters that anchors the company's day-to-day life, and a remote option that several of its departments now offer. Six recent postings list San Francisco as the primary location; among those, three (the Founding Data Lead, the Backend Engineer, and the Founding Recruiter) also carry a remote designation, meaning candidates in those roles can work from elsewhere in the United States without relocating. The remaining three, specifically the Engineering Generalist (Product Impact), the Research Engineer (Voice Intelligence), and the Customer Support Lead, appear tied to San Francisco proper. That distribution maps onto the kind of work each function does: roles that depend on fast, in-person collaboration across teams tend to stay anchored, while roles that produce output independently of geography open up.
The San Francisco headquarters is the connective tissue between Pocket's functions. A small team spread across those functions needs a physical place where spontaneous conversation replaces scheduled syncs, and where the mix of engineers writing code next to recruiters screening candidates actually becomes workable. When a Founding Data Lead and a Backend Engineer sit in overlapping physical space, the gap between "what the data says" and "what the code can do" narrows in real time. That proximity matters more for Pocket than it would for a larger organization with dedicated liaison roles.
Remote flexibility, where it exists, serves a specific purpose rather than functioning as a blanket policy. The Backend Engineer posting and the Founding Data Lead posting both offer remote (US) options, which tells you something about how Pocket structures those functions: the work decomposes into tasks that can be shipped asynchronously, with synchronous checkpoints reserved for planning and review. The Founding Recruiter role also carries a remote designation, which makes functional sense: recruiting talent across a distributed company does not require the recruiter to share a physical office with the people being hired. The Customer Support Lead, by contrast, lists San Francisco only, which may reflect the coordination demands of managing a support team that needs tight alignment with product and engineering timelines.
For a candidate, the choice is straightforward. If you are applying for one of the three remote-eligible roles, you gain geographic flexibility but still join a company whose culture and decision-making rhythms orbit San Francisco. If you are applying for a San Francisco-only role, you are expected to show up physically, and the hiring process, covered above, will treat that as a given. Pocket has not published addresses or facility details, and the company's board listings do not describe dedicated offices, co-working arrangements, or satellite locations beyond the San Francisco base and the remote option. The absence of that information tells you something: for a small frontier-tech company, site specifics tend to be secondary to whether a candidate can do the work and fit the team's way of working. The physical site matters less as a landmark and more as a mechanism: it exists to let Pocket's departments operate as one team rather than six silos, and the remote option exists to extend that mechanism without diluting it.
Who Lasts
Pocket's board data narrows the field considerably. Nearly every opening carries the qualifier "Founding." That combination of founding-level titles, a wide pay spread, and remote flexibility filters for a specific kind of candidate: someone who wants to build infrastructure rather than maintain it, and who values output over title hierarchy.
The research on what makes employees endure in demanding environments is consistent. MIT Sloan Management Review's synthesis of 11 meta-analyses identifies three factors as the most powerful predictors of toxic workplace behavior: toxic leadership, toxic social norms, and poor work design. When all three are present, the employees who endure are those who find room to act even when the system is broken. Separate research on middle managers found they are 2.5 times more important than companywide factors in predicting employee misconduct, which means surviving a political, unstable environment requires someone who can manage upward, read the room, and protect their own output from the chaos around them.
There is a complication. Pocket's process is built to test what you can do, not where you come from — which implies a meritocratic filter. But companies that promote "lone wolves" over collaborative candidates see sales teams book nearly a third less revenue, and fewer than two in five respondents said leaders dealt promptly with employees who hit their numbers but cut ethical corners. The candidates who last are those who can self-direct when structures are thin, who ship work when communication from above has gone quiet, and who tolerate ambiguity without waiting for permission.
What the evidence points to is a specific archetype. Pocket's founding-level roles, including the Founding Data Lead, the Founding Recruiter, and the Founding engineer positions, are not jobs for people who want a defined career ladder. They are roles for people who want to construct the ladder itself. At Pocket's median pay and a ceiling near $300,000, Pocket is paying for the kind of autonomy that only self-directed builders can deliver. The candidate who thrives here is someone who has built things without institutional support, who can write clean code or ship a product with minimal scaffolding, and who does not mistake silence for disapproval or ambiguity for opportunity.
At Pocket, the interview panel is not a gatekeeper — it is a mirror. What you bring to the table is what you leave with. The credential that matters most was earned before you ever applied.
Working in frontier tech? Zero G Talent tracks the openings: see every open Pocket role, browse frontier tech jobs, the companies hiring, and the people building the field.