Urgent.News

What's breaking now, across thousands of outlets.

Tech

I read Buffer's engineering blog before applying. Here's what it taught me about the Senior Design Engineer role.

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…

The job seeker applied for Buffer's Senior Design Engineer role before writing any part of their application. They meticulously studied Buffer's engineering practices, starting with their engineering blog and accessibility statement. Buffer's engineers prioritize accessibility as an integral part of their design process, not as an afterthought.

They build accessibility features into their products from the very beginning, such as using aria-hidden for decorative elements and designing motion for prefers-reduced-motion users. This approach is unlike many other companies that prioritize visual appeal over accessibility.

Buffer's transparency and honesty about their accessibility efforts stood out to the job seeker. They openly disclose their partial compliance with WCAG 2.1 AA and publish an email address for accessibility feedback. This level of openness demonstrates a culture that values improvement and acknowledges ongoing work, rather than simply claiming to meet standards.

The job seeker also gained insight into what a design system is at Buffer. For them, it's not just a collection of UI components, but a contract between the engineer creating the component and every engineer who will use it. This contract ensures that using a component from Buffer's design system doesn't require the user to manually handle accessibility considerations like ARIA roles, focus states, or contrast ratios.

The Senior Design Engineer's role involves creating these contracts that make the right choices obvious and easy for all developers to follow. They should also ensure that compliance with accessibility standards is verified in the continuous integration pipeline and that they own prefer-reduced-motion at the token level, not just the component level.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

India’s Airbound bags $37M to take on trucks with rocket-like drones

Airbound's ultra-lightweight approach to drone delivery has attracted backing from Greenoaks, DoorDash, and Silicon Valley investor Lachy Groom.

  • Indian startup Airbound raises $37M in Series A funding.
  • TRT drone, weighing 3.3 lbs, will carry up to 11 lbs payload.
  • Startup aims for 10,000 daily drone flights in Andhra Pradesh.

Your coding agent shouldn't run pytest

First post in a build-in-public series about verdict , an MCP server that gives coding agents structured, sandboxed test feedback.

  • Coding agents run pytest unsandboxed, causing issues
  • Verdict replaces pytest with four tools: verify, explainfailure, history, runchecks
  • Each failure stored in SQLite db, tracks pre-change vs agent-introduced failures

My Validation Layer Was Correctly Deleting 16% of My Good Data

Originally published at ai.bedvibe.studio . I built a real-time tracker in Rust — about two thousand lines — that reads a live ADS-B feed, keeps a Kalman-filtered track per aircraft, and screens every…

  • 16% of valid data incorrectly discarded by validation layer
  • Lag between actual and filter timestamps causes issue
  • Fix advances Kalman filter validity with new measurements

Stop saying SSL: TLS only does three jobs, and your 'SSL cert' is usually not the outage

Runbooks still say "renew the SSL certificate" when the browser warning is obsolete protocol . The certificate can be brand new. The tunnel is still TLS 1.0. This is a shortened English note.

  • SSL and TLS are distinct protocols; SSL is outdated and vulnerable
  • TLS versions 1.2 or 1.3 are currently used by browsers
  • Three primary jobs of SSL/TLS handshake: confidentiality, integrity, authentication

More from Tuesday 25 August →