Security has spent twenty years getting very good at finding things. Almost nothing was built to finish the work those findings start. That is the problem we are here for, and there are three founding seats open on it.
Resolving assets, identities, access, ownership, and change from the tools a company already runs into one model that stays current as the environment moves.
Working out which exposures form a real path to something that matters, and being able to show the evidence behind every conclusion.
Drafting the fix, routing it to the team that can make it, inside the workflows and approval gates a customer already has.
Re-checking the environment after the fact and being able to say, with evidence, whether the exposure is actually gone.
Two build and prove the product. One builds how the market comes to understand it. All three are founding roles, which means you shape what gets built, not just how it ships.
You own how Unizo decides what matters: resolving fragmented findings into exposure paths, working out reachability across cloud, identity, and code, and turning that into conclusions a security team will act on.
For practitioners who have lived inside vulnerability management or exposure programs and have opinions about why they fall short.
You take Unizo into real customer environments and make it work there. Connecting their stack, running real exposures end to end, and carrying what you learn straight back into the product.
For practitioners who have been on the receiving end of vendor promises and want to build the thing that actually holds up.
You build the engine: the content, campaigns, events, and account programs that earn attention from enterprise security teams and turn a point of view into qualified demand.
For marketers who can earn credibility with technical audiences and would rather build the playbook than inherit one.
People who want the problem more than the title. This is a small team building something hard. Scope is wide, ambiguity is constant, and the work you do shows up in the product within days.
People who think in systems. Almost every hard problem here is about relationships between things, not the things themselves. That habit of mind matters more than any specific stack.
People who are honest about what is true. We are building a product whose entire promise is evidence. That standard applies to how we work as much as what we ship.
Probably not a fit if you want a defined lane, a long ramp, or a settled roadmap. None of those exist yet, and that is the point.
No cover letter needed. Send whatever shows how you think: a note about the problem, something you have built, or the reason this one is interesting to you.