Software Engineer - Data Platform
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We can include a short paragraph for "Who We Are" maybe as a
before sections. Not required to have heading. We'll include it as a
. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate. We'll create sections: - About the role:
About the role
thenwith the description. - Responsibilities:
Responsibilities
then- each bullet from "In this role, you will:" list.
- Requirements: maybe combine Minimum requirements and Ideal candidate? The instruction: Use sections Requirements, Qualifications, Skills. We have Minimum requirements (hard requirements) and Ideal candidate (preferred). Could map Minimum requirements to
Requirements
. Ideal candidate toQualifications
orSkills
. Since they are about experience/skills, we could put Ideal candidate underQualifications
. Or we could split: Requirements = minimum requirements; Qualifications = ideal candidate; Skills maybe not needed. But we should not create empty sections. We'll include Requirements and Qualifications. Skills maybe not needed if no specific skill list beyond those already covered. However we could treat the bullet list of ideal candidate as Skills. But we already have Qualifications. Let's decide: Use Requirements for minimum requirements, Qualifications for ideal candidate. No Skills section. - Benefits: we have Total Rewards paragraph and Flexible Working paragraph. Combine into Benefits section. - Pay: we have Annual Base Salary range. - Schedule: not specified; no schedule info. So we omit Schedule section. We must not include placeholder text like "commensurate with experience". Not present. We need to ensure we don't include boilerplate like "Flexible Working At Samsara, we embrace a flexible working model..." That's substantive about flexible working; we can keep as part of Benefits. We must not include EEO etc. So we will cut out Belonging at Samsara, Accommodations, Our Commitment to Authenticity, Fraudulent Employment Offers. Also remove "Who We Are" maybe keep as intro paragraph. Now craft HTML. We need to preserve all substantive information: ensure we keep details like "Samsara (NYSE: IOT) is the pioneer of the Connected Operations™ Cloud..." etc. Let's extract the Who We Are paragraph: "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." We'll keep that as a. Now About the role paragraph: "About the role: Samsara is looking for a Software Engineer to join our Data Platform team, which owns and develops the core analytical platform across Samsara. This team builds and maintains the infrastructure that powers Samsara’s data lake, distributed compute platform, and the systems that move data from our production data stores into our lakehouse. As a Software Engineer on Data Platform, you will design, build, and operate reliable, scalable, and secure infrastructure for ingesting, processing, cataloging, and accessing petabytes of data. You will work on the foundational systems that enable engineers, data scientists, analysts, and product teams across Samsara to build customer-facing features, train models, develop operational insights, and support the company’s long-term AI and analytics roadmap. This is a specialized software engineering role focused on data infrastructure. You will work on systems such as Spark and Databricks infrastructure, Delta Lake on S3, data replication from primary data stores such as RDS and DynamoDB, orchestration and metadata services, internal data libraries, and infrastructure tooling across the big data ecosystem. This role is not an analytics or business data engineering role. If your experience is primarily focused on SQL modeling, BI dashboards, ETL tools, or building business-facing data marts, this role is likely not the right fit. The ideal candidate is a software engineer with deep experience building and operating production data platforms, distributed systems, or large-scale ingestion infrastructure. This is a remote position open to candidates residing in the US. Relocation assistance will not be provided for this role." We'll put that in
. Responsibilities bullet list: - Design, build, and operate high-scale data ingestion and replication systems from Samsara’s primary production data stores, including RDS, DynamoDB, internal APIs, and event-driven systems, into our data lakehouse. - Build and maintain reliable, scalable, and modern data platform infrastructure capable of handling petabytes of data across Samsara’s analytics, AI, product, and operational use cases. - Improve the reliability, observability, scalability, security, and developer experience of Samsara’s Spark and Databricks-based data processing platform. - Develop internal libraries, APIs, frameworks, and tooling in languages such as Go and Python to help teams across Samsara move, process, discover, and access data safely and efficiently. - Work on foundational data lake and lakehouse technologies, including Delta Lake on S3, data catalogs, metadata services, orchestration systems, and platform automation. - Collaborate closely with infrastructure, product engineering, data science, analytics, security, and data engineering teams to understand platform needs and deliver durable, scalable solutions. - Stay connected to modern data platform technologies and help shape Samsara’s long-term data infrastructure roadmap, including support for AI, privacy, security, global scale, and customer-facing data products. - 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. Now Minimum requirements list: - 4+ years of professional software engineering experience in production environments. - 4+ years of experience building or maintaining large-scale production data infrastructure, data platforms, distributed systems, or data lake systems. - Strong experience with Apache Spark or similar distributed data processing systems. - Experience operating production infrastructure in AWS, including services such as S3, RDS, DynamoDB, SQS, Kinesis, Lambda, or similar. - Experience designing, building, and operating reliable systems with strong ownership of scalability, observability, security, and operational excellence. - Proficiency in at least one production programming language such as Go, Python, Scala, or Java. - Ability to collaborate effectively with cross-functional partners, including software engineers, data scientists, analysts, security teams, and product stakeholders. Now Ideal candidate list (Qualifications): - Experience with Databricks, Delta Lake, or similar lakehouse technologies such as Iceberg or Hudi. - Experience building data replication or ingestion systems from OLTP data stores into a data lake or lakehouse. - Experience with Infrastructure-as-Code tools such as Terraform or CloudFormation. - Familiarity with data catalogs, metadata systems, and data discovery tools such as Unity Catalog, Hive Metastore, DataHub, or Amundsen. - Experience with orchestration systems such as Airflow, Dagster, or Prefect. - Experience with streaming data, event-driven architectures, or systems that handle late-arriving or mutable data. - Familiarity with containerization or orchestration technologies such as Docker, Kubernetes, ECS, or Fargate. - Experience building internal platforms, libraries, or developer tooling used by other engineering teams. - Experience contributing to data infrastructure roadmaps, evaluating new technologies, and driving improvements that create leverage for internal and external customers. Now Benefits section: combine Total Rewards and Flexible Working paragraphs. Total Rewards paragraph: "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. If you’re ready to build for the long term and own the outcome, your journey starts here." Flexible Working paragraph: "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. All offers of employment are contingent upon an individual’s ability to secure and maintain the legal right to work at the company and in the specified work location, if applicable." We'll combine into Benefits
- maybe but it's prose; we can keep as
paragraphs. Pay section: Annual Base Salary $113,645—$191,000 USD. We'll put as
. Now ensure we don't include any boilerplate like "Learn more about our total rewards and benefits below." That's part of Total Rewards paragraph? Actually there is a line: "Learn more about our total rewards and benefits below." That's generic; we can keep? It's not substantive detail; maybe we should remove as it's just a reference. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Learn more about our total rewards and benefits below." is not boilerplate but maybe filler. Safer to remove it. We'll omit that sentence. Thus Benefits section will have two paragraphs: the Total Rewards (without the Learn more sentence) and Flexible Working. Now ensure