Want a $200K AI Role at Pulse? Its Screen Rewards Shipped Systems, Not LeetCode.

The Hiring Surge: Pulse's Nine Open Roles

Pulse, a 2,400-person (Pulse Careers reports) research and product company building "the quiet infrastructure behind modern life," shows nine open San Francisco-based engineering and AI roles on its first-party job board, Zero G Talent's first-party board data shows. The company reported 24% year-over-year growth, Pulse Careers' data shows, and €340 million in 2025 revenue, Pulse Careers' figures put it, while staying profitable after its Series D, and operates from seven offices across four continents with 63% of its business in the public sector, Pulse Careers found. That scale, combined with a market where demand for hands-on AI engineering skills climbed 51% between September 2025 and July 2026 (per Workday's analysis of 550 employers), explains the concentration of roles in San Francisco.

The roles span engineering, applied AI, and go-to-market: Growth and Marketing, Forward Deployed Engineer ($140K–200K), DevOps Engineer ($150K–210K), Machine Learning Engineer ($160K–220K), Software Engineer, Inference ($150K–230K), Design Engineer ($110K–150K), Software Engineer ($140K–200K), Account Executive ($100K–150K), and Business Development Representative (BDR) ($80K–120K). Salary bands across salaried roles run $94K–$223K with a $200K median, Zero G Talent's first-party board data shows. No remote roles are listed; every opening is San Francisco-based.

Third-party aggregators show slightly different counts; JobScroller and HighFit each read 10 roles as of October 10, 2026, but the first-party board is the source of truth for what's actually live and applyable. JobScroller verifies daily against Pulse's own careers page; HighFit re-scans every few hours. The discrepancy likely reflects a role that opened or closed between scrapes. What's consistent: engineering dominates (six of nine), the stack centers on NLP, computer vision, LLMs, Python, AWS, C++, Kubernetes, Terraform, and GitHub Actions, and seven of nine roles disclose pay up front.

The strategic driver isn't just growth — it's the shape of that growth. Forty percent of business leaders now expect AI to help them get more from existing employees; only 28% expect headcount reductions (Workday Global Workforce Report, October 2026). Pulse sits at the intersection: product demand is rising, but the talent market is flooding. Workday's 2026 data shows the median applicants per filled job hit 69, up from 58 a year prior; in tech and media, applications per role jumped 40% year over year, Workday's data shows. More than half of applicants in those sectors said AI tools increased how many roles they applied to, Workday found. That surge in volume is exactly why Pulse's screening process, the subject of the next section, has become the real gate.

The Screening Process: What We Know

Pulse uses Ashby as its applicant tracking system (evidenced by jobs.ashbyhq.com links on its postings). While the company doesn't publish its internal screening thresholds, the multi-stage process typical for AI-native companies at this scale involves: initial resume review against stated requirements, automated technical assessments for engineering roles, and structured interview loops. The volume data from Workday (69 median applicants per filled role, 40% year-over-year increase in tech/media) means even a well-calibrated filter eliminates most applicants before human review.

Industry research on hiring workflows notes that "the most visible points of friction often emerge during handovers" between screening stages (People Matters, TechHR Pulse Philippines 2026). Pulse's nine simultaneous roles amplify that risk. The company's founders (Sid Manchkanti, Janeane Mooring, Akshay Kothari, Ankit Gupta, Akshat Goenka, Ritvik Pandey, Anand Thaker, Mayank Mehta) have built a team that ships production-grade document extraction; their hiring loop reflects the same precision.

The Hidden Scorecard: Qualifications That Move the Needle

Pulse's job postings read like a spec sheet for the exact problem they're solving: production-grade unstructured document extraction at scale. The Machine Learning Engineer role, listed at $160K–220K, makes the baseline explicit: three-plus years in applied ML or research, or a strong open-source record. PyTorch or JAX. Modern vision or multimodal architectures. Solid engineering discipline and metrics focus. That last phrase does heavy lifting. Pulse isn't a research lab; it ships an API suite that ingests PDFs, Word, and Excel, runs layout understanding with specialized component detection, low-latency OCR, reading-order algorithms, proprietary table parsing, and fine-tuned vision-language models for charts and figures — then hands structured output to downstream LLMs. The "nice to have" list (Triton Inference Server, TensorRT, ONNX, distributed training) isn't decorative. It signals the inference stack candidates will touch on day one.

