Lab0’s Three-Hire Funnel Puts the AI Gate First

The AI Gate

Lab0 has opened three roles: forward-deployed engineer, founding product marketer, and founding engineer, and the first reader of every application is not a person. It is an AI-powered applicant tracking system that ingests resumes for these positions.

By the end of 2026, 83% of companies will use AI to screen resumes, a Reddit hiring-manager survey shows. According to r/jobhunting on Reddit, ninety percent of those managers report a surge in what they call spammy, low-effort applications. LinkedIn data from September 2026 puts the flood at roughly half of all candidates now using AI to craft or polish their materials. "Your ATS is not filling up with better candidates," a recruiter wrote on LinkedIn. "It's filling up with better-looking applications."

Lab0, which develops the RoboGlide system for container unloading, palletization, and real-time motion planning in warehouses, sits inside this arms race. Its leadership, comprising founder David McCalib, CTO Vadim Tikhanoff, COO/CFO Felipe Collares, and advisory-board members Kelly Reidel (LightForce & Amazon Robotics) and Pulkit Agrawal (MIT), has built a company around physical AI that adapts in real time. Its hiring stack now applies a similar logic to the people who would build the next generation of that technology.

The screening layer operates on pattern matching at scale. Keywords from the job description ("motion planning," "simulation-to-reality," "computer vision," "ROS 2," "CUDA") carry weighted scores. Structural signals matter: clear project ownership, quantified outcomes, domain-specific toolchains. The Estée Lauder case, where staff won a payout in March 2022 after being evaluated by algorithmic hiring tools, remains the cautionary benchmark: opaque scoring can embed bias and exclude qualified candidates who don't mirror the training data. NYU's career center, in February 2024 guidance, advises applicants to mirror the exact phrasing of the job description — a tactic that works until the model updates its weights.

For Lab0 applicants, the impact is immediate. A resume that lists "robotics experience" without naming the stack, the scale, or the failure modes gets filtered. One that stuffs every keyword from the posting triggers the spam detector. The gate rewards specificity: the candidate who writes "optimized CUDA kernels for 200 Hz lidar preprocessing on Jetson AGX" passes; the one who writes "experienced with GPU acceleration" does not. The system does not read for potential. It reads for evidence that matches the vector space of the role.

What clears the gate then faces a human — but only after the model has narrowed the pool to a fraction of the inbound volume. The next filter is not another algorithm. It is a technical evaluation designed to prove the resume was not written by the same model that screened it.

The Technical Crucible

Lab0's technical domain is not abstract. The company builds AI agents that sit inside live ERP implementations, including Salesforce, ServiceNow, Oracle, Microsoft Dynamics 365, SAP, Adobe Experience Manager, and Workday, and the connective tissue between them. A forward-deployed engineer configures platforms, writes integrations and connectors, migrates data, and builds workflows that take a customer from first conversation to production go-live. The job description makes this explicit: "You'll take enterprise software implementations from the first customer conversation to a working system in production." That scope, including discovery, configuration, integration, testing, and delivery, defines the technical surface any assessment must cover.

ServiceNow alone carries roughly 4,000 fields; for a single procurement-to-IT handoff, about fourteen matter, and they are scattered across tables, statuses, and naming conventions. Coupa's "requester email" maps to ServiceNow's "requested for." Approval statuses do not align. The hard part, as Lab0's own documentation puts it, "is the handoff between Coupa and ServiceNow." Most fields line up once renamed; the approval status does not, and it is not a straight swap. Knowledge lives in kickoff calls, specs, and people's heads — "no single person or document has the full answer." An engineer who cannot reason across schema mismatches, API quirks, and undocumented platform behavior will not last.

