About Ammit
At Ammit, we are rebuilding how identity works on the internet. We are designing and implementing a next-generation identity management system backed by KERI (Key Event Receipt Infrastructure) — a protocol designed for absolute autonomy, minimized trust, and cryptographic security.
What we’re looking for
- Looking for skilled, passionate professionals, not rock stars.
- Team players that can collaborate and are passionate about their skillset.
- Passionate about building products and systems that make a difference across the globe.
Our Philosophy on “Experience”
We don’t care about an arbitrary “years of experience” number on your resume. We’ve seen engineers with two years of experience write beautifully decoupled, secure systems, and engineers with ten years of experience write unmaintainable spaghetti code (and similarly for UX and other disciplines). We care about your craft. If you prioritize safety and security as first-class citizens, prioritize the user experience over quick results, and structure solutions for the big picture, we want to talk to you.
Why Join Ammit?
Hard Engineering Problems: You will be working on the cutting edge of decentralized identity and cryptography. This isn’t another CRUD app; it’s infrastructure that matters.
Design Autonomy: We value good ideas over hierarchy. You will have a massive say in how our systems are structured and engineered.
No Bureaucracy: We are a lean startup. We value deep work, asynchronous communication, and clear thinking over endless meetings.
How to Apply
Skip the generic cover letter. Instead, send us a link to a repository you’re proud of, an architectural document you’ve written, or a brief write-up of a complex software design problem you solved and why you solved it the way you did.
Reach out to us at contact@ammit.org and let’s build the future of identity together.
Open Roles
Crypto / Rust Core Engineer Engineering
We don’t believe in bloated, fragile codebases. Our engineering philosophy is simple: do it right, design it securely, and write it once. Our core logic is built entirely in Rust, which we then project into iOS, Android, and web services via UniFFI and Kotlin.
What You’ll Do
Architect and Build the Core Engine: You will be a primary contributor to our core Rust codebase, implementing KERI-backed identity management logic for multiple network-connected devices.
Design Multi-Platform Bindings: Work closely with UniFFI to package our core Rust logic into robust, idiomatic interfaces for mobile (iOS/Android) and backend web services.
Prioritize Security and Correctness: Since we are building an identity system, “moving fast and breaking things” isn’t an option. You will design software that is secure by default, leveraging Rust’s type system to enforce invariants and prevent edge-case vulnerabilities.
Collaborate on Ecosystem Boundaries: Ensure that our core engine exposes clean, logical APIs that seamlessly integrate with our Kotlin-based web services and mobile environments.
Who You Are
A Systems Thinker: You care deeply about software design patterns, domain-driven design, and structural maintainability. You write code that other developers find intuitive to read and safe to modify.
Proficient in Rust: You are highly comfortable with Rust’s ownership model, lifetimes, macros, and async paradigms. You know how to use the type system to eliminate bugs at compile time.
Security-Minded: You understand the basics of cryptography (or are eager to master them) and naturally think about threat modeling, attack vectors, and data minimization when designing systems.
Polyglot Curious (Bonus): Your primary home is Rust, but you aren’t afraid of the boundaries. If you have experience with Kotlin, Swift, or mobile application development, or if you’ve worked with foreign function interfaces (FFI) before, you’ll hit the ground running.
UX Design Design
A technically perfect identity system is useless if real people can’t understand it, trust it, or use it every day. We’re not looking for someone to skin wireframes—we need a designer who thinks holistically about what it means to own your identity, recover from mistakes, decide who to trust, and stay connected with the people who matter.
What You’ll Do
Shape the End-to-End Experience: Map and design how people discover, establish, manage, and recover identity across devices and contexts—not as a sequence of screens, but as a coherent journey people can reason about.
Design for Trust and Connection: Prototype and refine flows for peer discovery, verification, credential sharing, and ongoing relationships. Help users answer “Who is this?” and “Should I trust them?” without drowning them in cryptography.
Ground Solutions in Real Users: Conduct research, test assumptions, and validate designs with people who aren’t security experts. Translate mental models, fears, and everyday workflows into interfaces and interaction patterns that feel natural.
Partner with Engineering: Work alongside our Rust and mobile teams to balance usability, security, and technical constraints. Advocate for the user when tradeoffs arise—and help engineers see why a design decision matters, not just what to build.
Define Information Architecture and Patterns: Establish reusable patterns, language, and structure so the product stays consistent as we grow. Think in systems: onboarding, settings, notifications, error recovery, and cross-platform parity.
Who You Are
A Systems-Level Thinker: You design experiences, not just UI. You care about information architecture, mental models, edge cases, and what happens when something goes wrong—not only the happy path.
User-Obsessed: You’re passionate about making complex technology approachable for normal people. You push back on jargon, hidden state, and “expert-only” flows that leave everyone else behind.
Security-Aware: You understand that identity products can’t trade safety for convenience. You design friction where it protects users and remove friction where it only annoys them.
Collaborative and Articulate: You can explain your reasoning to engineers and stakeholders. You welcome technical pushback and use it to arrive at better solutions.
Craft Over Credentials: We don’t care how many years you’ve been titled “UX Designer.” We care whether you dig into hard problems, show your thinking, and ship work that makes people’s lives genuinely easier. A strong portfolio, case study, or walkthrough of a complex flow you untangled tells us more than a résumé timeline.
Customer Success Go to Market
Closing deals isn’t the job. We need someone who sits with customers—especially in regulated, technical environments—and learns what actually hurts: integration blockers, compliance gaps, workflows that break down, and requirements that never made it into a slide deck. You’ll bring those insights back to the team and help us build the right product, not just sell what we already have.
What You’ll Do
Listen Deeply: Spend real time with enterprise customers. Ask follow-up questions, sit in on working sessions, and understand their problems in context—not just what they say they need in a procurement call.
Translate Pain into Product Direction: Synthesize customer feedback into clear, actionable input for engineering, design, and leadership. Distinguish one-off requests from patterns that should change the roadmap.
Be the Voice of the Customer Internally: Represent enterprise needs in planning discussions. Push back when we’re building the wrong thing, and champion solutions that solve root causes—not band-aids.
Guide Adoption and Success: Help customers get value from what we ship: onboarding, rollout, troubleshooting, and ongoing check-ins. Success means they’re solving real problems, not just renewing a contract.
Bridge Technical and Business Worlds: Explain our platform to customer stakeholders who range from security architects to line-of-business owners—and explain customer constraints and priorities back to our team in terms we can act on.
Who You Are
A Problem-Finder, Not a Pitch-Giver: You’re genuinely curious about how organizations work. You’d rather understand a failed workflow than hit a quota with a feature checklist.
Technically Fluent: You can follow architecture conversations, read API docs, and talk credibly with engineers on both sides. You don’t need to write Rust, but you need to understand what’s feasible and why something is hard.
Enterprise- and Regulated-Industry Savvy: Experience with financial institutions—or similar regulated sectors—at a technical level is important. You understand compliance pressure, procurement cycles, and why “just ship it” isn’t always an option for our customers.
Collaborative and Credible: Customers trust you because you tell the truth. The team trusts you because you bring evidence, not anecdotes. You build relationships on both sides of the table.
Craft Over Credentials: We don’t care how many years you’ve carried a “Business Development” title. We care whether you’ve helped shape a product by listening well, whether customers come back to you for honest guidance, and whether you can show us how you turned customer insight into something the team actually built.
Get In Touch
Interested in joining the team? We'd love to hear from you.
Send us an email with your background and what excites you about the future of secure identity: