Frontend Engineer Contract

THE OPPORTUNITY:
We’re looking for a Frontend Engineer to join Brisk on a short-term contract (3 months) to drive a focused push on accessibility across our product. We’ve engaged an external accessibility audit firm to help us define accessibility priorities and their findings are landing now. We need a strong frontend engineer who can pick up that backlog, work through it methodically, and ship fixes that hold up under real screen reader and keyboard testing.

This is hands-on, high-leverage work. You’ll be deep in our React codebase and design system, fixing real issues that affect real teachers and students — including educators and learners who rely on assistive technology to do their jobs and learning every day. The Brisk Extension lives inside Google Docs, Slides, YouTube, Microsoft Word and PowerPoint online, and a growing list of other surfaces, so your work will touch the most visible parts of the product.

YOU WILL:
Work through the accessibility audit findings delivered by our external partner — triaging, prioritizing, and shipping fixes against a clear plan.
Remediate WCAG 2.1 AA issues across the Brisk Extension and our web app: semantic HTML, ARIA, keyboard navigation, focus management, color contrast, and screen reader support.
Partner closely with our design and engineering teams to upgrade components in the Brisk design system so accessibility is baked in for everything we ship after you leave.
Verify fixes the way real users would experience them — keyboard-only flows, NVDA and VoiceOver passes, and other automated tooling.
Pair with the audit firm to confirm remediations, close out tickets, and push back when their findings need clarification.
Document the patterns you put in place so the team can hold the line on accessibility after the engagement ends.
Use AI tools aggressively to move faster — for triage, refactors, generating test cases, and cutting through repetitive fix work without sacrificing quality.
YOU HAVE:

• Strong frontend engineering experience, with the bulk of it in React and TypeScript.
• A track record of shipping production UI work and a good eye for the small details that make components feel right.
• Comfort ramping quickly on accessibility — you don’t need to be a deep a11y specialist on day one, but you’ve worked with semantic HTML, ARIA, and keyboard interactions before, and you can get to expert quickly on the things this engagement requires.
• Experience working inside a design system or shared component library, and an instinct for fixing issues at the component level rather than patching them one screen at a time.
• Fluency with browser developer tools — accessibility tree, focus inspection, contrast checks, and the network/DOM tools you need to debug complex UI.
• Solid CSS and layout fundamentals — Flexbox, Grid, and responsive design without workarounds.
• A working AI-assisted workflow — you use Claude, Cursor, Copilot, or similar tools as a multiplier on your daily output, and you have a point of view on what they’re good and bad at.
• The ability to work independently on a focused scope, communicate clearly in writing, and hit weekly and monthly goals without hand-holding.

BONUS:

• Hands-on screen reader testing experience (NVDA, JAWS, VoiceOver).
• Familiarity with WCAG 2.1 AA or VPAT remediation work.
• Experience shipping browser extensions or working with content scripts and DOM integrations.
• Prior experience in edtech or building tools used directly by educators or students.