Frontier-tech hiring at this level follows a documented pattern. Palantir's technical process, described in a 2026 recruiting video, tests "more than basic coding skills" and "challenges how you solve unfamiliar technical problems." The assessment covers programming fundamentals, logical reasoning, and technical problem-solving. Coding questions involve arrays, strings, hash maps, linked lists, trees, and graphs. Algorithms and data structures, including searching, sorting, recursion, graph traversal, dynamic programming, and big-O complexity, are baseline. Problem-solving questions escalate: "A technical question may become harder as requirements change." System design discussions cover APIs, databases, distributed systems, scalability, reliability, and data pipelines. The goal is an efficient solution, not just an answer; candidates must explain their approach, handle edge cases, and improve the solution when constraints increase.

Lab0's work maps cleanly to that framework. Its config agent "implements systems through APIs and browser automation, reverse-engineers undocumented behavior, and writes connectors and workflows in languages such as ABAP and X++." Its testing agent "finds configuration problems, tests edge cases, and supports user acceptance testing." The discovery agent "joins customer meetings, asks questions, gathers requirements, and calls tools in real time." Each agent operates on a per-client semantic layer that preserves context across implementations — "the first implementation creates the pattern; every change after it starts ahead." A technical assessment that does not probe multi-system reasoning, schema mapping under ambiguity, and the ability to build and debug agent-driven workflows would miss the job.

Lab0's job postings read less like requirement lists and more like briefs for the work itself. The founding product marketer role asks for a portfolio of polished work you personally made, with clear ownership of the writing, design, or production. The forward-deployed engineer role requires three-plus years of software engineering or technical implementation with work you've personally shipped. Both postings lead with output, not credentials.

This tracks with a broader shift in frontier-tech hiring. Skills-based hiring evaluates what candidates can actually do, and research shows it produces stronger hires with lower turnover. Credentials help raise the likelihood that someone has required skills, but they should never be confused with the skills themselves. Lab0's postings make that distinction explicit: they want to see the work, not the degree that might have preceded it.

AI fluency appears as a non-negotiable for both roles, but defined narrowly. The product marketer must walk through a workflow built with Claude, explain how they check its output, and identify where their judgment improves it. The engineer needs regular use of AI coding tools and agents with judgment about how to test and verify what they produce. Neither role treats AI as magic. Both treat it as a tool that fails in specific ways — and the hire is the person who catches those failures before a customer does.

Customer-facing ability carries equal weight. The product marketer needs comfort talking to customers and presenting live, asking good questions and turning an incomplete brief into finished work. The engineer owns customer implementations end to end, surfaces problems early, and cares whether the customer can actually use what's been built. Lab0's product sits in the messy middle of enterprise software rollouts where ServiceNow alone has roughly four thousand fields and about fourteen matter for any given workflow. No single person or document holds the full answer. Knowledge lives across kickoff calls, docs, specs, and people's heads. The hire is the one who can navigate that fragmentation without waiting for a handoff document that will never arrive.

Ownership through the messy parts of delivery appears in both postings almost verbatim. Follow through. Surface problems early. Care whether the customer can actually use what you've built. This isn't culture language — it's a job description for the problem space. Lab0's agents keep context across implementations so each change runs against what the system already knows about a client's setup. The initial implementation sets the pattern; subsequent changes begin ahead. But the human layer still has to recognize when requirements move, such as a new approval threshold, another system to connect, or a field finance now wants on every request, and decide whether the agent's suggestion matches the customer's actual need.

The hiring manager's signal is simple: show me something you built that survived contact with reality. A portfolio piece that a senior buyer would take seriously. A workflow you automated, verified, and improved when it broke. A customer conversation you turned into a reusable asset the whole team can use. The ATS filters for keywords. The human filter looks for evidence that you've already done the job.

The Human Layer

The AI filter and technical screens narrow the pool, but they don't make the hire. At Lab0, as at most frontier-tech companies, the final gate is human — and it operates on signals no model can reliably score.

Research on cultural-fit assessment describes it as a combination of methods designed to determine whether a candidate will work well with the existing team and thrive in the company culture (AIHR; Cowen Partners, 2022). The U.S. Office of Personnel Management lists structured interviews, accomplishment records, and emotional-intelligence measures among validated job-fit methods. In practice, this layer translates to behavioral interviews, reference checks, and team interactions — stages where nuance, context, and judgment override keyword matches.

