Jobs / United States / Samsara INC
Senior Software Engineer II
Samsara INC · 🇺🇸 Remote - US · Remote
Sponsorship verdict
Sponsorship possible
One solid signal, not two — worth applying, and worth asking about sponsorship early.
- Employer is on a government sponsor recordThe US Department of Labor certified 47 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. USCIS also records 20 H-1B approvals in FY2023. Source: LCA disclosure data (US Department of Labor (OFLC)).
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- What Samsara INC paid sponsored hires in similar roles4 certified filings for “Sr. Quality Engineer I” (Software Quality Assurance Analysts and Testers) in CA: $138k–$187k, median $140k. Most were filed at wage level I (50%) — 1 lottery entry, ≈15% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).
- Confirmed live todayWhen a source last listed this job as open.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Sponsor Radar — Samsara INC
The US Department of Labor certified 47 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. USCIS also records 20 H-1B approvals in FY2023. Source: LCA disclosure data (US Department of Labor (OFLC)).
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for Samsara INC →
About the role
Who we are Samsara (NYSE: IOT) is the pioneer of the Connected Operations™ Cloud, which is a platform that enables organizations that depend on physical operations to harness Internet of Things (IoT) data to develop actionable insights and improve their operations. At Samsara, we are helping improve the safety, efficiency and sustainability of the physical operations that power our global economy. Representing more than 40% of global GDP, these industries are the infrastructure of our planet, including agriculture, construction, field services, transportation, and manufacturing — and we are excited to help digitally transform their operations at scale. Working at Samsara means you’ll help define the future of physical operations and be on a team that’s shaping an exciting array of product solutions, including Video-Based Safety, Vehicle Telematics, Apps and Driver Workflows, and Equipment Monitoring. As part of a recently public company, you’ll have the autonomy and support to make an impact as we build for the long term. About the role Join Samsara's In-Vehicle Experience team as a Senior Software Engineer. You'll be the technical leader of the team, setting the direction for what we build and how. We are building AI voice experiences that speak to, coach, and assist drivers as they work, spanning proactive assistance, on-demand interaction, and the range of situations in between. We are looking for the product-minded full-stack engineer who will figure out what those experiences should be, ship them, and build the systems that let them evolve into one coherent product rather than a set of disconnected tools. You'll design what agents say and how they behave, build the services that support them, and iterate on both based on what drivers actually experience. These systems sit at the intersection of software, AI, and the physical world. Because drivers interact with our products while operating a vehicle, decisions about what reaches them, and when, carry real weight. The systems underneath are where the hard-to-reverse decisions live. How agents share context, how concurrent interactions get arbitrated, and how the system's decisions can be explained after the fact. You'll decide what's worth building, and own the systems that make it possible. You'll ship against clear priorities from day one. We are looking for someone whose instinct is to shape the direction of the team's work, not just execute against it. Putting forward a point of view, making the case for it, and getting the team moving in a new direction is core to how this person operates. Engineers who habitually notice what should improve and then make it happen, rather than waiting to be told, will find this kind of role familiar. AI-assisted engineering is central to this role. You will be expected to use tools such as Codex, Claude Code, and Cursor proficiently throughout the software development lifecycle, not only for code generation but also for investigation, design, testing, review, and operational work. This is a remote position open to candidates residing in the US. In this role, you will: • Define what to build and how to build it, shaping product direction from the engineering side. • Build and ship voice agent experiences from zero to one in a fast-moving, ambiguous environment. Iterate quickly based on real interactions. • Own the technical direction for how these experiences coordinate: how they share context, how concurrent interactions get arbitrated, how the system holds up as more experiences are added, and how its real-time decisions can be investigated by the teams that need to. • Make and document architectural tradeoffs where requirements are still evolving, favoring foundations that generalize as new use cases emerge over one-off sol