The Software Engineer, Inference role ($150K–230K) and DevOps Engineer ($150K–210K) reinforce the same theme: serving vision-language models at low latency, with signed webhooks (launched via Svix on 2026-09-03) replacing polling loops for enterprise customers. Fountain embedded Pulse directly into Compliance, not as a standalone tool, and reported 90% faster processing with 98% extraction accuracy as of March 4, 2026 (Pulse blog). That integration depth means screeners weight candidates who have shipped model-serving infrastructure, not just trained models. A Forward Deployed Engineer ($140K–200K) sits at the customer boundary; the role demands fluency in the same stack plus the ability to map messy enterprise documents (supply-chain invoices, complex financial tables, mathematical equations) to Pulse's Formula Recognition and schema-mapping pipeline.

The Design Engineer role ($110K–150K) reveals another priority: human-in-the-loop tooling. Unsiloed AI's July 2026 review dinged Pulse for lacking confidence scores, classification, and schema versioning — gaps that Extend's March 2026 review highlighted as strengths (99%+ accuracy, evaluation, human-in-the-loop). Candidates who have built review interfaces, confidence calibration, or active-learning loops for document AI move up the stack fast.

Market data backs this: 62% of product-manager posts now mention AI familiarity, AI PM titles are up 130% year-over-year, and 28% of new PM contracts are AI-related (Product Leader Academy, Market Pulse Q4 2025). But Pulse's technical roles demand proof of impact (saving time, cutting cost, increasing revenue), not just familiarity. The Account Executive ($100K–150K) and BDR ($80K–120K) roles target Fortune 100, YC startups, public investment firms, and growth-stage companies; sellers who can articulate the ROI of 98% extraction accuracy on compliance workflows outpace those pitching generic "AI document processing."

Remote roles are shrinking industry-wide; only 22% of product openings are remote versus 46% in 2022 (Product Leader Academy), and Pulse's board shows zero remote listings. The Growth and Marketing hire, added recently, suggests the next push is top-of-funnel for a product that already powers enterprise compliance. Screeners know the difference between a candidate who has fine-tuned a vision-language model for table parsing and one who has only called an API. The scorecard is narrow, and the evidence bar is high.

The Applicant Playbook: Strategies That Work

Pulse's screening process rewards candidates who treat the application as a product problem: identify what the buyer values, then build a submission that demonstrates it. Research converges on three levers that consistently move the needle at AI-native companies — AI fluency with judgment, shipped systems over algorithmic trivia, and signal density in every artifact you submit.

Demonstrate AI Fluency, Not Just AI Usage

Coinbase's redesigned engineering loop explicitly tests three dimensions: usage (effective, responsible tool use), application (knowing when AI is and isn't the right solution), and understanding limits (where models break down) (Coinbase blog, July 2026). Pulse builds developer tools for AI teams; its interviewers will probe whether you can direct an assistant to explore a design space (generating schemas, drafting API contracts, stress-testing failure modes) while regularly applying the judgment the model cannot substitute for. In practice, this means your technical assessment and onsite conversations should show you catching subtle bugs an LLM introduces, reasoning about rollback scenarios in a repo you didn't write, and explaining why you accepted or rejected a generated change. Candidates who pass the AI-assisted coding assessment advance through onsites at a meaningfully higher rate than those on the old assessment, per Coinbase's data. Prepare by working in realistic codebases with Copilot or Cursor: debug a failing test, refactor a legacy module, add a feature with guarded migrations. Document your prompts, the model's output, and your critique — that artifact becomes a talking point.

Lead With Shipped Systems, Not LeetCode Ratings

Multiple startup founders confirm the same hierarchy: competitive programming doesn't matter much for early-stage roles. What counts is whether you've built real systems that actual users interact with (Emergent Labs interview experience, LinkedIn; Reddit r/datascience). Pulse's open roles all sit on the execution side of AI infrastructure. Your resume bullets should map to the problems those roles solve: latency optimization for inference serving, observability pipelines for multi-step agents, evaluation frameworks that catch regressions before users do. Use the C-A-R framework (Context → Action → Result) for each bullet. Quantify: "Reduced p99 latency 40% by rewriting the batching layer in C++" beats "Optimized inference performance." If you lack production scale, show a side project that real developers used — a CLI tool with 500 GitHub stars, a VS Code extension with 2,000 installs, a Discord bot serving 50 servers. Startups value speed, ownership, and prior hands-on experience far more than ratings or theoretical knowledge.