Aviator, another Y Combinator company, illustrates the pattern: after technical screens and a take-home project, candidates face three to four hour-long technical interviews (45 minutes of problem-solving, 15 minutes of Q&A), all conducted via live IDE screenshare using the candidate's own environment and tools. Crucially, Aviator "strongly weighs on references and would ask for 2 references during or after the interviews… former teammates, manager, etc." — a human signal that no ATS captures (Y Combinator, Aviator job posting). The intro call frames the entire sequence: "Get to know the product, vision and see if this will be a good fit."

Lab0's public positioning emphasizes small, high-leverage teams: "We believe the future of software development isn't engineers replaced by AI — it's engineers supercharged by it. Small teams will ship what once required hundreds of people" (Y Combinator, Lab0). That philosophy implies a cultural filter for autonomy, collaboration with AI agents, and comfort compressing "six months of services work… into days." But Lab0 has not published its interview rubric, behavioral-question bank, or reference policy. The research contains no Lab0-specific description of final-round interviews, panel composition, or cultural-fit criteria.

What the broader data shows is consistent: frontier-tech hiring managers treat the human layer as a correction mechanism. Automated screens optimize for recall; human interviews optimize for precision — probing whether a candidate who passes the technical bar will actually ship in a high-velocity, agent-augmented environment. Candidates who reach this stage at Lab0 should expect the conversation to shift from "can you code?" to "how do you decide what to build, how do you work with agents, and how do you handle the friction of dependent work?" — the same dimensions that surface in structured behavioral assessments across the industry.

The gap between Lab0's public mission and its undisclosed interview process is itself a signal. In the absence of a published playbook, the candidates who advance are those who can articulate, without prompting, how they operate in the small-team, agent-supercharged future Lab0 describes.

Candidate Playbook

The resume that reaches a human at Lab0 has already survived a gauntlet most applicants never see. Research from NYU, Indeed, and ACI Learning converges on a single pattern: the candidates who clear AI screens treat the resume as a structured data object, not a narrative document. The tactics that work are mechanical, repeatable, and surprisingly narrow.

Formatting comes first. Over 200 ATS platforms parse resumes differently, but they share failure modes. Tables, columns, graphics, and special characters (ampersands, tildes, em dashes) scramble parsers. NYU's 2024 guidance stresses a single-column layout with standard headers: Contact Information, Summary, Skills, Experience, Education. Indeed's 2026 checklist adds that contact details must live in the document body, not headers or footers, and dates should follow "MMM YYYY" format. Stripping creative formatting alone moved one documented screen rate from 5 percent to 20 percent. The file type matters too: .docx remains the safest default unless a posting explicitly requests PDF.

Keywords operate on a precision threshold. NYU's research identifies a 60–85 percent match rate as the sweet spot; resumes that mirror the job description 100 percent trigger copy-detection filters. The strategy is surgical: pull priority skills, tools, and certifications from the posting, repeat each two to three times across the Skills and Experience sections, and include both singular and plural variants. Acronyms get spelled out on first reference, for example "Field-Programmable Gate Array (FPGA)," so the parser catches both forms. A training document circulating among job seekers prescribes a bullet structure that feeds parsers exactly what they expect: "[what you did] -> [the result] -> [the outcome in metrics]." Quantified achievements survive ranking algorithms; vague responsibilities do not.

LinkedIn has become a parallel data feed. Platforms now track behavioral signals, including clicks, dwell time, and connection requests to company employees, and feed them into recruiter recommendation engines. NYU notes that candidates who interact with a target company's content before applying surface higher in ranked stacks. Messaging talent acquisition directly via LinkedIn InMail or connection requests, bypassing the portal entirely, quadrupled one practitioner's interview rate. The portal stays the compliance path; the message becomes the signal.

