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 Carson Gross, creator of HTMX, principal at Big Sky Software, and computer science professor at Montana State University. Carson has been programming for more than 30 years, from HyperCard on a family Mac to Excel macros for an industrial engineering firm, a JVM language called Gosu, a Rails startup, and the 2012 library Intercooler.js that he rewrote without jQuery during COVID and released as HTMX. His argument is that the web was built as a hypermedia system, that links and forms are control logic living inside the document, and that most of what we call REST today fails the one constraint Roy Fielding cared about. He also covers which apps HTMX is wrong for, what changed in HTMX 4 and why 3 was skipped, and why his students now sit pencil and paper exams. It is a conversation about using the browser as the hypermedia client it was built to be.
Señors @ Scale host Neciu Dan sits down with Ryan Townsend, Principal Product Manager for Performance at Cloudflare, where he owns real user monitoring and the wider performance measurement remit. Ryan has over 20 years in web technology and a decade as a CTO: he co-founded Shift Commerce, the first enterprise scale headless SaaS, and was CTO of Matalan Direct after the business he built came second in Shopify's Build a Business competition with only three months of trading. We cover why the 'Rails doesn't scale' story was always a myth, the resume driven development he kept finding as a fractional CTO, the personalization script that claimed zero performance impact and cost seconds at P90, and how Shift ran over 99% cache hit ratios by splitting the anonymous page from the basket.
Señors @ Scale host Neciu Dan sits down with Szymon Chudy, Software Engineer at Netflix on the Hawkins team, which builds the design system behind thousands of internal applications used to produce the shows you watch. Before Netflix, Szymon spent two and a half years at Lokalise, growing from senior to staff frontend engineer and leading frontend direction across teams, and before that he toured Poland as a reggae guitarist while freelancing as a web developer in the off season. From why the source of truth for a design system lives in code, to Hawkins Consumer versus Hawkins Professional, to the UI paved road that changes what freedom and responsibility mean at Netflix, to measuring the team on adoption rate and shipping codemods and agent skills for every breaking change, to what being an informed captain who farms for dissent means in practice, this is the design system conversation for anyone maintaining a platform other engineers have to choose to use.
Señors @ Scale host Neciu Dan sits down with Vilva Athiban, Lead AI Engineer at Omio, one of Europe's leading travel platforms, where he architects and ships agentic AI systems in production. Vilva designed and delivered Omio AI, along with the MCP integrations that connect AI agents to the company's systems. He never set out to switch from JavaScript to AI: in June 2024 Omio picked two people to start an AI team reporting to the CEO and CTO, and he learned on the job, from his first API call to an LLM up to a consumer-facing agent whose backend runs on nothing but MCP. From why a bigger model with medium thinking came out cheaper than the mini, to capping tool calls because LLMs are built for token maxing, to the whale hunting request that showed his team guardrails are subjective, this is a conversation about what production agentic systems look like once the tutorials run out.
📻 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.