About the role
Developer Educator Developer Educator About Rippling Rippling is the all-in-one platform that lets companies run HR, IT, Spend, and Finance through a single employee graph. We started as an HCM platform. Over the last two years, we have become a configurable platform for business applications of every shape: custom apps built on the employee graph, data connectors to third-party systems, functions that let customers write code inside Rippling, and Rippling AI that automates the work that used to fall through the cracks between systems. Technical buyers don't know this yet. This role exists to tell them We prioritize candidate safety. Please be aware that all official communication will only be sent from @ Rippling.com addresses.
About
the role Developer Educator is a writing-first role. Your mission is to uplevel Rippling's profile with technical buyers: CTOs, VPs of IT, VPs of Engineering, and the technical stakeholders inside our customers and prospects who decide how systems get built. You will do this by telling the stories of the customers using Rippling in ways that look more like building software than configuring HR. Custom apps that replace bespoke internal tools. Data connectors that retire ETL jobs. Functions that automate workflows nobody wanted to own. AI that closes the gaps between systems. Most of this work has historically lived in spreadsheets or in the seams between three other vendors. Rippling is now the platform where it gets solved, and we need someone who can write the technical narrative that explains how.
What you'll do Write technical blog posts about customer solutions on the Rippling platform. Architecture overviews, real customer quotes, and the technical specifics of how the solution was built. Field reports, not marketing copy. Write technical white papers on Rippling's integration tech, platform capabilities, and the patterns enterprises use when implementing Rippling inside their broader tech stack. Interview customers and Rippling engineers to extract architecture decisions, tradeoffs, and the implementation details a technical reader actually wants. Partner with post-sales, FDE, product, and marketing to source customer stories and draft them into content that helps the broader market understand how innovative companies are solving business problems with Rippling’s tech stack . What you'll bring 5+ years of technical writing, developer education, developer relations, or technical PMM experience. A portfolio of in-depth technical content. Blog posts, white papers, specs, conference talks, or other long-form technical writing. The work should be detailed enough that a technical reader walks away understanding both how a system works and why it was built that way. Comfort reading architecture diagrams, understanding code (you do not need to write production code), and explaining enterprise SaaS integration patterns: APIs, webhooks, iPaaS, ETL/ELT, SSO/IdP, SCIM, identity, data residency. The interviewing skill to sit with a customer architect or a Rippling engineer and pull out the specifics that make a story technically credible. A strong opinion about what good technical writing looks like, and the discipline to edit yours down until it earns the reader's time. Self-direction. You will own the calendar, the customer relationships, and the editorial bar.
