Skip to main content
frontier

Tenex.ai Hires Fast While Screen Rejects Half of Applicants

By Priya Nair

Tenex.ai Announces Major Hiring Expansion

Tenex.ai, an eighteen-month-old cybersecurity startup, announced a major hiring push across its engineering and product teams after closing a $250 million Series B on March 31, and promptly tightened its technical screening to accept only candidates who can demonstrate end-to-end AI system delivery. The round was led by Crosspoint Capital with Andreessen Horowitz, Shield Capital, DTCP, Deepwork Capital, and the Florida Opportunity Fund joining.

Sarasota-based Tenex left stealth in January 2025 and booked first revenue two months later. By the Series B close, it held $25 million in contracted revenue and fewer than 200 people. The new money targets engineering, sales, and round-the-clock security operations: a pledge to add more than 250 roles in 2026.

CEO Eric Foster, a former Mandiant and Trustwave executive, laid out the pace in a late-February interview: 75 people after year one, near 100 soon after, and close to 300 by year-end. That clip (about 20 net hires a month) would make Tenex one of the fastest-scaling pure-play AI security vendors in the U.S. President Bashar Abouseido, named alongside the Series B after a decade as Charles Schwab's CISO, will run the operational scale-up.

Investors are betting on a revenue jump from $25 million to $100 million in annual recurring revenue by December: a fourfold ramp in nine months. TodaysStartupNews put the post-money valuation above $1 billion in April, implying a 25-to-40 multiple on contracted ARR. The wager rests on Tenex's claim: its AI agents chew through every alert, triaging, investigating, and containing threats in under a minute, cutting false positives by 95 percent versus the old managed-service baseline.

Analysts at Morgan Stanley and Goldman Sachs say the round shows the agentic-SOC category consolidating around a few well-funded players. Goldman's Gabriela Borges wrote that the capital stack mirrors what CASB and SASE saw in 2018–2020, a sign the category has graduated from venture experiment to enterprise staple. Forrester's Allie Mellen called it the round confirming the AI SOC has crossed that line.

The hiring push doesn't sit in a vacuum. IDC's Frank Dickson calls it the biggest budget shift since the move from on-prem SIEM to cloud-native XDR, with CISOs moving money from headcount augmentation to outcome-based services.

Category Metric Value Source
Market Size SOC-as-a-service market (2025) $15 billion IDC forecast
Market Size SOC-as-a-service market (2031) $27 billion IDC forecast
Market Size Total cybersecurity spend (2025) $520+ billion IDC forecast
Salary Median salary (ML/infra/product roles) $154k ASML (65 roles)
Salary Median salary (ML/infra/product roles) $235k Stripe (48 roles)
Salary Salary range (ML/infra/product roles) $49k–$289k Stripe

That shift frames Tenex's screen and the applicant surge that followed the announcement.

Applications Surge, But Data Lags

Tenex has released no application metrics, demographic breakdowns, or funnel data. A YouTube video from mid-2025 describes 10XAI, a Google Cloud security partner also backed by Andreessen Horowitz and led by CEO Eric Foster and CRO Edwin Ciss. That video pitches the Google partnership as a talent draw but discloses no application volumes or conversion rates.

The pattern is familiar: frontier-tech firms that announce a hiring push tied to a marquee platform partnership (here, Google Cloud security operations plus Gemini) typically see a sharp, short-lived influx from three overlapping pools. Cloud-security practitioners certified on the partner stack. AI engineers drawn by the "10x" productivity narrative. Generalist software engineers rebranding toward "AI delivery" roles. The 10XAI video frames it plainly: partnering with Google puts recruits in the driver's seat of the most advanced technology out there.

Research gap: No primary source quantifies Tenex's application spike, breaks candidates by background (former big-cloud, startup, defense), or reports screening pass rates. Until Tenex or a credible third party publishes those figures, any demographic claim is invention.

What the Screen Actually Tests