Master the Behavioral Layer With AI-Native Evidence

Coinbase kept its leadership and behavioral round but added direct questions about how candidates use AI in day-to-day work: concrete behavioral evidence, not abstract capability (Coinbase blog). Prepare STAR stories (Situation, Task, Action, Result) that showcase: a time you chose not to use AI because the risk outweighed the speed gain; a time you caught a hallucinated API signature before it hit staging; a time you designed an eval harness that caught a regression the model missed. Interviewers care less about whether you reach a perfect solution and more about how you reason, communicate trade-offs, and recover when you hit a roadblock — especially in AI and ML-heavy rounds (Guvi, FAANG interview experience). Admit knowledge gaps honestly; pretending to know everything is a red flag. A senior engineer at a FAANG AI lab put it plainly: "Learning to admit knowledge gaps honestly rather than pretending to know was what got me through the loop."

Optimize the Top of Funnel: Fresh Postings and Warm Intros

Application timing and routing materially affect visibility. A documented strategy: apply directly to positions that are fresh (0–3 days old) where competition is less intense, then immediately reach out to connections at the target company for referrals, sharing both resume and specific job links. A good internal referral is the highest hiring signal for most companies (Guvi). Pulse's board shows 8 salaried roles posted from San Francisco; the Growth and Marketing role was added recently. If you know a current Pulse engineer (founders include Sid Manchkanti, Akshay Kothari, Ankit Gupta, Akshat Goenka, Ritvik Pandey), a warm intro with a tailored note ("Saw the Forward Deployed Engineer role; my last project was a RAG pipeline serving 10K daily queries, happy to walk through the eval design") beats a cold submit every time.

Tailor the Resume to the ATS and the Human

Your resume is a positioning document that tells hiring managers who you are in under 10 seconds. Global Work AI's analysis of 1.2 million monthly postings shows ATS systems filter heavily on keyword overlap with the job description (Pulse 2.0 interview). Mirror the language: if the JD says "inference optimization," "multi-step agents," "observability," those phrases belong in your skills section and top bullets. But don't keyword-stuff; the human reviewer reads for narrative coherence. One page for <5 years experience; two pages max beyond that. Lead with a two-line summary: "ML engineer shipping LLM inference systems at scale. Built eval pipelines cutting false-positive rate 60%. Python/C++, Kubernetes, Triton." Then reverse-chronological roles with C-A-R bullets. Include a "Projects" section for shipped side work. Remove coursework, GPA, and generic "proficient in" lists.

Prepare for the Extended Technical Conversation

FAANG AI interviews frequently stretch to 90 minutes when interviewers dive deeper into problem-solving and system design (Guvi). Pulse's technical rounds will likely follow suit. Build stamina: practice 90-minute mock sessions where you design a system end-to-end with an AI assistant (schema, API, failure modes, rollout plan) while narrating your judgment calls. Focus LeetCode practice on medium-difficulty questions; these form the core of most interviews, whereas hard problems rarely appear (Guvi). Establish a sustainable routine of 1–3 hours daily rather than irregular weekend cram sessions. And rehearse the basics: a candidate who failed a datetime question they'd dismissed as trivial warned peers: "Focus more on the basics, never did I think that I'll fail a question on 'datetime', so don't be reckless and practice all the basics regularly" (LinkedIn interview experience).

Close the Loop After Every Interaction

Treat each interview round as a data-gathering step. After the recruiter screen, ask: "What's the one skill the team wishes more candidates demonstrated?" After the technical round, follow up with a one-paragraph note referencing a specific discussion point ("Enjoyed the debate on eval-driven development — here's a link to the open-source harness I mentioned"). After the onsite, send a decision-framework memo: "If I joined, here's how I'd approach the inference latency problem in my first 30 days." This isn't performative; it's the same judgment-first, artifact-driven workflow Pulse's engineers use daily. The candidates who advance are the ones who make the hiring committee's job easy — by showing, not telling, that they already work the way Pulse works.

What's Out of Scope: Boundaries of This Analysis

This article examines one company's hiring machine. It does not explain the tech labor market, the AI displacement debate, or what any other employer is doing. The research makes those boundaries necessary.

