About the role
Old problem, new $25B+ market Companies like AWS, Stripe, and Twilio have shown that if a technology isn't core to your value proposition, you should offload it. Still, every engineering team builds and rebuilds one piece: authorization , how you control who has access to what in your app. We intend to change that. We see a world where developers never roll their own authorization again, and instead say, "Just use Oso" – the same way you might say, "Oh, you should just use Postgres for that." In doing so, we're creating the $25B+ authorization market. Why Oso? We have the lead – in traction, capital, and team. Traction : Oso is used by thousands of companies from startups to the Fortune 500, like Wayfair, ProductBoard, Vanta, Brex, Verizon, ZoomInfo, and Duolingo. Capital : We're backed by the world’s best investors, including Sequoia, Felicis, and a standout group of infrastructure founders and operators: Olivier Pomel (Founder, Datadog), Dev Ittycheria (CEO, MongoDB), Armon Dadgar (Founder, HashiCorp), Edith Harbaugh (Founder, LaunchDarkly), Guy Podjarny (Founder, Snyk), Paul Copplestone (Founder, Supabase), Christina Cacioppo (Founder, Vanta), and Calvin French-Owen (Founder, Segment). Team : We've spent 5+ years going deep on the domain. We've met with thousands of engineering teams and know more about this problem than anyone. And we have two of the best developer go-to-market leaders on earth who have done it before at MongoDB and Snyk. Why now? We're at an inflection point. What it takes to get from where we are today to a world where developers say “Just use Oso” is going to be different. And we see that. The opportunity is for you to join at this inflection point, in a role that’s bigger and different than usual.
What you'll do Experiment, design, and build UIs, flows, features, and layers of abstraction that decrease the amount of work our users have to do. Lots of devex Expand use case coverage of our core authorization service Build and operate infrastructure for our highly available and low latency cloud service Plus, help build a company and community from the ground up by wearing other hats, including: Writing documentation and blog posts to excite and support new users Engaging with users through support channels (e.g., Slack) to help them with their problems Here are examples of things we've worked on: Built a visual policy builder for our declarative policy language, Polar Built an interactive debugger, called Explain, to help users understand why authorization requests succeed or fail Implemented incremental forward chaining to cache authorization responses for deeply nested recursive queries