Loading this job…
Northwind Systems is hiring a product manager in Austin, TX. You will own a slice of the product with a small team, real customers and incomplete information. The job is deciding what not to build as much as what to build, and being able to explain both to the people affected.
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.
Expect customer conversations, writing that sharpens a fuzzy problem into a shippable one, and the metrics work that tells you whether the last thing helped. You will sit with engineering during build rather than reappearing at the demo. The team works a hybrid week out of Austin, TX, usually three days together and the rest wherever you work best.
This is a senior individual-contributor role. You will be expected to push back on requirements that do not make sense and to set the technical direction for your part of the product. We are looking for prioritisation under pressure, metrics literacy and the willingness to kill your own idea when the evidence says so. A technical background helps, but clear writing helps more.
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