Pulse sits inside a sector that shed roughly 33,600 net jobs in 2025, a 0.3% decline CompTIA documented in its State of the Tech Workforce 2026 report. The same report projects 1.9% growth this year, pushing the national tech workforce toward 9.8 million. Those numbers frame the backdrop — they do not drive this analysis. We do not test whether Pulse's nine open roles reflect, contradict, or lead that trend. The article treats the company's current requisitions as a given and works inward from there.

The same discipline applies to the AI hiring surge. CompTIA counted over 275,000 active U.S. postings referencing AI skills in January 2026. Lightcast found 51% of those postings sit outside traditional IT and computer science roles. PwC's 2026 Global AI Jobs Barometer, built on more than a billion job ads across 27 countries, measured a 62% wage premium for AI skills, up from 57% a year earlier. Dice recorded a 101% year-over-year jump in AI and machine learning postings by August 2026. None of that breadth appears here. Pulse's roles ask for AI fluency; the article evaluates how the company screens for it, not how the market prices it.

We also exclude the structural reset SignalFire's 2026 State of Talent report describes. Engineering hiring at Tech Majors runs 11% below the 2019 baseline; at early-stage startups it is up 7%. Design is down 48% at majors and 22% at startups. Product management down 39% at majors, up 2% at startups. Marketing down 36% and 18% respectively. New-graduate hiring has collapsed 65% at majors and 76% at startups versus 2019. Top computer science graduates in 2025 were 45% less likely to land a large-tech engineering role than the class of 2022, and twice as likely to call themselves founders. Those patterns explain why the talent pool looks the way it does. They do not explain how Pulse filters that pool.

We do not cover compensation benchmarking across the sector. Levels.fyi measured median total compensation growth of 3.5% across U.S. software engineering levels in 2025. Principal engineers saw a 6.6% decline to $551,000; staff engineers gained 7.5% to $457,000. The Bureau of Labor Statistics put the median software developer wage at $135,980 in May 2025. Dice's 2024 survey found an average tech salary of $112,521, up 1.2%, with 59% of respondents feeling underpaid. CompTIA's median U.S. tech wage reached $112,805 in 2024, 126% above the national median. Pulse's posted bands sit inside those ranges. The article notes the bands; it does not litigate them.

We do not survey other AI labs' hiring. SignalFire reports AI labs (OpenAI, Anthropic, Google DeepMind, xAI, Mistral, Cohere) now maintain higher HR (9.2%), Finance (5.1%), and Legal (2.3%) ratios than incumbent tech giants, and their org charts are converging with big tech as they scale. Microsoft moved 6,000 employees into a new Frontier Co. subsidiary for forward-deployed engineering, backed by $2.5 billion. Amazon, Anthropic, and OpenAI announced similar deployment groups. Accenture and EY allied with Microsoft on AI-centric programs. Those moves shape the competitive landscape for talent. They do not shape Pulse's scorecard.

We do not analyze policy responses. Governor Newsom's May 2026 executive order directs California agencies to explore severance standards, employment insurance, transition support, worker ownership models, universal basic capital concepts, expanded workforce training, and stronger hiring and payroll tracking. The state has supported more than 674,000 earn-and-learn opportunities since 2019, including 250,000 registered apprenticeships. UC Extension serves 300,000 people annually; a new Degree Plus pilot combines bachelor's degrees with skills certificates and paid internships. Nearly $750,000 went to the California Workforce Association for a statewide AI workforce strategy. Those levers affect the pipeline long-term. They do not affect this cycle's screen.

We do not project futures. CompTIA forecasts tech occupations growing at twice the overall U.S. employment rate over the next decade, with data scientists up 420%, cybersecurity analysts up 346%, software developers up 188%. The BLS expects 10% growth for software developers, testers, and QA analysts from 2025 to 2035, roughly 106,100 openings annually. Texas leads state gains with 32,238 net new tech jobs forecast, then California (16,949) and Florida (14,453). The Stanford lab's Canaries Dashboard will update monthly; its researchers explicitly state they do not know whether documented patterns will accelerate, stabilize, or reverse. Gartner predicts a quarter of candidate profiles could be fake by 2028. This article stops at the current screen.

What remains is Pulse: nine roles, a multi-stage filter, and the specific qualifications and tactics that move candidates through it. The screening threshold doesn't care about the macro trend. It cares whether your resume shows you've shipped the thing they're building. Everything else is context — real, documented, and deliberately left outside the frame.

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