Code review for DevOps tasks
As a Developer Advocate, you will be responsible for building a strong developer community around Runops. In addition to advocacy, you will also have shared responsibilities for user education and community engagement.
The role will include writing a lot of content, tutorials, and docs and being active on the chat, social media, and even running online events.
You will have a significant impact on our users' developer experience, as well as our community and public image.
As a developer advocate, you will:
What we're looking for:
Come help fix the broken tech from the 80s that protect our data today.
Data privacy is so broken because systems to protect data are terrible. Companies are using technologies from the 80s (RBAC/VPNs) to protect our data. A company with 100 engineers has 50,000 RBAC policies to manage only for AWS EC2 service.
Runops is a client to databases, AWS, Kubernetes, and others. Users access Runops from Slack, CLIs, Web, IDEs, and others. We make accessing cloud resources easier than installing multiple clients and using VPNs. We leverage APIs and contextual data to make authorization decisions. By making security easy we fix data privacy.
The worst thing that can happen to an engineer is to get paged out-of-hours only to realize they can't fix the problem on their own. They did all the hard work of waking up, debugging the problem, and finding a solution. But when it's time to apply the fix, they don't have access. Time to call a DevOps engineer to get permission or have them run the patch.
DevOps means developers run their own code, but how can a developer operate a piece of software if she can't access the database, the cloud provider, or the Kubernetes cluster? Only a handful of people has access to these resources at most companies today.
This problem is not just bad on out-of-hour pages. DevOps teams centralizing raw access to production are bottlenecks to the whole engineering team. A simple query in the database to troubleshoot a problem can take hours for the busy and sad DevOps team to process the request in their queue.
It's not ok to keep making direct updates to the database or change things in the AWS console all the time. CI/CD and infrastructure as code are great tools. But direct access will happen no matter how much automation a company has. Restricting raw access to a few engineers results in bad culture incentives and an environment with low trust and autonomy.
Runops democratize access to production to enable DevOps. We fix this problem by adding security and compliance into easy-to-use clients. Runops enable any engineer to make production access with security and reliability.