Senior Frontend Engineer · Accessibility
I build interfaces everyone can use.
Eight years of frontend: WCAG AAA at Drift, and today leading SITIMM's web, app and admin panel with teams of AI agents.
Open to senior frontend and full-stack roles · Remote, UTC−6
Now
Leading SITIMM's platform, the web, app and admin panel for a union of 70,000 members, with teams of AI agents: 5 repos and 8,790 commits since May 2025.
Selected work
-

SITIMM: web, app and admin panel
A union's public platform for 70,000 members, rebuilt and run by AI agent teams I direct: the website, an app on both stores and the panel behind them.
-

Making accessibility hard to break
Nine failures on sitimm.org, the WCAG criterion behind each one, the fix, and the checks that keep it fixed when AI agents write the code.
-

Teaching an assistant to find the right answer
An outage on a Saturday, and by Sunday the app's assistant searched everything the union publishes, inside the Postgres it already had.
-
Accessibility at Drift
Frontend held to WCAG AAA across the platform, and the go-to engineer for high-priority bugs.
What SITIMM taught me
A year as the only engineer on a platform for 70,000 union members. These changed how I build.
-
Meet people where they already publish.
The comms team already posted every notice to a WhatsApp channel, so the CMS was a second, manual job. Now a bot reads the channel, AI drafts the post in 8 languages, and an admin approves it from email or WhatsApp.
-
Nobody wants a ticket. They want an answer.
Members didn't get how a ticket queue works; they wanted results right away. Consultations became a conversation, and SitimmVito, the app's assistant, answers from the union's own documents in seconds.
-
Approving should take one click.
A new magazine used to wait for approval before its page and promo video were even made. Now everything is built the moment the issue is detected; approving only makes it official.
-
Show people it saved.
Autosave felt modern to me. The admins, who aren't technical, didn't trust it. A clear “Save changes” button, visible states and a success message fixed that.
-
“Sent” is not “delivered”.
The server counted every notification as sent. When I measured, almost no phones were subscribed. Now each notice shows how many people could get it, received it and opened it.
-
Unused isn't unneeded.
I proposed removing features with zero usage. The client stopped me: the panel was new, so zero measured adoption, not need. Broken things get fixed, not deleted.
Experience
- 2025–SITIMMLead engineer, AI agent teams
- 2022–25DriftSenior Frontend Developer
- 2019–22SITIMMFrontend Developer
- 2018–19RemoteFrontend Developer
- 2017MagmaLabsJunior Frontend Developer
Let's talk
I'm looking for a senior frontend or full-stack role where accessibility matters. Email is the fastest way to reach me.