Pave Robotics Offers $140K for Role Requiring Zero Robotics Background

The Role: Co-Founder Without the Paperwork

Pave Robotics, a four-person Y Combinator-backed startup building autonomous road-repair machines, as the LinkedIn job posting shows, is hiring its first non-engineering employee, a Founder's Associate-Sales role that demands equal fluency in robotic crack-sealing specs and municipal procurement cycles. The title reads like a catch-all. The job description reads like a co-founder contract stripped of equity paperwork.

Founded in 2024 by Josh Kelly and Mason Landon Smith, Pave builds autonomous machines that seal pavement cracks. The founders come from Stanford, Zipline, NASA, and the engineering team behind Mark Rober's YouTube channel and Crunch Labs. The company's YC W25 batch page, confirmed by the LinkedIn job posting, lists three employees and two open engineering roles. This sales-operations hybrid is the only business-side position on the board.

The hire reports directly to Kelly and Smith. No sales manager, no operations lead, no CRM administrator. The posting makes this explicit: "You'll work directly with the founders across sales, customer deployments, project management, and company operations." The initial priority is equally direct — win customers and deploy the technology. That means cold-calling cities and paving contractors, navigating municipal procurement and public-works bidding, preparing proposals, building the CRM from scratch, coordinating field deployments, managing vendor logistics, and fixing whatever internal processes break along the way.

The posting breaks the first 90 days into concrete milestones. Days 1–30: learn the product, the customer, and the road-maintenance industry; join customer conversations and field operations; learn the pitch; begin independent prospecting; own pipeline organization. Days 31–60: run significant portions of the sales process; own follow-ups, help navigate procurement and contracting, coordinate upcoming deployments; start identifying and fixing broken or missing internal processes. Days 61–90: own meaningful opportunities from prospecting through deployment; converse comfortably with public-works directors, paving contractors, and field crews; coordinate deployments in the field; take responsibility for making projects actually happen.

Seniority is listed as entry level. Employment type is full-time. The function is business development and sales. The industry tag is robotics engineering. But the description explicitly rejects a narrow definition: "This is not a strategy-only role. If you want a narrowly defined job with established processes, this probably isn't the right role. If you want to help build those processes, work directly with the founders, and take ownership of whatever problems matter most to getting an early-stage robotics company off the ground, we'd love to talk."

The founders describe the ideal candidate as "extremely high-agency, organized, resourceful, and comfortable operating without a playbook." No road-maintenance or robotics experience is required. The ability to learn quickly, communicate well, and do both high-level and unglamorous work is. Some days the associate will work with founders on a major customer opportunity. Other days they'll call 30 paving contractors, chase paperwork from a city, build a process that doesn't exist, coordinate a nighttime deployment, or solve an unexpected problem in the field.

Pave expects the role to evolve significantly as the company grows. The posting notes exposure to nearly every part of building the company and the opportunity to take ownership quickly. Depending on strengths and interests, the position could develop into leadership in sales, business development, operations, or another major function. For a startup deploying physical robots on public roads, the hybrid profile isn't a compromise — it's the only way the business side keeps pace with the hardware.

Pay: What the Data Shows

The Y Combinator job description for this specific role prices it as a senior individual-contributor role with founder-track upside, not a junior sales development representative slot. The 3+ years experience requirement on the YC posting reinforces that.

Broader market context: across 429 active robotics roles on JobsRadar (46 percent publishing ranges), the median salary rose 6.5 percent year over year, as BLS labor statistics indicate.

Equity for early-stage YC companies typically follows a standard four-year vest: 25 percent after year one, then 2.08 percent monthly for years two through four. The YC posting does not specify the vesting schedule for this role.

Important distinction: Multiple compensation datasets in public sources reference "Pave", a compensation-software company (pave.com) with 8,000+ clients, as Pave.com reports, offices in San Francisco, New York, and Salt Lake City, and 16 open roles on JobsRadar. That entity is not Pave Robotics. Levels.fyi, RecruitingFromScratch, and JobsRadar figures describe the compensation-software company. They are excluded here.

How Pave Robotics Interviews

The LinkedIn job posting describes a four-stage process designed to move from initial conversation to decision in approximately two weeks:

1. Intro call: 20–30 minutes with a founder about background, motivations, and the role. Discussion focuses on situations where you've taken initiative, dealt with ambiguity, sold or persuaded people, and gotten things done without much structure.

2. Practical exercise (~60 minutes): a problem similar to something you might encounter at Pave, such as researching potential customers, thinking through a sales approach, planning a deployment, or solving an operational problem. The posting states they care "more about how you think and execute than producing a polished presentation."

3. In-person working session: 2–3 hours at their San Francisco office. You'll spend time with the founders and team, see what they're building, and work through a few real problems together. This is also an opportunity to get a realistic picture of the company, the role, and what working there is like.

4. References + offer, for strong candidates, they move quickly.

No first-party careers page for Pave Robotics (distinct from pave.com) appears in the research. Third-party interview data from Dataford describes the compensation-software company Pave, not Pave Robotics, and is excluded.

The Hybrid Skill Set: Technical Fluency Meets Procurement Literacy

The Founder's Associate, Sales & Operations role sits at an intersection that rarely exists in early-stage robotics: the candidate must speak the language of computer-vision crack detection and robotic sealant application while also navigating a procurement cycle that runs through state DOTs, municipal public-works departments, and private paving contractors. The LinkedIn posting and Y Combinator job description make this hybrid expectation explicit through the 30-60-90 day milestones and the target buyer list.

