New York or Remote /
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 lost time for an area that's not core to what most companies are trying to solve for their users, and what's more, no one on the team is feeling great about this work.
At Oso, we're building the first batteries-included library for authorization so developers don't have to roll it on their own ever again. We're designing slick APIs to cut down the amount of time they spend getting their system set up, and building a fully-fledged policy engine and programming language under the hood to ensure they can customize their system however they need. We don't have any product managers – the engineers on the team are responsible for taking broad problems, experimenting with potential solutions and shipping a superhuman experience for our users.
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're happy to explore product ideas through design, hacks and guides before designing and building something fully baked. 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 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 look for ways to make easy things easy, and impossible things possible.
- You're always learning. You have no problem throwing away ideas and code if they don't pan out. You are optimistic and/or determined enough to keep hunting for new ones. You're not afraid to take something on just because you don’t know how to do it yet.
- 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 can see your team as people. You have their backs and cheer them on.
- 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
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.