"How Does This Make My Developer's Day Better?" Asks Render Founding DevRel Engineer Shifra Williams

0:00This audio is presented by Hacker Noon, where anyone can learn anything about any technology. How does this make my developers day better? Ask Render Founding DevRel Engineer Shifra Williams by Shifra Williams. Let's start with you. Who are you? What do you do? And what does your company build? I'm Shifra, dea scientist, technical writer, and educator turned DevRel. I'm the Founding Developer Relations Engineer at Render, the intuitive cloud platform for deploying any app or agent. What does DevRel actually mean to you? Is it marketing, engineering, product, or something else entirely? DevRel is absolutely the intersection of marketing, engineering, and product, but that's more of a classification. The process of DevRel, to me, is about building relationships and trust with developers and showing them how your tools make their day materially better. DevRel works in both directions. You speak for the company to developers, and for developers inside the company. How do you balance the two, and when have you pushed back on your own team for developers'

1:00sake? To be honest, we all lean more heavily on the former. One example that comes to mind was exploring AI-generated video to showcase our product. While it was interesting, it felt like the wrong choice and I knew that it would cost trust with developers. They want to hear from real people, and I want to show them aerial human developer experience. I'm grateful that my team trusted my input on that decision. Tell us about your community. Who's in it? How big is it now? And what helped it grow? We now have 7M plus developers building on Render. It's a diverse international community of founders, software engineers, data scientists, and more. But what they all have in common is that they want to focus on building their product or project at scale. Render is such a loved platform that a lot of the growth is product-led and word-of-mouth. That aside, I made some product videos to trech 8 million views, and I've spoken at events around the world demoing Render. On a more personal note, I have a little podcast called Saturday Data and a community on LinkedIn, mostly in the data and

2:03software engineering space, and I'm super grateful for those who have followed me since the beginning less than three what's a launch or campaign you ran that you're proud of. What happened, and what did you learn? I'm incredibly proud of the Render workflows launch. I built one of the demo apps to showcase a data pipeline built on workflows as well. One takeaway was that a lot of developers want to see demos at scale. Looking back, Render is cool, but I wish I emphasized the scale at hundreds of thousands of workflow tasks and heavier CPU usage to show the kind of fruit with the product I scapeable of. I'll take that lesson with me. In a product-led world, the product is the marketing. How do docs, onboarding, free tiers and sample apps fit into your dev-roll work, and what's one change that measurably improved developer adoption? Thinking about launches is omnichannel campaigns. Every launch should be a blog, a landing page, a YouTube video, a social push, and a partner collaboration within product documentation and banners to show the user what's new. We have to keep it all connected, anything else is a missed opportunity. What's your favorite piece of content

3:07your team has shipped, and why did it work? One recent piece I'm proud of is a blog post I collaborated on with Mac, our analytics engineer. How Render workflows powers our internal data pipeline? It brings together everything I'm passionate about. Work flows, data, dog fooding, humor, and patterns that developers can apply to their own work. Plus, our data team is delightful to work with. How do you measure whether DevRel is working? What do you track, and what do you ignore? We have extensive tracking for all the concrete outcomes our leaders care about, from signups to pipeline generated by our team. We're constantly monitoring those numbers to ensure they're healthy. Beyond that, it's all about making a positive impact in conversations with developers on the ground. When a developer came up to me at my PR, I'd event to tell me they almost cried tears of joy because of how much it meant to them, that was a massive win. Talk is cheap, show me the code. Linus Torvalds wrote this on the Linux kernel mailing list in 2000. How does that idea shape the way you reach developers? As I've mentioned in previous questions,

4:12everything I do starts from first principles grounded in one question. How does this make my developers day better? That starts with code usability and ergonomics and extends into a lot of different areas. When developers point out quick fixes in our website, I PR them myself, and my engineers appreciate it. When I find UX issues, I put myself in the user's shoes and pass them onto the team immediately with my recommended fixes. The code first perspective is in ethos and a mindset I try to inhabit every day. There's a well known saying that developers are allergic to marketing. Do you agree? How do you reach developers without it feeling like marketing? 100% accurate. I don't market to developers who won't benefit from what I have to offer. I show value to the developers who will. Kathy Sierra argues in bad ass. Making users awesome that the goal is to make houses awesome. Not to make the product look awesome. How does that idea show up in your work? It aligns with how render operates as an infrastructure company. We're here to get infrastructure out of the way and make it as flexible as possible so our users can build

5:15anything they can imagine. The best products focus on enabling the user, not forcing them into a constrained framework for arbitrary reasons. One way this shows up for me is meeting users where they're at in terms of architecture. Render is a full stack platform but migrations can be intimidating. That's when I encourage developers to try one new render service like workflows instead of always pushing them to migrate an entire stack. The ability to adapt and be flexible is a core part of dev-real work. How did you first come across hacker noon and is there a story you've read or written here that stuck with you? I found out about it recently. As a fan of PIDANTIC and observability tooling, I enjoyed this one. Observability first AI agents. What you gain and what you give up. Especially this quote. At this point I discovered a bug that actually made me happy. Who's dev-real work do you admire most? Whether people, companies or programs, and what do they do that others should copy? My friend and mentor, Laii's Carvalho at PIDANTIC. Her talk,

6:16the open source of self, is one of the best I've ever seen. She's incredibly technical, creative, smart, humble, and kind. She came up in the Python community and she pays forward everything she's learned while lifting up marginalized voices along the way. I'm truly privileged to call her my collaborator and my friend. Are you a dev-real leader? Get interviewed. Thank you for listening to this hacker noon story, read by artificial intelligence. Visit hacker noon.com to read, write, learn, and publish.