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 open sourced Oso late summer 2020, and the feedback has been amazing. We are out to build a big, vibrant community of open source users, and we need to be proactive to achieve that goal. To that end, we are hiring our first developer advocate. This person will report to the cofounder/CTO and work closely with him, the cofounder/CEO, and the rest of the engineering team.

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

Note: we are ultimately building a team of developer advocates. We ❤️ generalists, but we know that the role can take different forms, and not every member of the team will be able to do all the things all the time. If you see a piece of yourself in the "What you'll do" below, we encourage you to apply.

What you'll do

• Show Oso to the world. Get the word out on Oso, inspire users and help them adopt it with demos and sample apps, blog posts, tutorials, and videos, plus talks at meetups, conferences and on podcasts.
• Talk to users. Engage with users on Slack, Twitter and other online channels to ensure they have direct access to the team and whatever they need to be successful. Capture feedback and feed it back into our roadmap. Write and share our changelog entries via Twitter, Slack and email to close the feedback loop with our users.
• Build the community. Build and empower community champions that amplify your work. Engage with adjacent communities. Connect users who have relevant problems with each other. Create a sense of belonging with hackathons, AMAs or whatever else you can think of.
• Desired: carve out engineering projects and ship code for the core product (to stay close to the codebase)

Who you are

• You're an owner. You are accountable to results over the process. You prioritize your team's success over the success of any one project.
• You like to ship. You get satisfaction from getting concrete output into users' hands in a short period of time. You prioritize speed over explicit permission, and a calculated risk over further analysis.
• You're for the makers. You look for ways to make easy things easy, and impossible things possible. You prioritize the developer experience above ours.
• You give and take feedback. You seek out critical feedback. You have the courage to give critical feedback to others.
• You pierce your echo chamber. You ask questions, and look for your blind spots by talking to people who aren't like you.
• You're always learning. You have a history of practice and expansion. You're not afraid to take something on just because you don’t know how to do it yet.
• You can see your team as people. You have their backs and cheer them on.

Requirements

• You want to build something from scratch
• You have experience as a professional developer working in more than one programming language
• You can create clear and creative technical content, and you can demonstrate this by sharing at least 3 talks and 3 writing samples of long-form content you created on your own
• You have been actively involved in a developer community and can draw on this experience to build a new community, e.g., you understand how the community is organized, how its members engage with each other, what motivates them, how to support them
• You have worked at a startup or in a similar environment

Nice to have

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