×
Cymphony
Workforce security for the AI era — one graph covering employees and agents
Last verified September 14, 2026 · Updated daily
What Cymphony is building
Cymphony builds a workforce security graph. The premise is that enterprise security was designed around a human employee — a person with a badge, a manager, a joiner-mover-leaver lifecycle — and that model quietly broke the moment employees started connecting AI agents to internal systems. An agent is an identity that reads at machine speed, inherits whatever permissions its human creator had, and leaves no trail a conventional IAM tool was built to read. Cymphony's answer is to stop treating AI as one more application to secure and instead model the whole workforce, human and non-human, in a single graph. The graph unifies four signal types: identities, the systems they touch, the permissions they hold, and the data interactions they actually perform. On top of it sit four functional surfaces — AI tool discovery, data exposure detection, identity hygiene, and insider threat monitoring — plus a conversational investigation assistant called Maestro, which lets an analyst ask questions without learning a query language. The design bet is that the query syntax is the thing that stops security teams from investigating, not the data. The findings are what sell it. Cymphony surfaced roughly 85,000 files reachable by AI tools inside one large US public company and drove the remediation. At another customer it found an unsanctioned Claude instance scanning thousands of sensitive documents. Shy Dekel's favourite example is smaller and sharper: a customer who connected ChatGPT to SharePoint and, without noticing, exposed an incredibly sensitive litigation process to interns. None of these are model failures. They are permission-inheritance failures that nobody had a lens to see. Dekel's framing of the category is the clearest statement of the thesis: 'The security industry keeps treating AI as another application to secure, but that's the wrong model.' You cannot secure what you cannot see, so the product starts as visibility and earns the right to enforce.
Why this matters
The traction is unusually specific for a company that just left stealth. Double-digit enterprise customers and seven-figure ARR inside the first year of selling, with KKR, Syngenta, Cass Information Systems and Athennian named publicly. Sequoia runs Cymphony internally to manage its own exposure, which is a stronger signal than the cheque. The market timing argument is that the incumbents are arriving but have not landed. Microsoft, Okta, CyberArk, Wiz and Varonis are all extending toward agent identity, and Balkansky's own read is that Cymphony is currently complementary to those tools rather than displacing them. That is an honest description of a window, not a moat — which is exactly why the next twelve months of engineering matter more than the next twelve months of selling. The wider context is a funding wave: Cymphony was the third significant agent-security raise in three weeks, part of roughly $435M into the space over five months. The counterweight is that 88% of enterprises with agent initiatives never ship them to production. Read those two numbers together and the opportunity is not 'agents are everywhere' — it is that the shadow-agent problem is already real inside companies that have not officially deployed a single agent.
Open roles at Cymphony
4 positions we're tracking. Roles are re-checked daily and removed when filled.
Backend / Graph Engineer (Tel Aviv — the identity-permission-activity graph is the core asset)
First seen today
Detection & Response Engineer (turning graph findings into ranked, actionable risk)
First seen today
Enterprise Account Executive (New York — selling into CISOs at KKR-scale accounts)
First seen today
Solutions Architect / Sales Engineer (deployment into SharePoint, Google Workspace, IdP and agent estates)
First seen today
Know when Cymphony is hiring before anyone else
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Cymphony
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+Hiring outlook
The launch release states the round will accelerate product development and expand the engineering and go-to-market teams. At ~30 people with double-digit enterprise customers and a two-site footprint, that expansion is immediate rather than aspirational. Scored 7 rather than 8 because Cymphony does not publish a role list on its own site — openings are maintained on its LinkedIn company page.
Working at Cymphony
Cymphony is a AI company based in New York, USA. For a AI company this size, the reality is broad remit, direct access to founders, and equity that still means something if the company works out.
Most Cymphony jobs are based in New York, USA.
How to actually get hired at Cymphony
Why applying the normal way doesn't work
With only <50 employees, Cymphony doesn't have dedicated recruiters. Founders review applications between running the company. The challenge isn't competition — it's visibility. Direct outreach wins.
Who to contact at Cymphony
Founding team
Talpiot graduate with a hardware engineering background spanning Apple and the Israeli Ministry of Defense. Brings the systems-level depth behind Cymphony's graph infrastructure, which has to ingest identity, permission and activity signals across an entire enterprise estate in near real time.
Graduate of Talpiot, the Israeli military's elite technology programme. Spent nearly six years in Unit 8200, rising to Head of the Cyber Department. Holds an INSEAD education and is based in Tel Aviv. Co-founded Cymphony roughly two years ago and raised a Sequoia-led seed before the company had a product or a settled product direction.
Talpiot graduate who ran a research group in the Office of the Prime Minister of Israel and won an Israel Defense Prize for that work. Owns product at Cymphony, including Maestro, the conversational investigation layer built so analysts can interrogate the workforce graph without writing queries.
What to show them
Build a small permission-reachability graph over a real SaaS estate you control — a Google Workspace or Microsoft 365 tenant plus one connector. Model users, groups, files, scopes and OAuth-granted apps as nodes, then answer one question end to end: given an agent acting as user X, which documents are reachable and by what path? Ship the traversal, show query latency as the estate grows, and write up the one path that surprised you. That last part is the hire signal — Cymphony's whole product is the surprising path.
A cold email that works at Cymphony
What Cymphony screens for
Sequoia led the seed when there was no product and no clear product direction, then co-led the A and deployed the thing internally. That is a conviction pattern, not a portfolio bet, and it means the company will be given room to build a platform rather than pushed to chase revenue. The hiring window is the specific thing to notice: ~30 people, a fresh $25M, and five well-capitalised incumbents walking toward the same category. The next hires are the ones who decide whether the workforce graph becomes the enforcement layer or stays a very good dashboard. If you have worked on identity, permissions or data-access modelling at scale, this is the rare moment where that unglamorous expertise is the whole product.
Tailor your CV to the specific Cymphony role rather than sending a general one. Applications that mirror the language of the job description clear automated filters at a materially higher rate.
Don't make these mistakes
Do not open with how transformative AI agents are. All three founders are Talpiot graduates; Shy ran the cyber department in Unit 8200 and Edi built hardware at Apple and the Israeli Ministry of Defense. They have heard the category pitch from every fund and every candidate for two years, and Shy's public position is explicitly that treating AI as 'another application to secure' is the wrong model — so a note framed around securing AI apps reads as someone who did not read his launch quote. Equally, skip the Unit 8200 flattery; in Israeli security it is table stakes, not a compliment. Lead instead with a permission-inheritance failure you have personally seen: an OAuth scope that quietly granted an integration more than anyone intended, a shared drive that turned out to be org-wide, a connector that made an intern's account a retrieval path into legal. Concrete blast radius, then how you would model it.
Mistakes that kill Cymphony applications
A recycled CV gets rejected fast at Cymphony (<50 people). They notice.
Lead with their problem, not your ambition. Cymphony is focused on The traction is unusually specific for a company that just left stealth — show you understand that.
Don't apply and wait. The median AI application gets no response ever. One follow-up at day five roughly doubles reply rates.
Applying to Cymphony? Get the contact, not the form.
The Cymphony interview process
3 stages · 7 days typical · take-home: yes · modelled from similar companies
We don't yet have verified candidate reports for Cymphony. What follows is the typical process for a <50-person AI company — treat it as a model, not confirmed detail.
Interview stages
Intro Call
Video call · 30 min
Culture fit and role expectations
Founder or hiring manager
Technical Deep Dive
Video call or in-person · 60 min
Past projects and problem-solving approach
Technical founder or lead
Final Round
In-person or video · 45 min
Team fit and offer discussion
Founding team
Cymphony take-home assignment
Cymphony includes a take-home exercise in their interview process. For AI roles, this typically involves a practical problem that takes 2-4 hours. Focus on clean, working code over premature optimization. They're evaluating how you think and communicate, not just the solution.
Cymphony interview timeline
Cymphony runs about days from first contact to offer. The median for AI companies at <50 people is 10 days, so Cymphony is faster than most.
Interviewed at Cymphony?
Tell us how it went — stages, questions, timeline. Takes 90 seconds and it's how this page stays accurate for the next person.
Submit your Cymphony interview experience →Cymphony jobs, frequently asked questions
How many jobs does Cymphony have open?
We're tracking 4 active openings at Cymphony (verified September 2026).
Does Cymphony hire remotely?
All current Cymphony roles are based in New York, USA.
What roles is Cymphony hiring for?
Cymphony is hiring across Engineering, Sales. The most recent opening is Backend / Graph Engineer (Tel Aviv — the identity-permission-activity graph is the core asset).
How do I apply for a job at Cymphony?
Click through to apply, or see our detailed guide on landing a job at Cymphony.
Does Cymphony respond to cold emails?
We haven't verified response rates at Cymphony yet.
Who is the hiring manager at Cymphony?
At this size, hiring is usually run by a founder or department head.
How competitive is it to get hired at Cymphony?
<50-person AI companies see ~50-100 applicants per role in two weeks. The 72-hour window is your advantage.
How many rounds is the Cymphony interview?
3 stages: Intro Call, Technical Deep Dive, Final Round.
Is the Cymphony interview hard?
The interview emphasizes technical depth and system design over abstract problems. Hardest stage: Technical Interview.
Does Cymphony give a take-home task?
Yes, Cymphony includes a take-home assignment.
How long does Cymphony take to get back to you?
Around 7 days across the full process.
What should I prepare for the Cymphony interview?
Prepare for technical depth and system design. A <50-person startup wants proof you can ship, not that you can whiteboard.
Where is Cymphony based?
Cymphony is headquartered in New York, USA.
Get Cymphony roles before they're posted
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching Cymphony
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+