Technical fluency starts with the product itself. Pave's Tracer platform uses onboard cameras and lidar to map every crack in real time and classify severity as the platform works the lane, a purpose-built robotic arm that tracks each crack within a quarter inch and dispenses heated rubberized sealant on the exact path, and GPS-RTK plus visual odometry that keeps the sealing head locked to every crack while a driver tows and oversees the platform. Fleet telemetry logs every foot sealed with GPS, material flow, operator identity, and before/after photos. The specs — up to 2,500 feet per hour sealing rate, 125-gallon heated tank, ambient operating range of 20°F to 110°F, hybrid diesel-electric power, 16-hour run time on a single operator — are the vocabulary the hire will use daily with prospects who evaluate equipment on throughput, uptime, and total cost of ownership. A candidate who cannot explain why quarter-inch tracking matters for crack-seal longevity or how the heated tank maintains viscosity across that temperature band will lose credibility with a public works director who has watched manual crews fail the same test.

The sales competencies are equally specific, following the 30-60-90 plan outlined above. This is not a pure hunter role; it demands the operational discipline to manage a pipeline, the contract literacy to move a deal through a DOT purchasing office, and the field presence to stand beside a Tracer unit during a pilot and translate what the crew sees into actionable feedback for the engineering team.

The Y Combinator job description's target list, which includes paving companies, state or local DOTs, state or local public works departments, private equity firms buying paving companies, and large private parking lot or road owners, reveals the go-to-market motion. Each buyer type speaks a different dialect. A paving contractor cares about crew utilization and bid competitiveness. A state DOT cares about specification compliance, lifecycle cost models, and multi-year budget cycles. A private equity roll-up cares about EBITDA impact across a portfolio. The hire must code-switch across all five in a single week.

Soft skills are embedded in the "identifying broken or missing internal processes and fixing them" mandate at 60 days and the expectation that the role "evolves significantly as Pave grows" into potential leadership roles as described earlier. With a three-person team (as of the W25 batch), there is no handoff layer. The associate will write the first CRM workflows, design the first deployment checklists, and negotiate the first master service agreements. That requires a bias toward documentation, comfort with ambiguity, and the judgment to know when to escalate to founders Kelly and Smith versus when to decide and move.

Candidates who clear the screen will demonstrate they have sold complex hardware or infrastructure services into government or regulated markets, can read a technical spec sheet and translate it into a value proposition for a non-technical buyer, and have operated in an environment where process did not exist and they built it.

What the Screen Actually Tests

The interview loop Pave Robotics describes is short — four stages, roughly two weeks from first call to decision — but the company's own posting makes the bar explicit: they want "extremely high-agency, organized, resourceful" people who "see an ambiguous problem and start figuring it out rather than waiting for detailed instructions." That phrasing isn't aspirational; it's the rubric.

The first screen is a 20- to 30-minute conversation with a founder. The posting says they'll dig into the scenarios described earlier. Prepare three concrete stories that map to those four dimensions. One should show you cold-calling or cold-emailing a stranger and moving the conversation forward. One should show you taking ownership of a messy, cross-functional problem: coordinating vendors, chasing paperwork, building a process from zero. One should show you learning a technical domain fast enough to speak credibly with engineers. The founders' backgrounds signal they'll probe whether you can keep up technically even if you're not writing production code.

The practical exercise (roughly 60 minutes) is where the hybrid profile gets tested. The posting says it could involve the tasks described earlier and that they prioritize thinking and execution over polished presentations. Don't prepare slides. Prepare to work live: map a target account list for a municipal paving program, sketch the steps from first contact to signed contract, identify the operational blockers (permits, crew scheduling, nighttime deployment logistics), and propose a tracking system you could build in a spreadsheet or Notion page by end of day. Show bias for action. Ask clarifying questions about priority, then execute the first step while you're on the call.

The in-person working session (two to three hours at their San Francisco office) is the decisive filter. You'll sit with the four-person team, see the robots, and work through real problems as described earlier. This is where the 30/60/90 day plan in the job description becomes your prep document. Walk in ready to discuss how you'd structure the first 30 days: what you'd shadow, what questions you'd ask which stakeholders, and what pipeline hygiene you'd impose immediately. The team is small enough that "if something important needs to happen and nobody owns it yet, there's a good chance you'll own it."

The posting says "you don't need experience in road maintenance or robotics. You do need to learn quickly." Demonstrate that learning speed by doing the homework: read every public spec on their autonomous repair system, understand the paving-contractor procurement cycle, and come with a point of view on which municipal decision-makers hold budget authority.

Finally, calibrate to the culture signals. The posting emphasizes execution over perfection: "You'd rather execute than spend weeks discussing how something should be executed." The winning profile is the operator who ships imperfect work, learns from the field, and iterates in public. Show that you've done it before.

What This Article Does Not Cover

This article examines one role at one company — Pave Robotics' Founder's Associate–Sales opening — and the interview process built around it. It does not survey the autonomous road-maintenance robotics market, track funding rounds across the sector, or compare hiring strategies at competing startups. Those topics are real and material to anyone watching the space; they are deliberately excluded here.

Funding data for Pave Robotics shows conflicting public figures between Forbes and Aventure.vc. This article does not reconcile those discrepancies.

The Tracer unit waiting in Pave's San Francisco bay doesn't care about market forecasts. It only knows cracks, sealant, and the operator beside it — the one who called the city, chased the permit, built the checklist, and showed up at midnight to make the deployment happen. That operator is the person they're hiring.

Working in frontier tech? Zero G Talent tracks the openings: see every open Pave role, browse frontier tech jobs, the companies hiring, and the people building the field.