Careers
Build the identity layer other products get to take for granted.
Oidot is small on purpose. Every person here owns a real piece of the system end to end, not a slice of a ticket queue.
How we work
Fail closed
Access control defaults to denied, not allowed. We would rather an engineer file a bug about a missing permission than discover a system that quietly granted one.
Write the reasoning down
Every non-obvious decision gets a line in a decisions log, not just a chat thread that scrolls away. The next person to touch the code should be able to find out why, not just what.
Boring at the base, deliberate at the boundary
We would rather run one well-understood service than a distributed system with nothing yet to distribute. Infrastructure gets added against a named requirement, never a trend.
No invented numbers
If a metric isn't real yet, we say so and leave the section out. We won't publish a number we can't back up just to make a page look more finished than the product is.
Open roles
There are no open, funded roles right now. We'd rather leave this honest than list positions we can't actually fill — check back, or reach out if you think there's a fit worth discussing early. Get in touch.
Don't see the right role?
We're always glad to hear from people who care about building this kind of system correctly.