We should be clear right up front that you’ll need to have a strong technical background for this to work. Our product is a DevOps-focused tool to aggregate and instantly search logs, graph metrics, monitor server status, and alert when things go wrong. The previous sentence should make sense to you and perhaps even excite you. (Ideally, you should have an engineering background, have worked in DevOps, or otherwise have reasonably deep experience in these areas.)
Here are three examples of pieces we’ve written that closely model the kind of writing we’ll want you to do:
We’ll give you lots of juicy source material to work with - straight from our engineering department - but we’ll expect you to craft it into something interesting and view-worthy. And you’ll be encouraged to source your own material & topics as well.
We think of our blog as a way of telling the Scalyr story to our (current and future) partners, investors, employees, and customers. We want to produce content that falls into a few different categories; it's up to you to tell us which areas are the best fit for your experience and writing style.
You’ll be working directly with our CEO and Head of Marketing, who can help edit and direct your writing projects if/as needed.
And your work will matter and have a huge impact on the business! Our blog posts are widely read and are a primary source of growth.
We’re a VC-funded startup, founded in 2011 by former Google engineers with a deep background in technical operations. We’re backed by top-tier VCs (Google Ventures, Bloomberg Beta, Susa Ventures, Sherpalo Ventures) and have plenty of cash. We have - *gasp* - paying customers and a healthy business model. We’re growing. We’re nerds. And writing is in our DNA -- Our founder, Steve Newman, was one of the creators of Writely (acquired by Google to become Google Docs in 2006.)
Send a brief cover note, a portfolio, blog, or other link to some technical writing you’ve done, and one suggestion for a blog post you think Scalyr should publish (and that you'd enjoy writing) to firstname.lastname@example.org.