Working at Adaptive Security: Culture, Pace and Who Thrives

How Work Gets Done

Adaptive Security moved from public launch to more than a thousand enterprise customers in eighteen months. That velocity did not happen by committee.

Brian Long and Andrew Jones co-founded the company. Long acts as the public face: founder interviews, product announcements, the YouTube deep-dive where he describes the threat environment in real time: "When I started talking to customers about this a little over a year ago, about 5% of executives had experienced an attack at their company. Now it's probably 30 or 40%." Jones stays lower-profile, but the capital table makes the power structure legible. The Series A was led by the OpenAI Startup Fund and Andreessen Horowitz — OpenAI's first and only cybersecurity investment. The Series B, announced December 2025, brought Bain Capital Ventures in as lead with NVentures, the OpenAI Startup Fund, a16z, Abstract Ventures, Capital One Ventures, and Citi Ventures following. Over $140 million raised in under two years, Adaptive Security reported. When a cap table looks like that, the founders retain operational control but investors expect a return tempo that matches their own fund cycles.

The product roadmap reflects that pressure. Adaptive launched its AI Content Creator in May 2025, a multimodal generative platform that turns a threat write-up into deployable training in seconds. By June 2026 the company had produced a 15-video training series starring Conan O'Brien, filmed in Los Angeles, each module opening on a comedic framing before handing off to Adaptive's instructional engine. Customers see both versions side by side in the content library and choose which to assign. That kind of cross-functional ship, encompassing content, product, partnership, localization across 35-plus languages, and enterprise distribution, does not run on consensus. It runs on a single-threaded owner model where product, engineering, and go-to-market align behind a dated deliverable.

The hiring pattern confirms the orientation. Zero G Talent's board shows six active salaried roles with a median band of $150k:

The spread, with engineering at the top, BDR at the floor, two AE tracks, and CS split between senior and associate, signals a sales-led engine backed by a premium product team. Authority sits with whoever owns the revenue number and the ship date. Everyone else executes toward their targets.

The pace is visible in customer metrics. Adaptive estimates up to 60% of employees fail AI-powered attack simulations without prior training. The company's own simulations identify control gaps and auto-generate individualized remediation. Customers report deploying targeted training within hours of major incidents hitting headlines, compared to weeks or months for custom content. That feedback loop (threat → simulation → training → measurement) is the operating heartbeat. Miss a ship date and the loop breaks. Miss a quarter and the board asks why.

No public org chart, no leaked memo, no Glassdoor deep-dive spells out the meeting cadence or approval chain. The record shows a company that treats speed as a survival metric. Deepfake incidents grew 17× from 2023 to 2024; Deloitte projects that AI-facilitated fraud losses in the U.S. will grow from $12.3 billion in 2023 to $40 billion by 2027. Long puts it plainly: "The threat is evolving in real time. Our responsibility is to move at least as fast." That sentence functions as the de facto operating principle. Decisions get made at the level where the clock is watched most closely. For a candidate, the question is not whether the culture is intense — it is. The question is whether your own operating speed matches the one the market just imposed.

Values Written in Headcount

The job board tells the story before any founder interview does. Four of six salaried roles are revenue-facing: two Senior Account Executive slots (one remote, one tri-city), a Business Development Representative role across NYC, LA, and SF, and a Senior Customer Success Manager in New York. The lone technical slot is a Software Engineer, Product & Platform role in New York. A Customer Success Associate sits at the other end. That distribution, heavy on quota-carriers and light on pure R&D, is a value statement rendered in headcount budget.

The width of the engineering band itself signals how the company thinks about talent. A $175k spread on a single title suggests they're not hiring to a leveling rubric; they're hiring for output. Someone who can ship the core platform fast commands the top of that range. Someone who needs more scaffolding starts lower. The band rewards demonstrated velocity over credential, which aligns with an execution-first culture that promotes from proof, not pedigree.

Sales roles carry narrower base bands, but the real compensation lives in variable, a structure that selects for people who bet on themselves. The two Senior AE postings, one remote and one geo-locked, indicate they'll pay for proven closers wherever they sit, but they still want bodies in the rooms where deals get signed.

Customer Success splits into two tiers: a Senior Manager at the higher band (base-heavy, likely managing strategic accounts) and an Associate at the lower band (higher-volume, lower-touch). The gap between them is deliberate: no mid-level CSM role posted means the company either promotes from the Associate rank or hires experienced managers externally. Either way, the message is the same: own the renewal, expand the account, or move on.

What's absent from the board is telling. No dedicated security research roles. No devops or platform engineering titles separate from the product engineer. No marketing, no product management, no design. The organization appears to run lean on functions that don't directly attach to revenue or the core platform. That's not an oversight — it's an operating principle: every headcount must justify itself against the sales funnel or the shipping cadence.

The remote Senior AE listing alongside the hub-locked one reveals a tension the company is still resolving. They'll hire a proven closer remotely, but the BDR and Associate roles, the pipeline generators and the front-line retention layer, require physical presence in NYC, LA, or SF. The logic is practical: early-career reps need osmosis, not autonomy. But it also creates a two-tier culture where seniority buys flexibility and junior roles buy apprenticeship through proximity.

If there's a stated values page or a founder manifesto, it hasn't surfaced in public reporting tied to this analysis. What exists instead is a hiring ledger that reads like a set of operating principles written in compensation bands: revenue first, velocity over process, seniority earns autonomy, and the rest is noise. Candidates who need a mission statement on the wall will find the culture opaque. Candidates who read the org chart and see the strategy will know exactly what they're signing up for.

