Technical Writer

New York or Remote (US/EU Timezones) /
Engineering /
Full-time
Old problem, new $25B+ market
Companies like AWS, Stripe, and Twilio have demonstrated that if a technology is not 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. You’ve probably started with something quick 'n dirty – some IF statements and roles in a database...until you need to add more features, and more features. And inevitably you band-aid onto this system until you have to do a big refactor. Have you seen this before?

We're changing this picture and in doing so, we are creating the next $25B+ dollar market: the authorization market. We’re on a mission to create the global standard for authorization. Our vision is that in 10 years engineers will spend 1/10 the time and brainpower they spend on authorization today.

Why now?
This is a once-in-a-career opportunity to join a company at a stage late enough that the problem and solution are de-risked, but early enough that you can shape the product, company, and the market.

Why Oso?
We started with an open source product – adopted by thousands of developers at startups to the Fortune 100, like Wayfair, Intercom, Visa, Oxide, and Codecademy. Adoption is growing week over week, and we’re now launching Oso Cloud. We have met with hundreds of engineering teams over the last 2 years and know more about this problem than any team in the market. Oso is:
- Backed by Bill Coughran at Sequoia, as well as the founders and CEOs of companies like MongoDB, Segment, LaunchDarkly, and Honeycomb
- Founded by Graham Neray (early MongoDB employee – helped scale from $1M —> $250M revenue) and Sam Scott (PhD Cryptography)
- Advised by Abhishek Parmar, co-creator of Google Zanzibar and Airbnb Himeji
- Built by a team of user-first engineers, including multiple former startup founders and early employees

What you'll do

    • Write some quick blog posts by repurposing pages on the docs and interviewing our cofounder/CTO
    • Write longer 'how-to' blog posts, which might include building sample apps or showcasing new features in action
    • Write documentation on new features to make Oso users feel supported
    • Write long-form content that's relevant to our user base of developers trying to solve problems related to authentication, authorization, and application security more generally

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 ideas through design and hacks before writing 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 get what kind of content developers want to read, and can articulate this
    • You can write clear and creative content, and can demonstrate this by sharing at least 5 writing samples of long-form content you wrote on your own
    • You can code and learn new technical concepts quickly
    • You know the concept "Show, don't tell" (or you can Google it, then grok it)

Nice to have

    • Experience with our problem space, e.g., building 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.