Loading this job…
Northwind Systems is hiring a frontend developer in San Francisco, CA. Frontend here means everything a user actually touches: layout, interaction, accessibility and how fast the first useful pixel arrives. It is measured work — we watch real-user metrics, not a lab score from a fast laptop on office wifi.
The US market for this role is deep and well paid, and candidates rightly compare offers carefully. The band below is the real band — we do not hold a number back for whoever negotiates hardest.
You will build and maintain the interfaces our customers spend their working day inside, work through interaction detail with design rather than receiving it finished, and keep the bundle and the render cost inside an agreed budget release after release. Accessibility is part of the definition of done, not a later audit. The team works a hybrid week out of San Francisco, CA, usually three days together and the rest wherever you work best.
This is a lead role. Alongside hands-on work you will shape the direction of your area, mentor two or three engineers and represent the team in planning. Strong HTML and CSS still beat framework trivia in this loop. We are looking for someone who reaches for a semantic element before a div, knows what a screen reader does with their markup, and can tell you what actually made a page slow.
Core hours are set by the team rather than by the company, and we are deliberate about protecting long stretches of focus time. The range shown is the annual gross salary band for this role.
Northwind Systems builds the deployment and rollback tooling that sits between a merged pull request and a running service. Around four thousand engineering teams use it, and roughly a third of them have never spoken to a salesperson — they found the CLI, tried it and expensed it.
Because our users are engineers, the bar for the product is unusually literal: an error message that is vague gets filed as a bug, and a documentation page that is wrong gets a pull request within the hour. We treat both as the compliment they are.
The company is headquartered in San Francisco with engineering hubs in Austin and Toronto, and about half of the team is remote across North America.




Read these before you send your application.
A practical, India-specific guide to writing a fresher resume that survives the first screen: structure, projects, keywords and the mistakes that get CVs rejected in ten seconds.
4 min read · 21 Aug 2026
What actually works when applying for remote roles from India: which companies genuinely hire remotely, how to handle timezones and payment, and how to make a remote-ready application.
4 min read · 16 Aug 2026
The React interview questions that actually come up in Indian hiring loops, what a strong answer sounds like, and how the bar shifts between junior, mid and senior rounds.
3 min read · 9 Aug 2026