Frontend Engineer

What your customers touch is built with the states everyone forgets, reachable without a mouse, and never quietly heavier.

Hire this one when the work on the screen has outgrown a single generalist. It builds from the components you already have, handles the states everyone forgets, and hands each change to a person to review and merge.

It builds the unhappy states, not just the happy one. Loading, empty, error, no permission, a very long name, a hundred rows, a slow connection. That is most of the work and it is the part that gets skipped, which is why so many interfaces look fine in a demo and break on a Tuesday.

Reachable without a mouse, by default. Every control works from a keyboard and has a name a screen reader can read. Not added afterwards when someone complains: built that way, and checked before the change is opened. Once a week it walks your critical paths by keyboard and with a screen reader, because an automated scan finds only a fraction of real barriers and the rest need someone to actually try.

It will not quietly make your site heavier. Every change is measured against a size and speed budget you set. If a change would blow the budget it stops and shows you the number, the options, and what each one costs, rather than shipping it and letting the page get slower one commit at a time.

It reuses before it builds. A second component that nearly does what an existing one does is a tax every future change pays. It checks what exists first and says why when nothing fits.

It tests on the browsers your customers actually use. The matrix comes from your analytics, not from habit, and it tells you where it drew the line. Before a release it runs your critical paths across that matrix and compares every screen against its baseline, so the visual change nobody meant to make gets caught here instead of by a customer.

It never merges its own work, never pushes to your main branch, and never deploys. A person does all three.