The Hiring Filter

Brian Long has framed the problem Adaptive solves in terms that double as a filter. "Seventeen percent of hiring managers have spotted deepfakes while interviewing candidates, and it's expected in the next year that one in four applicants are going to be fake," he told The Hacker News in January 2026. He added that the Justice Department found more than 300 U.S. companies had unknowingly hired North Korean operatives using deepfakes for remote IT roles. Over 100,000 deepfake attacks hit the U.S. last year alone, a 17x increase. The technology, Long said on a September 2025 YouTube deep-dive, is "about 85% of the way there today… in the next year you're going to see it hit the mid 90s." The attack surface has already moved beyond email to real-time voice calls, SMS, and Zoom, where traditional protections don't exist.

Candidates who land at Adaptive tend to show three things. First, fluency with the threat model. The sales roles aren't pure relationship plays; they require explaining why a simulation-and-training platform matters to a CISO who just watched a deepfake bypass their MFA. The Senior Account Executive bands and the BDR role sit at price points that assume enterprise sales cycles, not transactional volume. The Customer Success roles imply post-sale ownership of simulation programs; candidates who have run security awareness or phishing simulations at scale show up stronger than generalist CSMs.

Second, comfort with a market that compounds weekly. Long's "exponential growth" line isn't marketing — the 17x jump in attacks is a documented figure. The hiring bar selects for people who can sell or build against a moving target without waiting for a product roadmap to settle. The Software Engineer role's band is wide enough to capture both a senior individual contributor and a founding-engineer type who can ship detection features as the deepfake quality curve bends toward the mid-90s.

Third, a track record of operating without hand-holding. The remote Senior Account Executive slot and the three-hub territory for the other AE and the BDR suggest the company expects reps to generate pipeline independently. The board data shows no SDR layer beneath the BDR — the BDR is the top of funnel. That structure rewards self-starters who can cold-call into security teams, qualify on technical pain, and hand off a demo-ready opportunity.

What gets screened out? Generalist SaaS reps who've never sold to security buyers. Engineers who want a stable API surface. Candidates who need a mature process before they execute. The company's own product — simulate the attack, train the failure — mirrors how they hire: they test for resilience under pressure, then coach the gaps. If you've never had to explain why a voice-clone attack bypassed a help desk, the learning curve is steep. The bar isn't credentials; it's whether you've already been moving at the speed the threat environment demands.

Inside the Black Box

Public employee feedback on Adaptive Security is thin. The GadgetReview piece from June 10, 2026, notes the partnership "signals that companies are finally acknowledging what employees have known for years: traditional security training doesn't work," but the "employees" there are the end users of Adaptive's product, not Adaptive's own staff. The Microsoft governance news from June 8, 2026, is unrelated.

What the research does support is a structural inference: a small, well-capitalized team selling into a market that grew 17x in a year, with a founder who frames the problem in urgent, personal terms, and a headcount plan weighted toward quota-carrying roles. That structure selects for people who treat ambiguity as a feature, not a bug. It penalizes people who need process maturity, work-life boundaries enforced by policy, or a culture of consensus. The absence of public complaints may mean the filter is working, as people who would burn out don't join, or they leave before they review. The absence of public praise may mean the ones who stay are too busy shipping to write reviews. Either way, the signal is the same: the culture is the work.

Who Stays, Who Leaves

People who thrive here share a specific profile: they treat quota as a scoreboard, not a threat. The BDR role is an entry point with that same profile if you convert pipeline. The two AE postings suggest the company is still building its sales motion, not optimizing a mature one. That means territory definition shifts, comp plans evolve mid-quarter, and the playbook gets rewritten while you're running it. Candidates who need a stable map before they move will stall. Candidates who build the map as they go will outpace the plan.

Engineering tells a parallel story. The range accommodates a senior IC who ships fast and a staff-level hire who owns architecture. But the single posting, "Software Engineer, Product & Platform," signals a lean team where everyone touches infrastructure and product code. Engineers who thrive treat operational burden as ownership signal. Engineers who burn out treat it as distraction from "real work."

Customer success sits in the pressure zone between the two. The Senior CSM likely carries expansion revenue targets, not just retention. The Associate is the front line for onboarding volume. Both roles absorb the friction when sales sells ahead of product and engineering ships behind schedule. CS professionals who thrive here speak fluent technical and commercial; they can debug a webhook failure on a call with a CISO and translate it into a renewal narrative. CS professionals who burn out wait for product to fix the bug before they follow up.

The remote AE posting is a tell. A fully remote quota-carrying role at a Series A security startup suggests the company has a repeatable motion that travels. The tri-city AE posting suggests hub-based deal teams where in-person deal reviews happen weekly. If you're the remote rep, you're on Zoom while the room reads body language. That gap separates people who over-communicate proactively from people who assume visibility happens automatically.

Mismatches cluster around three areas. First: pace tolerance. The sales-driven tempo means Monday pipeline review, Tuesday deal slippage, Wednesday executive escalation, Thursday product gap, Friday scramble. People who need predictable sprints leave. Second: ambiguity tolerance. The wide salary bands, the single engineering role, the evolving sales motion — all signal a company still discovering its model. People who need role clarity before they execute leave. Third: feedback tolerance. A culture that prioritizes resilience and execution gives direct, frequent, sometimes blunt feedback. People who interpret critique as attack leave.

Adaptive Security doesn't hide this. The role mix, the compensation spread — it's all visible on the board. The candidates who self-select out before applying save everyone time. The ones who self-select in understand the commitment: a company that moves at the speed of the threat, and expects you to keep up.

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