oso puts security in the hands of the makers. We're doing this by delivering security as code, or as Charity Majors (cofounder & CTO of Honeycomb) put it, "Consumer-quality developer tools" for security.
We recently released oso into Developer Preview, and the feedback has been amazing. While we've written a lot of documentation, one of the primary barriers to engaging new and would-be users is showing them when and how to use oso. To that end, we are looking for a technical writer to help us create more articles, blog posts and documentation for our user community.
Who you are
- Act like an owner - You are accountable to results over the process. You prioritize your team's success over the success of any one project.
- Desire for feedback - You seek out critical feedback. You have the courage to give critical feedback to others.
- Mind and heart of the user - You look for ways to understand users' motivations, frustrations, perspectives, and habits. You seek out information on target use cases. You prioritize the user experience above ours.
- Sense of urgency - You get satisfaction from getting concrete output done in a short period of time. You prefer to beg for forgiveness vs. ask for permission.
- Growth mindset - You cultivate your qualities and skills through effort. You have a history of practice, learning and expansion. You get pleasure out of having range
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
- 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 Rust