> Markdown version of [/jobs/ext/4034753-senior-frontend-engineer-react](https://www.wearedevelopers.com/jobs/ext/4034753-senior-frontend-engineer-react). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Frontend Engineer - React

- **Company:** Voxquill LLC
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Salary:** $200,000.0 - $300,000.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Software Debugging, Document Object Model, Design of User Interfaces, Human-Computer Interaction, ReactJS, Front End Software Development, Virtual Agents
- **Published:** October 30, 2026
- **Apply:** https://www.careerbuilder.com/job-details/senior-frontend-engineer-react-san-francisco-ca--05a47d98-a4ed-43f3-a135-1607a33ea8ed

## About the Role

User Interface/Experience (UI/UX), Artificial Intelligence (AI), User Interface/Experience (UI/UX), Debugging Skills, DOM (Document Object Model), Writing Skills, Three to five years of professional frontend experience is the sweet spot.
Less is fine if your track record is exceptional.

A CS degree, or you've done real work at a company.
If you have none of the above, you'll have to prove strong technical skills and a solid foundation in the application and first interview.

Expert-level React. You should be able to explain what the virtual DOM is doing, when you'd reach for useMemo versus useRef, and why you structured state the way you did.

And you need to be able to write React without AI assistance. Use whatever you want in your day job, but the interviews are live, unassisted. For the technical interview.

## Description

Monday through Friday in the office in Bay Area, and Sunday remote. Sunday is mandatory, not optional, and some Sundays are not light.

 * There are no set hours. Nobody tracks when you arrive or leave. They treat people like adults and care about whether the work is done. But the schedule is the schedule, and we'd rather you close this tab now than find out at the final round.

If that's a dealbreaker, no hard feelings. If it sounds like the kind of stretch you've been looking for, keep reading.

What you'd actually do

React, React, React. This is a React-heavy role, and they mean it literally! The first two interviews are hands-on React coding.

You'd own features end to end. Someone tells you a customer can't debug their agent's transcripts, and it's on you to decide what gets built, architect it, ship it, and see whether it worked. You'd make frontend architecture calls that stick, in a codebase young enough that they matter.

You'd report directly to the CTO, who is also a co-founder. No layer in between, and none planned.