engineering
Posted Apr 8Founding Developer Advocate
at Infracost
United StatesRemote
Responsibilities
- You’ll collaborate with marketing, product and engineering, but you’ll own the developer voice outside the company. - Create content: Create compelling content (blog posts, videos, tutorials, demos, sample code, example repos) that show developers how to use Infracost and integrate it into their workflow. - Build community: Build awareness through GitHub, Slack, YouTube, Reddit, Hacker News, and relevant dev communities or podcasts.
- Test messaging, content formats, and distribution strategies with one goal in mind: increasing developer signups. - Feedback loop: Collect insights from the community, report back to product and engineering, and help shape the roadmap. PRIOR
Requirements
- EXPERIENCE - Developer-first mindset: Background in DevOps and Infrastructure as Code with a passion for educating and enabling developers. - Content creation: Demonstrated ability to create engaging technical content; blogs, videos and social media posts. - Community building:
- Experience engaging with developer communities online and offline. Ability to simplify technical concepts into clear, developer-friendly messages. - Significant advantage:
Benefits
- ABOUT INFRACOST The spend on public cloud is fast approaching $1 trillion per year - we estimate this boundary will be crossed before the turn of the decade.
- BENEFITS - Fully remote team - Two meetups a year - last year we went to Croatia and Barcelona - Employee-friendly equity terms, including a 10 year exercise window https://www.abar.tech/articles/10yr-excercise-window/ - 401k matching (US) - Health, dental, and vision insurance (US) - 31 days paid leave per year (includes national holidays) - 12 weeks paid parental leave ABOUT THE INTERVIEWS - 25 minute initial chat - 55 minute interview about your Dev Rel
Contact
- The Infracost CLI repo https://github.com/infracost/infracost/ has 12K stars on GitHub! There’s a massive opportunity to help organizations proactively manage their cloud spend; rather than reacting to surprise cost spikes after the fact.