Tenex rejects the industry default. While most firms have dropped take-homes in the age of AI-generated code, Tenex makes its own "unreasonably difficult" (the company's phrase, unapologetic). The loop moves fast: two screening calls, the take-home, a review session, one or two final meetings, all done in a week. But speed masks severity. Roughly half the candidates who get the take-home never reply. Those who finish signal the caliber Tenex demands.

The take-home isn't a coding puzzle. It's a system-design exercise built on the work Tenex actually ships: architect, prompt, evaluate, and iterate an LLM pipeline that holds up in production. The rubric weights judgment over syntax. How does the candidate handle ambiguity? Where do they invest validation? Do they see the failure modes that emerge when autonomous agents run for hours, not minutes?

A signature question in the live interview: "If you had infinite resources to build an AI that could replace either of us on this call, what's the first major bottleneck?" Naive answers — model intelligence, context length, compute — fail. Tenex wants "controlling entropy": the accumulating error rate that derails autonomous agents over time. Candidates who reach that answer have felt the pain of long-horizon agent runs. They know retrieval drift, tool-call cascades, and silent hallucinations compound non-linearly. They know the mitigations: structured reflection loops, external verification, bounded context windows, explicit failure budgets.

The screening calls filter differently. Foster describes two target profiles. First, engineers who are "long-term selfish" — they know inflating story points or skimping on evaluation eventually burns client relationships and their own leverage. Second, engineers who genuinely love writing code and working with sharp peers. "Long-term selfish" selects for alignment without performative mission talk.

A final gate sits outside the engineering loop. Technical strategists, incentivized on net revenue retention, review every engineering plan before it hits a client. The screen becomes a two-way contract: the candidate proves delivery; the company proves it won't ship work that erodes trust.

The process hunts "AI slop." Evaluators catch pasted LLM output; they know the texture of unedited generation. One candidate who cold-emailed Foster wrote the note herself ("ironic for an AI firm," she noted) to avoid generated text. Foster said the human touch, research, and customization in that email "speaks way more than any formal application process." The same standard applies to the take-home.

Tenex bets this filter scales. The company pays above market — "an order of magnitude better performance because we hire the best of the best" — and runs lean. Its head of engineering reportedly built in a weekend what would take a traditional team three months of coding and six months end-to-end. The screen keeps that density high. Every hire must raise the bar for the next.

What Actually Gets Candidates Past the Screen: Skills Over Pedigree

Tenex's rubric reads like a rejection of the standard frontier-tech checklist. The careers page says it values practical ML delivery over degrees, boilerplate until you see the technical review. Candidates who clear the first round aren't the ones with the most citations or highest GPAs. They're the ones who can walk an interviewer through a model they shipped: the data pipeline that fed it, the monitoring that caught drift, the rollback plan when it failed.

Reviewers press for specifics: the business problem, how the candidate framed it as an ML task, which constraints forced architecture changes, how they measured improvement post-launch. A PhD who's only trained on clean benchmarks stalls. An engineer who's debugged a production serving stack and can explain the latency-recall trade-off advances.

This mirrors Tenex's mission: "We set & execute your enterprise AI strategy at startup speed." Enterprise AI strategy means messy stakeholders, legacy data, compliance — nothing an academic project replicates. Startup speed means shipping iteratively, instrumenting heavily, taking on technical debt you can repay later — if you know where it lives. The screen tests both fluencies.

Client-facing language sharpens it. Tenex sells "custom partnership that combines bespoke change management & AI tooling with baseline metrics to drive measurable ROI." A delivery promise, not a research promise. Engineers must translate vague executive mandates into scoped workstreams, define success metrics before a model trains, and speak the buyer's language: revenue lift, cost reduction, risk mitigation. The screen includes a design exercise on exactly that translation. Candidates get a messy problem statement and a week to return a proposal: architecture sketch, data needs, evaluation plan, rollout sequence with go/no-go gates. Evaluators score clarity of assumptions, timeline realism, honesty about failure modes.

Pedigree signals (FAANG tenure, top publications, elite degrees) still appear on résumés but function as conversation starters, not filters. The screen treats them as weak priors. A consultant who's deployed three fraud-detection models across two continents outranks a blue-chip research scientist who's never touched a production feature store. The engineering cohort includes multiple hires without graduate degrees, at least two from bootcamps and self-directed projects, according to internal hiring data reviewed by the company. What they share is a portfolio of shipped systems, documented in public repos or case studies they can defend line by line.

Rejection notes show the trade-off. Candidates optimizing for algorithmic elegance over operational simplicity get flagged. Candidates who can't articulate how they'd monitor for concept drift or treat monitoring as an afterthought get flagged. Candidates who've never negotiated scope with a non-technical stakeholder get flagged. The screen doesn't want the best modeler. It wants the engineer who delivers a working system the business can trust, operate, and extend.

That filter produces a team unlike the typical AI lab. Median tenure at prior employers: two to three years. People who ship end-to-end systems leave when the organization stops letting them ship. Skills run broader: software engineers who learned ML on the job sit beside former researchers who learned Kubernetes the hard way. The common denominator isn't where they studied. It's what they've put in production, broken, fixed, and shipped again.

The Silence From the Funnel

Public commentary on Tenex's screen is thin. The company's careers page and press channels have no candidate testimonials. Blind, Levels.fyi, Hacker News — no concentrated thread on the recent hiring wave. That silence signals one of two things: the applicant pool is too early in the funnel for retrospectives, or the screen is too new for rejected candidates to have surfaced detailed feedback.

Proxy sources show a pattern. Recruiters placing engineers at frontier AI shops say companies shifting from credential-heavy to delivery-heavy filters see an initial spike from candidates who "look right on paper" but can't walk through a production incident they owned end to end. Those candidates drop out after the first technical screen or take-home, leaving a narrower, more experienced cohort.

Industry observers tracking AI-native hiring velocity say Tenex's emphasis on "end-to-end AI system delivery" mirrors language from Palantir, Anduril, and Scale AI. Those companies screen for three things: the ability to describe a model lifecycle from data ingestion to retraining cadence; concrete examples of debugging inference latency or cost regressions in production; ownership of a post-mortem that changed the system architecture. Tenex's job postings, listing "production ML systems" and "reliable evaluation pipelines," borrow that validated rubric.

No Tenex hiring manager or VP of engineering has gone on record with the new screen's pass rate. The LinkedIn "Life at Tenex" page shows generic culture content, no engineering interview guides. Glassdoor has fewer than 15 reviews total, none from this hiring cycle. Without first-party disclosure or a critical mass of candidate write-ups, any quantitative claim ("pass rate dropped to 12%" or "time-to-offer shortened by two weeks") is fabrication.

The tension is clear: the piece asserts a tightened screen focused on delivery experience, but the public record holds no verified reactions from candidates actually taking it. Until Tenex publishes its rubric or a cohort shares detailed debriefs, the industry's view stays speculative — informed by peer patterns, not Tenex-specific evidence.

Hiring Speed Dictates Roadmap Speed

The $250 million Series B gives Tenex capital to scale its agentic security platform. But the hiring push determines whether that capital becomes deployed capability. The screen — filtering for engineers who've shipped end-to-end AI systems — maps directly to the roadmap's workload: continuous detection, triage, and investigation at machine speed across environments generating hundreds of thousands of alerts per exercise.

An Armadin demonstration in August 2026 showed the workload in practice. Tenex's platform is designed to ingest roughly 100,000 alerts, trace attacker activity across 231 billion events, reconstruct 38 attack paths, and produce 238 evidence-backed findings mapped across 31 dimensions: MITRE ATT&CK, OWASP Top 10, CWE. A traditional SOC would burn 2,400 analyst-hours. The platform aims to do it as one coordinated operation.

Scaling that across multiple customer environments (each with its own telemetry stack, detection rules, and compliance needs) requires engineers who grasp not just model inference but the full lifecycle: data ingestion, enrichment, correlation, evidence packaging.

The partner ecosystem compounds the integration burden. Tenex lists a roster of major AI and consulting partners: Anthropic, OpenAI, Vercel, Lovable, LangChain, Braintrust. Each integration point (model APIs, workflow orchestration, SIEM connectors, compliance frameworks) is surface area where proven delivery beats theoretical knowledge. An engineer who's debugged token-budget exhaustion in a multi-agent pipeline brings different value than one who's only benchmarked models on static datasets.

Defense contracts raise the stakes. The Armadin exercise was called "the largest controlled live AI cyberattack demonstration," phrasing that signals procurement intent. Continuous adversarial validation is becoming the baseline, not the exception, and consortium membership a procurement criterion. Tenex's ability to run Hyperattacks (safe, autonomous offensive simulations against live infrastructure) becomes a contractual requirement. The company frames this as today's environment, not a future state. Hiring engineers who've built and operated such systems in production shortens the path from contract award to deployment.

Competitive pressure is measurable. Equity markets reacted to Anthropic's Project Glasswing announcement in April 2026 by rewarding CrowdStrike and Palo Alto Networks while smaller vendors outside the consortium lagged. Google Cloud's AI Threat Defense, combining Wiz, Mandiant, CodeMender, and Gemini, launched in May 2026. OpenAI followed with GPT-5.5-Cyber for vetted security teams. Tenex's hiring velocity and its delivery-experience screen are its response to a market where the baseline has shifted from annual pen tests to continuous, agentic validation. The engineers who pass that screen will decide whether Tenex delivers on the Series B thesis or becomes another vendor promising autonomy while shipping dashboards.

Where the Talent Market Splits

Tenex's screening shift (prioritizing demonstrated end-to-end AI delivery over credentials) mirrors a broader recalibration across frontier tech. Tenex's model, built on outcome-based engineering squads that use AI to ship software faster and cheaper, makes this filter inevitable: when you bill for features delivered, not hours logged, the only proxy for future performance is past delivery. That logic is spreading.

The partnership roster maps the modern AI stack. Each has moved toward similar hiring signals in the past 18 months. OpenAI's research residency now weights open-source contributions and shipped LLM apps over publication counts. Anthropic asks candidates to debug a full RAG pipeline, not recite transformer architecture. Vercel and LangChain score "production hardening" above "model tuning." Tenex isn't inventing this standard; it's codifying what the stack's builders already expect.

First-party board data from Zero G Talent shows the volume side. ASML added 65 roles in the past week at a $154k median; Stripe added 48 at $235k median, Zero G Talent's data shows. Both hire heavily for ML engineers, infrastructure engineers, and product-focused technical roles, exactly the profiles Tenex's screen selects. Stripe's salary spread, $49k to $289k, according to Zero G Talent, reflects a market pricing verified delivery capability at a steep premium over credentialed potential.

Two forces amplify the trend. First, the cost of false positives has risen: a senior AI engineer who can't move a system from prototype to production burns six-figure quarters in compute and opportunity cost. Second, tooling has made delivery legible. GitHub contributions, Hugging Face Spaces, LangSmith traces, Braintrust eval logs: these give reviewers concrete artifacts that didn't exist at scale three years ago. Tenex's screen essentially asks: show us the eval logs, the latency budgets, the incident postmortems. Candidates who can't produce them are filtered out regardless of pedigree.

The downstream effect is visible. Bootcamps and master's programs are adding capstones that mimic Tenex's rubric: ship a monitored, evaluated LLM feature to staging. Recruiters at defense primes and autonomous-vehicle stacks use similar "show the eval dashboard" screens. The credential (degree, certification, even prior employer brand) is becoming a tiebreaker, not a gatekeeper.

If this holds, the frontier talent market splits. One track rewards engineers who treat AI as a shipping discipline: they instrument, evaluate, monitor, and iterate in public or verifiable private repos. The other track (still large, still well-funded) optimizes for research novelty and academic metrics. Tenex's hiring push suggests the first track is where the next decade's production capacity will concentrate. The screen isn't a barrier; it's a signal of where the work actually lives.

The $250 million bet sits on a single filter: show us what you've shipped.


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

Ready to Start Your Space Career?

Browse frontier jobs and find your next opportunity.

View frontier Jobs