Kateryna Porchienova
Senior Engineering Manager at Buffer
In this episode of Señors @ Scale, host Neciu Dan chats with Kateryna Porchienova — Senior Engineering Manager at Buffer — about her programming journey, the craft of animation, and why accessibility should be treated as a foundation of good engineering, not an afterthought.
Main Takeaways from my conversation with Kateryna:
🎨 Animation is the new differentiator.
With the cost of spinning up UIs dropping fast, the quality of motion and interaction defines product craftsmanship. Kateryna explains how details like view transitions and subtle microinteractions give products character — and why animation should serve accessibility, not fight it.
💻 Her path into programming wasn’t linear.
From Pascal and competitive programming in high school to optimizing payment widgets for revenue, Kateryna’s path shows how curiosity and frustration can turn optimization work into real engineering.
♿ Accessibility starts with understanding assistive tech.
She breaks down how screen readers, switches, and even sip-and-puff devices interact with the accessibility tree — and why every frontend developer should try navigating their own app using only a keyboard.
🧩 Learn to use semantic HTML and minimal ARIA.
Many teams overcompensate with ARIA attributes. Kateryna warns that websites using ARIA incorrectly have more errors than those without. Accessibility is about balance — not verbosity.
🛠 Use tools that do the hard work for you.
Libraries like React Aria, Radix, and testing setups in Storybook, Playwright, or Lighthouse help ensure consistent accessibility without reinventing patterns from scratch.
🤖 AI can both help and harm accessibility.
She discusses how AI-assisted code can “overdo” accessibility — overlabeling or injecting redundant ARIA attributes that break experiences. Yet the same technology can generate alt text, identify missing roles, and speed up audits when used thoughtfully.
🚫 Avoid common pitfalls.
From modal dialogs that trap focus to icon-only buttons without hidden labels, Kateryna outlines the subtle mistakes that make UIs unusable for assistive tech — and how to fix them.
💬 Advocacy has to become culture.
Accessibility shouldn’t be a ticket in the sprint backlog. Kateryna shares how teams at Buffer bake accessibility into QA, code review, and design processes — treating it like testing rather than a “nice-to-have.”
📚 Recommended Reads:
- Inspired: How to Create Tech Products Customers Love by Marty Cagan
- Nonviolent Communication by Marshall B. Rosenberg
🎬 Also in this episode:
- How early exposure to inclusion shaped Kateryna’s engineering mindset
- Practical tips for testing with screen readers and reduced motion settings
- Why over-animated UIs can make users physically ill
- How Apple’s AI-generated alt text pushes accessibility forward
- Building a cross-functional culture of empathy and inclusion
Episode Length: 40 minutes of accessibility insights, animation philosophy, and leadership lessons for modern engineering teams.
💡 More Recent Takeaways
Señors @ Scale host Neciu Dan sits down with Santosh Yadav, principal developer advocate at CodeRabbit and one of only around 80 GitHub Stars in the world. Santosh started hating C in 2004, fell for C# by 2008, and turned a year of open source contributions to Angular and NgRx into a stack of community titles — Google Developer Expert, GitHub Star, Nx champion, and Microsoft MVP. As a staff engineer at Celonis he led the move of 20-plus apps to module federation and drove Nx adoption across 30-plus teams when the product grew from four apps to thirty. From the year-long incremental migration off a single deployable unit, to why polyrepos can't give AI tools the context they need, to how Nx's affected graph and build caching tame a 20-million-line monorepo, to running code review for free for open source at CodeRabbit, this is the monorepo conversation grounded in someone who actually shipped one at scale.
Señors @ Scale host Dan Neciu sits down with Nicolas Beaussart-Hatchuel, staff engineer at Payfit and one of the maintainers of TanStack Router. Nicolas's path started with C macros to auto-generate his student paper headers and frontend learned by building phishing login pages for practice, took him through an iframe-based AngularJS-to-Angular 2 micro frontend migration at a web radio platform, into open source contributions across NX, ESLint, Vite and Hasura, and finally to maintaining one of the most ambitious routers in the React ecosystem. From why TanStack Router exists, to migrating Payfit's 300-route, 1.5-million-line codebase off React Router v5 using the strangler pattern, to collapsing 25 polyrepos and five different micro frontend strategies into a single modular monolith, this is the routing conversation most engineers never get.
Señors @ Scale host Neciu Dan sits down with Mark Erikson, maintainer of Redux and senior front-end engineer at Replay.io, where he works on a time-traveling debugger. Mark's path started with a 286 he got at eight years old, ran through a computer science degree, four years teaching English in China, embedded software at Northrop Grumman emulating legacy CPUs in old aircraft, and a chain of projects — GWT, jQuery, Backbone — that led him to React and Redux. From the @deprecated backlash that had people insulting him on the internet, to why the Redux core hasn't meaningfully changed since 2016, to what RTK Query actually solves, the underused listener middleware, building source maps into React's own build pipeline, and how Replay's recordings now hand debugging over to AI agents — this is the Redux conversation grounded in two decades of shipping software.
Señors @ Scale host Dan Neciu sits down with Dominik Dorfmeister — better known as TkDodo — the maintainer of TanStack Query and a software engineer at Sentry. Dominik's path started at a technical high school in Vienna, ran through JVM backend work in Java and Scala, and turned to frontend around the introduction of TypeScript. During the pandemic lockdowns in Austria he started answering questions in the TanStack Discord, got addicted to the instant gratification of helping people, and slowly turned that into a blog, a first code contribution six to eight months later, and eventually maintainership of TanStack Query. From tracked queries and the chaotic version-three-to-four rename, to the version-five mistake he still dreads, to ripping 28,000 lines of dead code out of Sentry with Knip and building Sentry's new design system, this is the open source maintenance conversation most developers never get to hear.
📻 Never Miss New Takeaways
Get notified when new episodes drop. Join our community of senior developers learning from real scaling stories.
💬 Share These Takeaways
Want More Insights Like This?
Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.