Buffer Engineers

We value diverse paths and experiences. If this overlaps with much of your background, even if not all of it, we’d love you to apply. buffer.com/journey/cef391…

he goal? Make Buffer’s platform more approachable, extensible, and genuinely welcoming for developers. A few highlights: 🌍 Fully remote 🗓 4-day work week 💙 Values-led, people-first culture 💰 Transparent pay: $157K–$194K + equity

We’re hiring, and this one’s a big deal for how developers experience @buffer 💚 We’re looking for a Senior Developer Advocate to help shape how builders discover, understand, and build on Buffer.

Built a Claude skill for drafting social posts using: → Buffer's 100M+ post analysis → My personal learnings → 19 tips from X's open-sourced algorithm → iterate until happy Then let Claude schedule it via Buffer's (NEW API!) What would you add?"

Playing with agent skills this week. Which ones have actually stuck for you, and what do you use them for?

Tool I recently adopted: Wispr Flow 🎙️✨ I'm usually terrible at building new tool habits but their onboarding nailed it — three quick tasks and I was actually using it immediately 👇 Game changer to pair it with – Claude Code

This week at @buffer, we wrapped up Customer Experience Week ✨, a few days focused on making tangible improvements for customers and a nice way to end the year strong. I worked with @daisysmells and Ben on adding the ability to see previously used Threads topics in the Buffer composer. We finished it within the week, despite working across three continents, with teammates based in Thailand, Australia, and Panama and up to 16 hours between us. It took real async collaboration to pull it off, which made the experience even more rewarding. 🌎 I really like the idea behind CX Week. Ship something valuable, work with people you do not usually collaborate with, and show customers that we are listening. It is a great way to close out the year. Special thanks to @Marochko and Daniel for helping us improve the implementation even further. 🙌 This feature will start rolling out to users soon. Looking forward to seeing it in the wild. 👀

We just had a Customer Experience week where EVERYONE can tackle any part of Buffer to make our customer experience better. Seeing non-engineers shipping code? Always a highlight.

Granola just Crunched my year and reminded me of one of my favourite bugs I squashed 🐛✨ Users reported drag-and-drop was "painfully slow" — like 7+ seconds slow. After hours of investigating, the fix was deleting one line of CSS. Sometimes less really is more 🗑️💅

🎉 #JavaScript, happy 30th birthday! Who would have thought the future would look like it does today? I've got my own share of problems with you, but then there's this: “There are only two kinds of languages: the ones people complain about and the ones nobody uses.”

Last week, Buffer turned 15! Just like in childhood, it feels like such an important milestone, almost like when your little baby suddenly becomes a teenager 😅 . I'm really happy to be part of this special moment, and I’m looking forward to seeing how Buffer continues to grow.

Hey! 👋 I thought I'd reintroduce myself, here goes: I'm Daisy, a software engineer at @bufferdevs living in FNQ, Australia 🌴🐊 I create content about frontend development, delightful animations, & storytelling — not just for devs, but anyone who loves bringing the web to life!

Onboarding as an Engineer in the Age of AI: This is the first time I've onboarded at a company while modern LLM capabilities are readily available. The experience has been different, and better. I joined @buffer, an async-first, remote company that builds tools to help creators and businesses manage their social media. The team has been excellent at providing guidance, context, and everything needed for a smooth onboarding. But when it comes to engineering, some things are best learned by doing, getting your hands dirty with the actual work. AI tools have made it easier than ever to start contributing. Not just for implementation, but for building context and understanding what's happening in the codebase. 🔬 Research and Understanding The real value isn't in rushing toward a solution. It's in using AI to thoughtfully understand the codebase. When I encounter unfamiliar patterns or architecture decisions, I ask questions that help me learn the "why" behind the code, not just the "what." @github, @linear, and @NotionHQ agents have been particularly useful here. Instead of spending hours searching through repos and docs, I get pointed in the right direction quickly, then dive deeper. This extends beyond the codebase too. When I need to understand company-specific workflows and practices, how we handle retrieval, storage, validation, that sort of thing, I point AI to our documentation and have it research how things work internally. Then I can propose solutions that follow our established patterns rather than starting from scratch. ⚒️ Getting Unblocked Local setup issues are common when joining a new codebase. AI has been great at understanding error messages, suggesting fixes, and helping me get unblocked without waiting for someone else to be available. In an async environment, immediate help isn't always possible. Plan mode has been useful here too. Before committing to a solution, I explore multiple approaches, weigh trade-offs, and make more informed decisions. I don't just follow what AI suggests. I use my own engineering experience to evaluate what it proposes and decide what makes sense. 🧘 The Balance It's tempting to work in a silo when you can unblock yourself more easily. But that misses the point. I still reach out to teammates, ask questions, and pair on complex problems. I come to those conversations better prepared, with more context, with specific questions rather than broad confusion. Onboarding with AI tools available has been smoother. I can ramp up faster, understand the codebase more quickly, and get unblocked more easily. The tools help me contribute sooner while still building the relationships that make remote, async work successful.

kicking off a new project to improve developer experience at @buffer, and we have the most important question - what gif should represent the project?

A little humor to soften the “entire internet is down” energy.

We'll be shipping support for Android 16 soon! Excited to fully support edge-to-edge in our app - how did you plan for / manage adding support for this in your apps? 🤔

Serious question: what MCP are you using in your dev workflow that has meaningfully improved how you code?

during the past few days onboarding at @buffer, I’ve been using AI more as a discovery tool than anything else mostly to understand how things work and the decisions behind them wild to think a few years ago this wasn’t even possible

Some fun changes are coming to Buffer, just in time for Halloween 👻