Data Engineer - West Region
Slalom · Seattle, WA · 3 wk ago
Information Technology$100k–$125k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes sections: "Who You’ll Work With", "What You’ll Do", "What You’ll Bring", "Additional Experience That May Be Helpful", "About Us", "Compensation and Benefits". Also maybe "Hybrid/In office" part. We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should map content to appropriate headings. The instruction: "use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should map content to appropriate headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings if content matches. However we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings where applicable. We need to include a section only when posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- About the role: could be the introductory description? The posting starts with description of Slalom and then "Who You’ll Work With". Might treat "About the role" as summary of role? Could combine "Who You’ll Work With" and "What You’ll Do" as About the role? But we need to follow instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Thus we need to map:
- About the role: maybe a brief paragraph summarizing the role (Data Engineer at Slalom). Could use the first paragraph after "Who You’ll Work With"? Actually "Who You’ll Work With" is about team. Could be part of About the role.
- Responsibilities: corresponds to "What You’ll Do". Use Responsibilities
with list.
- Requirements: maybe "What You’ll Bring" (mandatory). Use Requirements
with list.
- Qualifications: maybe "Additional Experience That May Be Helpful" could be Qualifications? Or Skills? Actually "Qualifications" could be the required qualifications. But we already used Requirements for mandatory. Could treat Qualifications as "Additional Experience That May Be Helpful". Or Skills as specific technical skills list.
- Benefits: we have compensation and benefits details. Use Benefits
with list.
- Pay: we have salary ranges. Use Pay
with paragraph.
- Schedule: we have hybrid/In office info. Use Schedule
with paragraph.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, accommodations, application instructions, etc. Also remove duplicated lines.
We must preserve all substantive information.
Let's extract content.
First, intro paragraph: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries collaborate with clients to bring powerful customer experiences, innovative ways of working, and new products and services to life. We are trusted by leaders across the Global 1000, many successful enterprise and mid-market companies, and 500+ public sector organizations to improve operations, drive growth, and create value. At Slalom, we believe that together, we can move faster, dream bigger, and build better tomorrows for all."
That's about company, could be part of About the role? Might be okay.
Then "Who You’ll Work With" paragraph: "At Slalom, we co-create custom software, data, AI, and cloud solutions with clients who are ready to accelerate their digital transformation. We are passionate about technology and its potential to create better products, experiences, and organizations. Our Data Architecture & Engineering team sees data as the foundation for decision-making, artificial intelligence, and transformation. You may work with cross-platform data engineering teams or with one of our centers of excellence that specializes in a particular ecosystem. Slalom works across Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), Databricks, and Snowflake, along with the technologies that support each platform. Expertise across every platform is not required. Your current skills, delivery experience, and areas of interest will help determine which team and client opportunities are the best fit, while giving you room to expand your capabilities over time."
That's about team.
Then "What You’ll Do" with bullet list (actually colon then list). We'll convert to - .
List items:
- Designing and implementing cloud-native data platforms, data lakes, lakehouses, warehouses, and data products.
- Building reliable batch and streaming data pipelines, integrations, and orchestration workflows.
- Translating business and technical requirements into maintainable engineering solutions and actionable development tasks.
- Developing solutions across AWS, Azure, GCP, Databricks, and Snowflake ecosystems based on client needs and your areas of expertise.
- Applying software engineering practices such as version control, automated testing, CI/CD, infrastructure as code, observability, documentation, and secure development.
- Using AI-enabled engineering approaches and tools to improve delivery speed, quality, testing, documentation, and maintainability, with appropriate human review and responsible use.
- Designing, building, and operationalizing governed data platforms that support analytics, AI, machine learning, Generative AI, and agentic workloads.
- Enabling data quality, metadata, lineage, security, privacy, governance, performance, reliability, and cost-effective operations.
- Participating in technical discovery, design sessions, code reviews, demonstrations, and knowledge sharing with clients and colleagues.
- Contributing to reusable patterns, accelerators, and engineering communities within Slalom.
Then "What You’ll Bring": list of mandatory qualifications.
Paragraph intro: "We welcome candidates with different combinations of experience. You do not need every skill listed below to be successful in this role. We are interested in the depth of your experience, your learning mindset, and the areas where you want to grow."
Then bullet list:
- Hands-on experience designing, building, testing, deploying, or supporting production data engineering solutions.
- Experience with at least one major cloud or data platform, such as AWS, Azure, GCP, Databricks, or Snowflake. Experience across multiple platforms is valued but not required.
- Proficiency in programming languages such as SQL, Python, Java and or Scala.
- Experience with several modern data engineering capabilities, such as data modeling, ETL/ELT, distributed processing, lakehouse architectures, streaming, APIs, orchestration, or data platform modernization.
- Familiarity with relevant technologies, which may include Spark, Kafka, Airflow, dbt, Dagster, Azure Data Factory, BigQuery, Redshift, Synapse, Microsoft Fabric, Delta Lake, Unity Catalog, Dataplex, Dataflow, Pub/Sub, Kinesis, Kubernetes, Terraform, or comparable tools.
- Understanding of how high-quality, secure, governed, and observable data foundations support AI, ML, Generative AI, retrieval-augmented generation, and agentic solutions.
- Experience with AI-enabled or agentic engineering practices, including using AI-assisted development tools and designing data workflows or platforms that can support intelligent agents and automated decision workflows.
- A commitment to responsible engineering, including privacy, security, transparency, testing, monitoring, and appropriate human oversight for AI-enabled solutions.
- Strong problem-solving, communication, and collaboration skills, with an ability to explain technical concepts to different audiences.
- A curious, growth-oriented mindset and willingness to learn new platforms, tools, and delivery approaches.
Then "Additional Experience That May Be Helpful": bullet list:
- Cloud, Databricks, or Snowflake certifications.
- Experience in consulting or in client-facing, cross-functional delivery teams.
- Experience with MLOps, LLMOps, vector databases, model or prompt monitoring, feature stores, semantic layers, or AI platform operations.
- Experience modernizing legacy data environments or migrating workloads to cloud platforms.
- Experience mentoring others or contributing to technical communities and reusable assets.
Then "About Us": repeats similar intro but slightly different: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days."
Then "Hybrid/In office: We are hybrid and require that you live within a commutable distance to a Slalom location. If your team leader or client requires you to be onsite, there are expectations that you can meet those requirements."
Then "Compensation and Benefits": paragraph about benefits then salary ranges.
Benefits list: "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance."
Then Pay: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and locations at the targeted base pay salary ranges share below. Los Angeles, Orange County, Seattle Consultant: $100,000 - $125,000 All other locations: Consultant: $91,000 - $115,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applications until September 30th or the position is filled. We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose."
We need to remove application instructions (the contact email maybe considered application instruction? It's about pay range questions; but it's still contact. The instruction says remove application instructions. The email is for pay range questions, not application. Might be okay to keep? Safer to remove that line? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The email is not exactly application instruction but could be considered contact for pay questions; maybe keep as part of Pay section? It's not application instruction. I'd keep it as part of Pay section but maybe remove the sentence about contacting for pay range? It's not application instruction but still contact. I'd keep it as it's relevant to pay transparency. However the instruction says remove application instructions; this is not about applying but about pay questions. I'd keep.
Now we need to output HTML fragment only.
We'll structure:
About the role
... combine intro and Who You’ll Work With? Might be too much. Could split: About the role could be the introductory description of Slalom and the role context. Who You’ll Work With could be part of About the role? But we have separate headings for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We might not need About the role if we already have Responsibilities etc. But we need to include sections only when posting has real content. We have content for Responsibilities, Requirements (What You’ll Bring), Qualifications (Additional Experience), Skills (
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings where applicable. We need to include a section only when posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- About the role: could be the introductory description? The posting starts with description of Slalom and then "Who You’ll Work With". Might treat "About the role" as summary of role? Could combine "Who You’ll Work With" and "What You’ll Do" as About the role? But we need to follow instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Thus we need to map:
- About the role: maybe a brief paragraph summarizing the role (Data Engineer at Slalom). Could use the first paragraph after "Who You’ll Work With"? Actually "Who You’ll Work With" is about team. Could be part of About the role.
- Responsibilities: corresponds to "What You’ll Do". Use Responsibilities
with list.
- Requirements: maybe "What You’ll Bring" (mandatory). Use Requirements
with list.
- Qualifications: maybe "Additional Experience That May Be Helpful" could be Qualifications? Or Skills? Actually "Qualifications" could be the required qualifications. But we already used Requirements for mandatory. Could treat Qualifications as "Additional Experience That May Be Helpful". Or Skills as specific technical skills list.
- Benefits: we have compensation and benefits details. Use Benefits
with list.
- Pay: we have salary ranges. Use Pay
with paragraph.
- Schedule: we have hybrid/In office info. Use Schedule
with paragraph.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, accommodations, application instructions, etc. Also remove duplicated lines.
We must preserve all substantive information.
Let's extract content.
First, intro paragraph: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries collaborate with clients to bring powerful customer experiences, innovative ways of working, and new products and services to life. We are trusted by leaders across the Global 1000, many successful enterprise and mid-market companies, and 500+ public sector organizations to improve operations, drive growth, and create value. At Slalom, we believe that together, we can move faster, dream bigger, and build better tomorrows for all."
That's about company, could be part of About the role? Might be okay.
Then "Who You’ll Work With" paragraph: "At Slalom, we co-create custom software, data, AI, and cloud solutions with clients who are ready to accelerate their digital transformation. We are passionate about technology and its potential to create better products, experiences, and organizations. Our Data Architecture & Engineering team sees data as the foundation for decision-making, artificial intelligence, and transformation. You may work with cross-platform data engineering teams or with one of our centers of excellence that specializes in a particular ecosystem. Slalom works across Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), Databricks, and Snowflake, along with the technologies that support each platform. Expertise across every platform is not required. Your current skills, delivery experience, and areas of interest will help determine which team and client opportunities are the best fit, while giving you room to expand your capabilities over time."
That's about team.
Then "What You’ll Do" with bullet list (actually colon then list). We'll convert to - .
List items:
- Designing and implementing cloud-native data platforms, data lakes, lakehouses, warehouses, and data products.
- Building reliable batch and streaming data pipelines, integrations, and orchestration workflows.
- Translating business and technical requirements into maintainable engineering solutions and actionable development tasks.
- Developing solutions across AWS, Azure, GCP, Databricks, and Snowflake ecosystems based on client needs and your areas of expertise.
- Applying software engineering practices such as version control, automated testing, CI/CD, infrastructure as code, observability, documentation, and secure development.
- Using AI-enabled engineering approaches and tools to improve delivery speed, quality, testing, documentation, and maintainability, with appropriate human review and responsible use.
- Designing, building, and operationalizing governed data platforms that support analytics, AI, machine learning, Generative AI, and agentic workloads.
- Enabling data quality, metadata, lineage, security, privacy, governance, performance, reliability, and cost-effective operations.
- Participating in technical discovery, design sessions, code reviews, demonstrations, and knowledge sharing with clients and colleagues.
- Contributing to reusable patterns, accelerators, and engineering communities within Slalom.
Then "What You’ll Bring": list of mandatory qualifications.
Paragraph intro: "We welcome candidates with different combinations of experience. You do not need every skill listed below to be successful in this role. We are interested in the depth of your experience, your learning mindset, and the areas where you want to grow."
Then bullet list:
- Hands-on experience designing, building, testing, deploying, or supporting production data engineering solutions.
- Experience with at least one major cloud or data platform, such as AWS, Azure, GCP, Databricks, or Snowflake. Experience across multiple platforms is valued but not required.
- Proficiency in programming languages such as SQL, Python, Java and or Scala.
- Experience with several modern data engineering capabilities, such as data modeling, ETL/ELT, distributed processing, lakehouse architectures, streaming, APIs, orchestration, or data platform modernization.
- Familiarity with relevant technologies, which may include Spark, Kafka, Airflow, dbt, Dagster, Azure Data Factory, BigQuery, Redshift, Synapse, Microsoft Fabric, Delta Lake, Unity Catalog, Dataplex, Dataflow, Pub/Sub, Kinesis, Kubernetes, Terraform, or comparable tools.
- Understanding of how high-quality, secure, governed, and observable data foundations support AI, ML, Generative AI, retrieval-augmented generation, and agentic solutions.
- Experience with AI-enabled or agentic engineering practices, including using AI-assisted development tools and designing data workflows or platforms that can support intelligent agents and automated decision workflows.
- A commitment to responsible engineering, including privacy, security, transparency, testing, monitoring, and appropriate human oversight for AI-enabled solutions.
- Strong problem-solving, communication, and collaboration skills, with an ability to explain technical concepts to different audiences.
- A curious, growth-oriented mindset and willingness to learn new platforms, tools, and delivery approaches.
Then "Additional Experience That May Be Helpful": bullet list:
- Cloud, Databricks, or Snowflake certifications.
- Experience in consulting or in client-facing, cross-functional delivery teams.
- Experience with MLOps, LLMOps, vector databases, model or prompt monitoring, feature stores, semantic layers, or AI platform operations.
- Experience modernizing legacy data environments or migrating workloads to cloud platforms.
- Experience mentoring others or contributing to technical communities and reusable assets.
Then "About Us": repeats similar intro but slightly different: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days."
Then "Hybrid/In office: We are hybrid and require that you live within a commutable distance to a Slalom location. If your team leader or client requires you to be onsite, there are expectations that you can meet those requirements."
Then "Compensation and Benefits": paragraph about benefits then salary ranges.
Benefits list: "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance."
Then Pay: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and locations at the targeted base pay salary ranges share below. Los Angeles, Orange County, Seattle Consultant: $100,000 - $125,000 All other locations: Consultant: $91,000 - $115,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applications until September 30th or the position is filled. We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose."
We need to remove application instructions (the contact email maybe considered application instruction? It's about pay range questions; but it's still contact. The instruction says remove application instructions. The email is for pay range questions, not application. Might be okay to keep? Safer to remove that line? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The email is not exactly application instruction but could be considered contact for pay questions; maybe keep as part of Pay section? It's not application instruction. I'd keep it as part of Pay section but maybe remove the sentence about contacting for pay range? It's not application instruction but still contact. I'd keep it as it's relevant to pay transparency. However the instruction says remove application instructions; this is not about applying but about pay questions. I'd keep.
Now we need to output HTML fragment only.
We'll structure:
About the role
... combine intro and Who You’ll Work With? Might be too much. Could split: About the role could be the introductory description of Slalom and the role context. Who You’ll Work With could be part of About the role? But we have separate headings for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We might not need About the role if we already have Responsibilities etc. But we need to include sections only when posting has real content. We have content for Responsibilities, Requirements (What You’ll Bring), Qualifications (Additional Experience), Skills (
About the role
... combine intro and Who You’ll Work With? Might be too much. Could split: About the role could be the introductory description of Slalom and the role context. Who You’ll Work With could be part of About the role? But we have separate headings for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We might not need About the role if we already have Responsibilities etc. But we need to include sections only when posting has real content. We have content for Responsibilities, Requirements (What You’ll Bring), Qualifications (Additional Experience), Skills (