I am applying for Buffer's Senior Design Engineer role.
Before I wrote a single line of my application, I read everything I could find about how Buffer builds. Their engineering blog. Their accessibility statement. Their homepage hero post. Their Build Week recap. Their Popcorn To Go mobile design system writeup.
Most candidates read the job description. I read the codebase philosophy.
Here is what I learned.
Buffer thinks about accessibility the way great engineers think about testing — as infrastructure, not cleanup.
Their engineer who built the new homepage hero described something I have rarely seen written down so clearly: accessibility-first design. Decorative elements wrapped in aria-hidden from the start. Motion designed for prefers-reduced-motion before the animated version was even built. Not bolted on. Not an audit item. Built in from line one.
That is the right way. And it is harder than it sounds — because it requires resisting the temptation to ship the visually impressive version first and fix accessibility later. Buffer's team resists that temptation. I noticed.
Their accessibility statement is honest in a way most companies' aren't.
Buffer publicly states they are partially conformant with WCAG 2.1 AA. They do not claim full compliance they have not earned. They list what they are working on. They publish an email address for feedback.
That honesty tells me more about the engineering culture than any job description could. It tells me this is a team that ships, acknowledges what is not finished yet, and keeps improving. That is the environment where a Senior Design Engineer does their best work.
What a design system actually is.
A component library is a collection of UI pieces. A design system is a contract — between the engineer who builds the component and every engineer who will ever use it. When you use a Button from the system, you should not have to think about ARIA roles, focus states, or contrast ratios. The component already handles it. The contract guarantees it.
The Senior Design Engineer's job is to write contracts that hold. To make the right thing the easy thing. To catch violations in CI with jest-axe before they reach a page. To own prefers-reduced-motion at the token level, not the component level.
That is what I do. That is what I want to do at Buffer.
Why I am writing this publicly.
Because Buffer operates in public. Their salaries are public. Their revenue is public. Their engineering decisions are public. Writing a private cover letter to a company that builds in public felt like the wrong approach.
So here is my thinking, in public. If it resonates with someone at Buffer, I would love to talk.
Jaivik Parekh
jaivikparekh1320@gmail.com
