Job Board
for underrepresented folks in tech

Back to all jobs
Photo of Oso

emoji of a pushpinNew York / Remote
emoji of a woman of coloremoji of a man6 people in techemoji of a woman of coloremoji of a woman 2 women in techemoji of a rainbow 1 LGBTQIA+ folks in tech

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.

JOB DESCRIPTION

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 done...until 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.

What you'll do

  • Experiment, discover, design, and build features and layers of abstraction that decrease the amount of thinking and coding that our users have to build authorization into their apps
  • Add features to the core of Oso in Rust – like new language operators – as needed to support new authorization use cases

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

Who you are

  • You're an owner. You are accountable to results over the process. You prioritize the team's success over the success of any one project.
  • You ship, listen, ship, listen. You're happy to explore product ideas through design, hacks and guides before building something fully baked. You have no problem throwing away ideas and code if they don't pan out. You get satisfaction from getting concrete output into users' hands.
  • You're for the makers. You want to understand our end users' world and prioritize solving their authorization problems above everything else, including your own personal preferences and the elegance of the solution.
  • You give and take feedback. You seek out critical feedback. You have the courage to give critical feedback to others.‍
  • You can see your team as people. You have their backs and cheer them on.

Requirements

  • You have worked at a startup or in a similar environment
  • You have built complex systems and can bring that to bear – e.g., how to break up a system into clean reusable components, how to design interfaces and abstractions given the way you expect internal and external users to consume them
  • You can program at different levels of the stack – i.e., in at least one web language like Node.js, Python, or Ruby and one lower-level systems language like C/C++, Go, or Rust

Nice to have

  • Experience with our problem space, e.g., building internal authorization systems
  • Experience with multiple web frameworks and ORMs

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.

INTERVIEW PROCESS

Interview Process: 

  • Exploratory Chat with CEO
  • Exploratory/Technical with CTO
  • Virtual On-Site (Split between 2 days) 

Day 1:

  • Work Sample (we provide a take home work sample, you work on them on your own, send them to us when done, then we discuss them live

Day 2: 

  • Debugging (We offer this in Python, Ruby, C++ or any language you are comfortable in)
  • Product Engineering
  • 1:1 with CEO
  • Chat with Team

DIVERSITY, EQUITY AND INCLUSION

For Oso leadership, inclusivity is about listening and welcoming.

Everyone has a weekly check-in with the CTO, plus a weekly, bi-weekly, or monthly check-in with the CEO (up to them). This is a meeting where leaders bring no agenda and just listen — an opportunity for team members to share anything on their minds and provide feedback.

We model inclusive language, including using everyone's preferred pronouns (which are in everyones' display names in Slack).

We model different types of schedules for folks with different life requirements. The CEO, for instance, logs off everyday at 6 pm to be with his kids, like clockwork.

We host events to that both celebrate inclusion and align with the company mission. For instance, in June 2021, for Pride Month we're running events where we are donating to non-profit LGBTQ+ support organizations for every engineer that attends.

Here's a tweet from Annie, one of the engineers on the team: https://twitter.com/AnneOgborn/status/1400105425761189894

Apply Now
When you apply, please mention that you found the posting on Diversify Tech!


Be the first to know!

We'll let you know as soon as a job is posted on our job board.

Subscribe →