Member of Technical Staff
athanor aiSeattle (WA)
About the role
Full-time Remote or Seattle Health, vision, and dental benefits About Athanor We build Kairos, a verification engine that proves or disproves computational claims with formal methods. Our customers are hardware teams, accelerator developers, and infrastructure engineers whose designs have to hold up to scrutiny, not just pass a testbench. We are a small, technical team where every engineer ships across the full stack. There is no distinction between "research" and "production" here. You will write Rust that runs in CI, Lean proofs that gate customer releases, and Python orchestration that coordinates multi-engine verification campaigns. What we look for Strong backend software engineering: you write clean, tested, production-quality code Rust experience: systems-level thinking, ownership model, no-panic production code RTL design knowledge: Verilog/SystemVerilog, synthesis, timing closure, gate-level reasoning EDA tooling familiarity Accelerator kernel development: NKI, CUDA, HLS, or similar hardware-targeted programming Comfort with formal methods: model checking, theorem proving, or equivalence checking (practical, not just theoretical)
Nice to have:
Lean 4 or other proof assistant experience Experience with Verus, Dafny, or other verified systems languages Prior work at an EDA company, chip design team, or hardware verification group Contributions to open-source EDA or formal verification tools How we work Small team, high autonomy, fast iteration Every engineer owns features end to end: design, implement, test, ship, support Heavy emphasis on correctness: property-based testing, mutation testing, formal proofs, CI gates that reject regressions Lean codebase discipline: complexity ratchets, no-scaffold rule, quality bar rises with every PR Direct access to founders and customers
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.