Over the last 15 years, companies like AWS, Stripe, and Twilio have helped developers offload anything not core to their apps so they can focus on what matters to their users. Despite a lot of progress in developer tooling, most developers still roll their own authorization.

You might start with something quick ‘n dirty – some IF statements and roles in a database, which may not be pretty but gets the job doneuntil you need to add more features, and more features. And inevitably every team band-aids onto this system until they do a big refactor. This is a waste of their time.

At Oso, we’re building the first batteries-included library for authorization so developers don’t have to roll it on their own anymore. We’re building slick APIs so they can get started quickly, and a fully-fledged policy language under the hood so they can customize their system however they need. We don’t have any product managers – the engineers on the team take big problems, experiment with solutions and ship a superhuman experience for our users.

The engineers who join now will not only have a disproportionately large impact on the product, but also on the culture and future of the company.

Note: We have no titles on our engineering team. Everyone is an Engineer. Compensation is commensurate with contribution.

Oso is an equal opportunity employer. All applicants will be considered for employment regardless of race, color, national origin, religion, sex, age, disability, sexual orientation, gender identity, veteran or disability status.