Careers
Banks, hospitals, and agencies can't approve agent products stitched from a dozen SaaS vendors — and self-hosted has always meant inheriting an ops burden. Visca closes both gaps: the whole stack — identity, credentials, runtime, audit — running inside the buyer's walls, maintained by its own operators. The humans here do the three jobs the stack reserves for humans — declare intent, sign approvals, hold the kill-switch — at company scale. If you've built infrastructure that other people trusted with their work, we should talk.
Skills can be taught. Calibration on these is what we look for in interviews. If they feel obviously right, you'll fit in. If they feel constraining, you probably won't.
Everything we ship will be read by a security team before it runs. We design for that reader: explicit identity, scoped credentials, evidence by default. A feature that can't survive a security review isn't finished.
The vendor's ops team was SaaS's secret advantage. Ours is agents — operators that deploy, upgrade, patch, rotate credentials, and answer incidents inside the customer's perimeter. We build the operators alongside the stack, not after it.
Every operation is a principal acting within a scope through one governed gateway — including our own maintenance. No tribal knowledge in SSH sessions, no history in console clicks. If it isn't on the ledger, it didn't happen.
Declare intent, sign approvals, hold the kill-switch. We are explicit about what stays human, and we engineer everything else to run without heroics — in the product and in how the company itself operates.
Integrated, opinionated, secure by default. The engineer who never reads the docs still ships something a security team can approve. That is the bar, and it costs us obvious-looking work we deliberately decline.
We disagree with each other when we are wrong. Honesty over agreement. We push back, we explain reasoning, and we credit the change-of-mind explicitly. No sycophancy.
We hire archetypes more than we hire titles — we are early enough that the right person can shape the role. If your experience fits one of these and you would bring it to a self-hosted, self-maintaining stack for regulated industries, write to us.
You have built systems that other people trusted with their work. You think in protocols, not features. Comfortable with Go, Rust, and the kinds of papers that distributed-systems engineers cite over lunch.
ApplyProduction cryptography practitioner. You've designed identity systems, attestation chains, capability schemes, or PKI. Equally comfortable with the math and the operational realities of key custody.
ApplyYou have designed developer surfaces (CLIs, SDKs, eval harnesses, paved paths) that thousands of engineers depend on. You believe defaults are the product and that the best documentation is the one that doesn't need to exist.
ApplyYou've stood up production deployments of enterprise infrastructure inside regulated organizations. You speak both CISO and platform-lead, and you can read a code repository as well as you can read a procurement RFP.
ApplyYou write the kind of documentation that engineers cite back to other engineers years later. Specifications, architecture references, the documents a security review actually reads — all of it.
ApplyDon't see your fit?
Where
Remote-first, with optional in-person time at the founding office. We hire across time zones that overlap with one of our two core working windows.
Hours
Asynchronous defaults; meetings only when synchronous is genuinely cheaper. Maker time is protected — engineers should expect long uninterrupted stretches every week.
Process
Conversation first, structured interview second, paid trial project for finalist roles. We do not do whiteboard puzzles. We will ask you to read a real internal document and tell us what you'd change.
The Autonomy Stack for regulated industries
Identity, credentials, runtime, and audit — shipped as part of your product, run inside your customer's walls, operated by agents under the same ledger as everything else. Nothing leaves the perimeter. Nothing is off the record.