Solutions Integration Engineer IV
under About the role or as a separate short paragraph before sections. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location and citizenship as a short
after the About the role heading maybe. We must not repeat job title as heading. Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real content. We have content for About the role (the paragraph after "About the role:"). Responsibilities: the bullet list under "In this role, you will:" with many items. Requirements: "Minimum requirements for the role:" list. Qualifications: "An ideal candidate also has:" list. Skills: maybe not separate; we could combine with Requirements? But we have technical mastery etc. Could treat as Skills section. However we already have Requirements covering experience and technical mastery. The instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they are distinct: Minimum requirements vs Ideal candidate. Could make Requirements section for minimum, and Qualifications for ideal. Skills maybe not needed. Benefits: Total Rewards paragraph plus Flexible Working etc. Also maybe "Belonging at Samsara", "Accommodations", "Our Commitment to Authenticity", "Fraudulent Employment Offers" are boilerplate EEO etc. Should be removed. So we keep only substantive benefits: Total Rewards (compensation, bonus, equity, flexible remote model, professional development stipend, health and parental leave). Also Flexible Working description. Also maybe "Belonging at Samsara" is EEO boilerplate, remove. Accommodations maybe also boilerplate but it's about disability accommodation; could be considered benefit? It's more EEO. Likely remove. Our Commitment to Authenticity and Fraudulent Employment Offers also boilerplate. Remove. Pay: Annual Base Salary range. Schedule: Not present, so omit. We also need to include location and citizenship note as a short
maybe after About the role heading before Responsibilities. We must preserve all substantive information; do not invent or summarize away detail. Must not omit details like specific technologies, etc. We need to format lists with
- . For prose use
. We must not include markdown code fences. Let's craft. Structure:
About the role
[text from "About the role:" paragraph]
This is a remote position open to candidates residing in the US except the San Francisco Bay Metro Area, NYC Metro Area, and Washington, D.C. Metro Area. Because this role supports our Public Sector customer base, the candidate must be a US citizen.
Responsibilities
- System Integration & Architecture: Lead the development of enterprise-grade, scalable solutions, managing integrations involving internal teams, third-party integrators, or custom-built systems using various Samsara’s Web integration technologies (APIs, Webhooks, Connectors, and more.)
- End-to-End Technical Leadership: Take full ownership of high-impact, high-risk projects—from navigating ambiguous requirements and integration design through configuration, delivery, maintenance, and operational support. Comfortable making delivery commitments for larger projects
- Strategic Mentorship: Act as a technical lead, mentoring engineers to establish the foundational standards for robust, enterprise-level integrations.
- Cross-Functional Bridge: Serve as the vital link between Customers and Product/Engineering teams; relaying feedback to align product roadmaps with customer success and evolving market needs.
- Innovation & Stack Optimization: Leverage AI-driven workflows and modern technologies (Glean, Cursor etc.) to continually uplevel the team’s efficiency and technical stack.
- Operational Excellence & Visibility: Create customer facing launch plans and roadmaps, own and drive internal initiatives that enhance team visibility across the organization and improve operational efficiency through process automation.
- Champion, role model, and embed Samsara’s cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally and across new offices
- Leads by example: Build, Test, validate and review thorough code reviews and provides feedback that is actionable and insightful
- Exchange best practices, share knowledge with the Samsara product team, developer community, and advocate for customer experience
- Contribute to the enhancement of Professional Services methodologies and tools
Requirements
- Experience: 7+ years of professional experience as software engineer, solutions engineer, integrations engineer, solution architect or other customer facing technical roles.
- Experience in gathering data integration requirements and translating into good technical data designs
- Technical Mastery: Expert-level command of Python, REST APIs, and Webhooks; deep architectural knowledge of scalable, event-driven integration patterns using data streaming technologies (e.g., Kafka, PubSub) and data visualization tools (e.g., Power BI, Tableau).
- Data Management: Skilled at selecting appropriate data warehousing and storage strategies for a given use case, with hands-on experience across SQL and NoSQL databases, data modeling, and modern data pipeline tooling.
- Customer Engagement: A track record of deep customer engagement—building real relationships and turning complex requirements into winning technical solutions and running impactful training sessions to demonstrate Samsara’s technology.
- AI Driven Development and Automation: Proficient in leveraging LLM-based tools like Cursor and Codex and MCPs for code generation, prompt engineering, and enhancing developer workflows.
- Cloud Infrastructure: Experience developing highly scalable solutions leveraging modern Cloud Services (AWS, Azure, or GCP).
- Collaboration & Version Control: Proficient in using GitHub for version control and collaboration, and experienced working with Modern Agile tools (e.g., Jira, Confluence).
- Communication: Proven track record of building trust and communicating effectively with a wide variety of stakeholders: Executives, Product and Engineering leadership, day-to-day users of our software.
- Excellent consultative skills with experience in end to end system implementations
Qualifications
- Bachelors in Engineering, Computer Science, or related discipline
- Experience working in a high growth startup where you wore multiple hats and owned outcomes end-to-end.
- History of working on successful B2B enterprise products and working directly with large customers ($1M+ ARR/ACV).
- Consistent track record of configuring and deploying complex technical solutions
- Familiarity with B2B system integration projects and workflows
- Tinkering with hardware gadgets, sensors, or vehicles is a plus
- Familiarity with fleet management and maintenance workflows
Benefits
- Total Rewards: At Samsara, we build for the people who keep the global economy moving. We want owners, not passengers, which is why our rewards are designed to fuel high-impact builders. Our compensation program delivers above-market total compensation through a combination of base salary, performance-based bonus/variable pay, and equity (for eligible roles) in a high-growth public company. We meaningfully differentiate pay for our top performers, who have the opportunity to earn above-market compensation that can outpace the broader market over time. Beyond compensation, we provide the foundations that enable long-term success: a flexible, employee-led remote model, a professional development stipend, comprehensive health and parental leave plans, and more.
- Flexible Working: At Samsara, we embrace a flexible working model that caters to the diverse needs of our teams. Our offices are open for those who prefer to work in-person and we also support remote work where it aligns with our operational requirements. For certain positions, being close to one of our offices or within a specific geographic area is important to facilitate collaboration, access to resources, or alignment with our service regions. In these cases, the job description will clearly indicate any working location requirements. Our goal is to ensure that all members of our team can contribute effectively, whether they are working on-site, in a hybrid model, or fully remotely.
Pay
Annual Base Salary $105,910—$160,200 USD
We should not include Schedule. Check for any duplicated content: We have included all substantive info. Ensure we didn't include boilerplate like EEO etc. We removed those. Make sure we didn't miss any details: The "About the role" paragraph originally: "As a Solutions Integration Engineer at Samsara, you will be an integral member of the Professional Services Organisation responsible for helping Samsara’s most strategic customers build and implement B2B integrations with our IoT platform. In a given week, you may work with a large long-haul trucking company, an industrial-scale food producer, and a public utility to map a customer’s integration needs to current and future API capabilities, help building custom integrations, provide guidance and technical training to implementation teams to follow best practices, troubleshoot issues and advocate for fixes on behalf of customers (working with our tech support team), and ensure a successful customer relationship. A successful Solutions Integration Engineer at Samsara will develop a thorough understanding of B2B integrations to ensure the proper technical solution is delivered to our customers. Your role will be cross-functional, working alongside and connecting product managers, business operations, sales, and systems engineers, enabling you to experience multiple aspects of a hyper-growth company from within. Since Samsara is a fast-growing company with emerging IoT technology, you can expect this role to evolve, with opportunities to take on increasing levels of responsibility and impact our growth". We need to include that exactly. Let's copy. Also after that there is "You should apply if:" bullet points. Those are motivational statements; they could be considered part of About the role or maybe a separate section like "Who should apply". But we have no heading for that; we could incorporate them into About the role as amaybe. The instruction: preserve ALL substantive information. So we need to include those bullet points. They are under "You should apply if:" with four bullet points. We should include them as a list under About the role or maybe a separate section like "Who should apply". But we only allowed headings from list; we could add a section like "Who should apply" but not in allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. those). It might be okay to add other headings but better to stick to those. We could incorporate the "You should apply if