Careers
The open roles are listed below — each says what the work is, where it is done and how an application is read. A speculative application is welcome as well: hr@zedmos.com.
Read the role, then apply. Applications go to the hiring manager and are answered — including the ones we decline.
Engineering · Senior
The services between the console and the fleet: carrying policy out to firewalls that may be on any of several versions, bringing results back, and keeping a multi-tenant system strict about which customer is which. The hard parts are distribution, upgrade safety, and never losing a record.
Engineering · Senior
You would work on the engine itself: the code that sits on a firewall's interfaces, decides what a session is, and reaches one verdict about it before the traffic moves on. It runs inline on appliances carrying production traffic, which is the whole difficulty and most of the interest.
Packet handling on the interface, protocol classification, TLS, and the evaluation that turns everything known about a session into one decision. It runs inline on firewalls carrying production traffic, so correctness and cost per packet are the same conversation.
The services that carry policy out to a fleet, bring the results back, and keep a multi-tenant console strict about which customer is which. Concurrency, safe upgrades across many versions at once, and not losing records.
A CV to hr@zedmos.com, and — more usefully — something you built or something you took apart, with a paragraph on what was difficult about it. Both are read. The second is what the conversation will be about.
Germany. Part of the work is close to hardware and happens at a bench, so it is not fully remote. English or German is fine, in writing and in the interview.
Report it at security@zedmos.com under our disclosure policy. That channel is open to everyone and is not a recruitment process — a finding is welcome whether or not you want a job, and credited if you want to be credited.
Applications: hr@zedmos.com
See the open roles