Generative AI enters as a drafting tool, not a submission engine. The same Reddit thread advises prompting an LLM for a first draft built from the job description, then rewriting heavily to restore human cadence. ACI Learning warns against keyword stuffing, as parsers now detect unnatural density, and insists on consistency between resume and LinkedIn. Discrepancies in titles, dates, or skills flag the application for manual review, which in high-volume pipelines often means auto-rejection.

The playbook ends where the human layer begins. A clean, keyword-aligned, metrics-heavy resume in .docx format gets you past the filter. The technical assessment that follows tests whether the experience behind the keywords holds up under scrutiny. Candidates who optimize only for the screen tend to stall at the evaluation. The ones who advance build the resume around evidence they can defend.

Industry Ripples

Lab0's three-stage funnel, consisting of AI resume screen, technical assessment, and human interview, mirrors a shift accelerating across the frontier-tech labor market since roughly 2023. The U.S. space economy employed over 373,000 private-sector workers that year, per Bureau of Economic Analysis figures, and the defense-aerospace sector is growing faster than it can staff itself, with the U.S. A&D market valued at $463 billion. That supply-demand imbalance is forcing every major player to automate the top of the funnel while doubling down on verified domain competence downstream.

The clearest parallel is the industry-wide move toward skills-first hiring. Defense recruiters tracking 2026 trends explicitly cite "skills-first hiring, accelerated clearance processing, and community-based talent pipeline development" as the three levers they are pulling. Lab0's technical crucible, practical evaluations after the AI filter, is the operational expression of that philosophy: keywords get you past the gate; demonstrated capability gets you an offer. The same logic drives NASA's State Hubs for Skilled Technical Workforce initiative, which kicked off September 15, 2026 at Space Center Houston to build regional pipelines that bypass traditional degree gates.

Clearance velocity is the other accelerant. All technical-track employees at The Aerospace Corporation, a 4,600-person FFRDC founded in 1960, must obtain and hold at least a Secret clearance, and U.S. citizenship is non-negotiable for those roles. The industry response has been to front-load clearance sponsorship and pre-screen for eligibility before a human ever reads a resume. That is exactly what an AI-driven ATS can do at scale: flag citizenship, clearance history, and export-control status in milliseconds, while the technical assessment validates the engineering chops that clearance alone doesn't guarantee.

Compensation data confirms the premium on this intersection of clearance and hard tech. First-party board data from Zero G Talent shows the following base salary bands:

Lab0's offers reflect an earlier-stage company. The Aerospace Corporation's band includes an 8–12% 401(k) match and 9/80 schedules.

Mobile-first application flows are the other observable shift. Indeed reports that mobile-app users get hired 30% faster on average across aerospace-AI listings. Lab0's ATS parses resumes on phone screens, surfaces skill signals, and routes to technical evaluation. The candidates who optimize for that parse, including clean formatting, project-level detail on ERP integration, schema mapping, or agent-driven workflows, are the ones who clear the AI gate. Everyone else disappears into the "review later" queue that never gets reviewed.

The Space Workforce for Tomorrow initiative, powered by the Space Foundation, frames this as a national STEM gap. The BEA itself admits that "little is known about the occupations within these industries, resulting in an incomplete understanding of the current skillsets of the space workforce and future skills needed." Lab0's process, along with every similar funnel at SpaceX, Blue Origin, Northrop, and the FFRDCs, is effectively a private-sector workaround for that data void. They define the skills they need, build the test, and let the AI filter for the proxy signals. The trend isn't toward less human judgment; it's toward human judgment applied only to candidates who have already proven they speak the language.

The software that read your resume for keywords will never sit across the table from you. The engineer who does has already seen the same schema mismatches, the same undocumented error codes, the same requirement that shifts at 4 p.m. on a Friday. They know the difference between a candidate who has lived that mess and one who only knows the words for it. The gate was built to keep the latter out. The interview exists to confirm the former is real.

Working in space? Zero G Talent tracks the openings: see every open SpaceX role, browse space jobs, openings at Blue Origin and Northrop Grumman, and the people building the field.