Zenity sells into a category that barely existed two years ago: securing and governing the AI agents a company deploys. Not the models themselves, but the agents built on top of them, the low-code and no-code automations in Microsoft Power Platform and Copilot Studio, and increasingly agents running on any framework, including ChatGPT Enterprise, Gemini, and coding agents like Claude, Codex, and Cursor. Gartner named Zenity a frontrunner in AI agent governance in an April 2026 report and a market shaper in AI application security, which is the kind of analyst signal that pulls enterprise budget into a net-new line item.
The money followed. In early August 2026 Zenity announced a $125M Series C led by Norwest (with SoftBank Vision Fund 2, Hitachi Ventures, Qumra Capital, and others joining; the full investor list is in the table below). Coverage put the total raised around $180M (some outlets say closer to $185M). For an engineer, the read is simple: a well-capitalized company hiring hard into a category being created and contested at once, which shapes both what they screen for and how unsettled the process can feel.
What Zenity actually builds, and why it changes the bar
The platform does discovery, posture management, and runtime protection for agents an enterprise may not even know it has. Think of a business user who wires up a Copilot Studio agent that can read SharePoint and send email: Zenity finds it, scores its risk, flags an over-permissioned connector or prompt-injection path, and blocks or alerts at runtime. That means the product is simultaneously a cloud security tool, an identity-and-permissions graph, and an AI-specific detection engine, which is why the open roles span backend and platform, frontend, security research, detection engineering, and go-to-market field engineering.
The research side is not window dressing. Zenity Labs, the company’s research arm, has a public track record at Black Hat USA and RSAC, and that reputation sets the intellectual bar in interviews. The single most useful prep for a research or detection candidate is to read that work before the loop. Start with the AgentFlayer series on zero-click agent compromise (the ChatGPT Connectors 0-click attack writeup is the clearest entry point), the Black Hat USA 2024 Living off Microsoft Copilot materials, and Zenity’s GenAI Attacks Matrix, whose techniques were folded into MITRE ATLAS. Those three show the house style: find a novel way to turn an agent’s own tools and permissions against its owner, then generalize it into a detection. Reports put the broader research group near 40 people with a smaller internal red team (loosely reported from job listings, not a confirmed org chart). If you come from a traditional appsec or detection background, the security engineer interview guides cover the fundamentals; be ready to layer prompt injection, tool misuse, and agent identity on top.
The Zenity interview loop, from a thin but real record
The clearest published description is Zenity’s own New York Senior Software Engineer posting, which lays out six stages and calls the process “transparent, conversational, and focused on real-world experience.” It starts with a 30-minute recruiter screen, then a problem-solving assessment, then a 60-minute hiring-manager interview that covers both system design and the problem-solving question. After that come a 30-45 minute Director of Engineering interview on technical depth, a 30-minute VP of R&D conversation about expectations and execution, and a 30-minute People Team interview on collaboration and work style. That’s a lot of leadership face time for an IC hire, which fits a company still small enough that the VP of R&D wants eyes on everyone joining.
The “problem-solving assessment” is the one stage worth pinning down early, because the posting doesn’t describe its format. Two clues bound it: the hiring-manager round explicitly revisits “the problem,” and the Tel Aviv student account mentions a coding assignment (memory-slot allocation). Read together, that points to a coding exercise you either complete beforehand or carry into the 60-minute hiring-manager round, format unconfirmed, take-home versus live. Whether you’re allowed AI coding agents on it is also unstated, which matters here specifically because advanced proficiency with those tools is a listed requirement, so ask the recruiter rather than guessing the rules.
Candidate reports are thinner and more mixed, so weight them lightly. One Glassdoor account from March 2026 describes four to five rounds stretched over roughly two months that ended with no response, and the candidate called the experience chaotic. A Tel Aviv student software-role account describes a tighter two-week process with a coding assignment about memory-slot allocation. Two anonymous data points don’t define a process, but they match a fast-growing startup: a real, multi-round loop that can run long and communicate unevenly. Expect the posted structure to be the intent and the lived timeline to vary.
For the security-research and detection-engineering roles, there is no published loop, so treat the following as inferred from the job requirements, not reported. A senior security researcher posting asks for 4+ years in security research spanning cloud, web, or API security, which points to at least one deep technical conversation about prior research, how you’d find a novel agent vulnerability class, and how you’d turn it into a detection. A detection-engineering hire (no detection-specific posting surfaced, so this is pure product-inference) should expect to talk through writing and tuning detections against real telemetry, false-positive economics, and how you’d catch an agent being manipulated versus an agent doing exactly what a careless admin configured. Confirm the actual rounds with your recruiter rather than prepping blind to this inference.
What each role screens for
The backend and platform track is a conventional strong-IC bar with an AI-tooling twist. The Senior Software Engineer posting asks for 5-7 years, fluency in a modern language from the set Python, C#, Java, Go, TypeScript, or JavaScript, experience running large-scale services on AWS, Azure, or GCP, and, notably, advanced proficiency with AI coding agents as an explicit requirement rather than a nice-to-have. If Go is in your stack and you’re rusty, the Go interview fundamentals are worth a pass, and the hiring-manager system-design round is best prepped against the kind of multi-tenant, high-ingest problems in the system design interview guides, since the product graphs activity across a customer’s entire agent estate.
Security research and detection engineering screen for depth and originality over breadth: whether you can find something nobody has named yet in a system with tool access and natural-language control. Field engineering and the GTM AI Engineer role (reported from an open GTM AI Engineer posting) screen for a different blend: enough technical credibility to stand in front of a security buyer, demo an agent exploit, and translate it into risk, plus the forward-deployed instinct to make a customer successful. Frontend candidates have less to go on: the product’s console and policy dashboards mean frontend work clearly exists, but no frontend-specific posting or loop is in the public record (inferred), so expect the same six-stage shape and confirm the technical rounds with your recruiter. Across all of them, the cross-functional and startup-fit signal in those later leadership rounds is real, so bring concrete ownership stories. A structured behavioral answer carries the VP of R&D and People Team conversations better than improvising.
| Zenity interview and company facts (as of November 2026) | Detail | How well-sourced |
|---|---|---|
| What it does | Israel-founded (Tel Aviv HQ plus US offices in New York and Jersey City) security and governance platform for enterprise AI agents: discovery, posture management, and runtime protection across Microsoft Power Platform and Copilot Studio and agents on any framework (ChatGPT Enterprise, Gemini, coding agents like Claude, Codex, Cursor). Named an AI-agent-governance frontrunner and AI-application-security market shaper by Gartner in 2026 | Reported (company site, security press, Gartner coverage) |
| Funding | $125M Series C led by Norwest, announced early August 2026; investors include Qumra Capital, Hitachi Ventures, SoftBank Vision Fund 2, LG Technology Ventures, plus existing Vertex Ventures, DTCP, Third Point Ventures, Intel Capital. Total raised ~$180M (some sources ~$185M); valuation not disclosed | Series C and lead reported consistently; cumulative total varies by outlet |
| Research arm | Zenity Labs publishes agent-exploitation research (e.g. the AgentFlayer zero-click chains, “Living off Microsoft Copilot” at Black Hat USA 2024, and the GenAI Attacks Matrix now folded into MITRE ATLAS) at venues including Black Hat USA and RSAC; broader research group reported near 40 people with a smaller internal red team | Named research verified on labs.zenity.io; head-count figures loosely reported from job listings |
| Interview loop (backend/platform) | Six stages per Zenity’s NY Senior SWE posting: recruiter screen (30m), problem-solving assessment, hiring-manager interview (60m, system design + problem), Director of Engineering (30-45m), VP of R&D (30m), People Team (30m). Candidate reports: one 4-5 round, ~2-month account ending in no response; one Tel Aviv student role, ~2 weeks, memory-slot-allocation coding task | Official stages reported from Zenity’s careers site; candidate timelines thinly reported from anonymous reviews; security-research/detection loops inferred from job requirements |
| What they screen for | Backend/platform: 5-7 yrs, Python/C#/Java/Go/TypeScript/JavaScript, large-scale cloud services (AWS/Azure/GCP), required advanced proficiency with AI coding agents. Security research: 4+ yrs research across cloud/web/API security. Field/GTM: technical credibility plus forward-deployed customer instinct | Reported from Zenity job postings; emphasis on adversarial thinking inferred from the product and research culture |
| Compensation (base, New York) | Posted Senior Software Engineer NY ranges ~$180k-$250k (one listing $180k-$235k, 5-7 yrs) under NYC pay-transparency law; excludes bonus and equity. Aggregator estimates (~$140k-$180k) are modeled, not posted. Levels.fyi showed only Israel data | Reported from NYC job postings (pay-transparency ranges); aggregator numbers are estimates, not verified offers |
For calibration against the rest of this space, Vanta is the nearest neighbor on the site, a security-and-governance company where compliance automation sets the tone, and the broader AI-native company interview guides plus the AI-startup interview difficulty index give more calibrated signal than Zenity’s own sparse review record.
How to prep when half the loop is unpublished
Prep to the product and the category. Whatever role you target, be able to explain in plain terms why an AI agent is a new kind of security object: an identity with permissions, acting on natural-language instructions an attacker can poison, chaining tools in ways its creator never intended. Prompt injection, over-permissioned connectors, and agent-to-agent trust are the vocabulary of the interview. A candidate who treats this as ordinary SaaS security will read as behind the problem.
On the backend track, be sharp on service design for high-ingest, multi-tenant systems and on the AI-coding-agent workflow the posting explicitly asks about, since they want engineers who build with these tools daily. On the research and detection tracks, the Zenity Labs reading above is the prep: bring a piece of prior work, your own or a critique of theirs, that you can defend end to end. For field and GTM roles, rehearse translating a technical exploit into business risk for a CISO. Because the leadership rounds carry weight, the general AI-era interviewing advice applies doubly here: show judgment about where this technology breaks, rather than enthusiasm alone.
On pay, anchor to the posted numbers and then get the real band. The New York Senior Software Engineer ranges of roughly $180k-$250k base come from Zenity’s own listings under NYC pay-transparency law, which makes them more reliable than the modeled aggregator figures, but they exclude bonus and equity and don’t cover other levels, locations, or the Tel Aviv roles. For non-US readers: the public US postings don’t state whether Zenity sponsors work visas, so ask; and because the company is Israel-founded with a Tel Aviv HQ that is actively hiring (reported), Tel Aviv-based roles with their own local bands are a real option, though relocation and sponsorship terms aren’t published (inferred). A freshly funded Series C company usually pairs competitive cash with equity that still carries real risk, so run the whole offer through the total comp calculator rather than comparing base alone, and ask the recruiter directly for the band on your exact level and location. When you have real figures, the usual salary negotiation moves apply. Given how new this category is and how thin the public interview record remains, treat this guide as a map of the terrain and confirm every specific with the person scheduling your loop.
Useful next steps:
