Senior Principal, Data Architecture and Engineering
Slalom · Seattle, WA · 1 mo ago
Engineering$194k–$215k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Job Title: Senior Principal, Data Architecture & Engineering
Content sections:
- Who You’ll Work With (description)
- What You’ll Do (responsibilities)
- What You’ll Bring (requirements/qualifications/skills)
- About Us (company description)
- Compensation and Benefits (pay and benefits)
- EEO and Accommodations (boilerplate to remove)
- Also there is "Slalom is a fiercely human..." repeated at start and later "About Us" similar.
We need to produce sections: maybe About the role (intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
But we need to map content.
We have description of role: "Who You’ll Work With" and "What You’ll Do". Could combine into About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content.
We have:
- About the role: could be the introductory paragraph about Slalom and the team? The posting starts with "Slalom is a fiercely human business..." then "Job Title: Senior Principal, Data Architecture & Engineering". Then "Who You’ll Work With". That could be considered About the role.
- Responsibilities: "What You’ll Do" section.
- Requirements: maybe "What You’ll Bring" includes skills, experience, etc. Could be Requirements and Qualifications and Skills.
We need to split into Requirements, Qualifications, Skills maybe. But we can combine if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits, Pay. No Schedule because not mentioned.
We must not create sections with filler like "commensurate with experience". So we need actual content.
Let's extract substantive content.
First, introductory 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 the company, could be About the role? Might be better as About the role (company context). Then "Who You’ll Work With" paragraph: describes team, platforms, etc.
We could combine both into About the role.
Responsibilities: "What You’ll Do" paragraph(s). Let's extract:
"Slalom’s Data Architecture & Engineering team is comprised of passionate, flexible technologists who love to practice and hone their craft. As tools evolve and technologies emerge, we work to stay in front of innovations in data platform development and delivery, working with some of the most forward-thinking organizations in data and analytics. As a Senior Principal for Slalom, you will design and deliver innovative solutions on Amazon Web Services, Microsoft Azure, and Google Cloud Platform using core cloud data warehouse tools, distributed processing engines, event streaming platforms, and other modern data technologies. In addition to building the next generation of data platforms, you will be working with some of the most forward-thinking organizations in data and analytics. This includes working closely with other Slalom teams to meet with prospective clients, discuss their needs and shape projects into a team-based delivery model. You will be responsible for leading the analysis, architecture, design, and development of cloud data warehouse and analytics solutions including defining the cloud data strategy and multi-phased implementation roadmap for your clients. You will have the opportunity to assist business development teams with pre-sales activities, including helping estimate and plan projects and be expected to actively contribute to the cloud and big data community at Slalom, and drive new capabilities forward."
That's responsibilities.
Requirements/Qualifications/Skills: "What You’ll Bring" paragraph(s). Let's extract:
"As a Senior Principal in the Data Architecture & Engineering team, you will bring a curious mindset to your client’s engagement, a thirst for knowledge and a hunger for fearless experimentation in new and interesting ways to meet our clients’ most pressing data challenges. You are self-starter, effective in breaking down large problems into smaller ones, and eager to regularly share what you learn with others within your projects and in the broader Slalom Build community. You are skilled at leading and growing direct reports. You will have an insatiable need to become the best at what you do and have hands-on experience with data platforms, migrating data to cloud platforms, and programming languages as you explore the range of technologies we help our clients with, including: Big Data Platforms (Apache Spark, Presto, Amazon EMR) Cloud Data Warehouses (Amazon Redshift, Snowflake, Google BigQuery, Databricks) Object-Oriented Coding (Java, Python) NoSQL Databases (DynamoDB, Cosmos DB, MongoDB) Container Management Systems (Kubernetes, Amazon ECS) Artificial Intelligence / Machine Learning (Amazon Sagemaker, Azure ML Studio) Streaming Data Ingestion and Analytics (Amazon Kinesis, Apache Kafka) Modern Data Workflows (Apache Airflow, dbt, Dagster)."
That's qualifications/skills.
Benefits and Pay: "Compensation and Benefits" section.
Extract:
"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. Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the Sr. Principal level. The targeted base pay range for these locations is $194,000 - $215,000 the following levels and targeted base pay salary ranges. 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 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 separate Pay and Benefits sections if possible. The posting lumps them together. We could create Benefits section with benefits list, and Pay section with pay range and bonus info.
Benefits list: 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, short/long-term disability, yearly $350 reimbursement account for any well-being-related expenses, discounted home, auto, and pet insurance.
Pay: targeted base pay range $194,000 - $215,000, annual discretionary bonus, note about dependence on skills etc.
We should not include contact email? It's part of compensation info but maybe we can keep as part of Pay section? It's not boilerplate? It's contact for pay questions. Might be okay to keep.
We must not include EEO and Accommodations (boilerplate). Remove.
Also remove duplicated lines like "Slalom is a fiercely human..." appears twice (intro and About Us). We should keep only once.
Also remove "About Us" section which repeats similar content; we can drop it as duplicate.
Now produce HTML fragment with headings
for each heading. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Job Title: Senior Principal, Data Architecture & Engineering
Content sections:
- Who You’ll Work With (description)
- What You’ll Do (responsibilities)
- What You’ll Bring (requirements/qualifications/skills)
- About Us (company description)
- Compensation and Benefits (pay and benefits)
- EEO and Accommodations (boilerplate to remove)
- Also there is "Slalom is a fiercely human..." repeated at start and later "About Us" similar.
We need to produce sections: maybe About the role (intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
But we need to map content.
We have description of role: "Who You’ll Work With" and "What You’ll Do". Could combine into About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content.
We have:
- About the role: could be the introductory paragraph about Slalom and the team? The posting starts with "Slalom is a fiercely human business..." then "Job Title: Senior Principal, Data Architecture & Engineering". Then "Who You’ll Work With". That could be considered About the role.
- Responsibilities: "What You’ll Do" section.
- Requirements: maybe "What You’ll Bring" includes skills, experience, etc. Could be Requirements and Qualifications and Skills.
We need to split into Requirements, Qualifications, Skills maybe. But we can combine if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits, Pay. No Schedule because not mentioned.
We must not create sections with filler like "commensurate with experience". So we need actual content.
Let's extract substantive content.
First, introductory 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 the company, could be About the role? Might be better as About the role (company context). Then "Who You’ll Work With" paragraph: describes team, platforms, etc.
We could combine both into About the role.
Responsibilities: "What You’ll Do" paragraph(s). Let's extract:
"Slalom’s Data Architecture & Engineering team is comprised of passionate, flexible technologists who love to practice and hone their craft. As tools evolve and technologies emerge, we work to stay in front of innovations in data platform development and delivery, working with some of the most forward-thinking organizations in data and analytics. As a Senior Principal for Slalom, you will design and deliver innovative solutions on Amazon Web Services, Microsoft Azure, and Google Cloud Platform using core cloud data warehouse tools, distributed processing engines, event streaming platforms, and other modern data technologies. In addition to building the next generation of data platforms, you will be working with some of the most forward-thinking organizations in data and analytics. This includes working closely with other Slalom teams to meet with prospective clients, discuss their needs and shape projects into a team-based delivery model. You will be responsible for leading the analysis, architecture, design, and development of cloud data warehouse and analytics solutions including defining the cloud data strategy and multi-phased implementation roadmap for your clients. You will have the opportunity to assist business development teams with pre-sales activities, including helping estimate and plan projects and be expected to actively contribute to the cloud and big data community at Slalom, and drive new capabilities forward."
That's responsibilities.
Requirements/Qualifications/Skills: "What You’ll Bring" paragraph(s). Let's extract:
"As a Senior Principal in the Data Architecture & Engineering team, you will bring a curious mindset to your client’s engagement, a thirst for knowledge and a hunger for fearless experimentation in new and interesting ways to meet our clients’ most pressing data challenges. You are self-starter, effective in breaking down large problems into smaller ones, and eager to regularly share what you learn with others within your projects and in the broader Slalom Build community. You are skilled at leading and growing direct reports. You will have an insatiable need to become the best at what you do and have hands-on experience with data platforms, migrating data to cloud platforms, and programming languages as you explore the range of technologies we help our clients with, including: Big Data Platforms (Apache Spark, Presto, Amazon EMR) Cloud Data Warehouses (Amazon Redshift, Snowflake, Google BigQuery, Databricks) Object-Oriented Coding (Java, Python) NoSQL Databases (DynamoDB, Cosmos DB, MongoDB) Container Management Systems (Kubernetes, Amazon ECS) Artificial Intelligence / Machine Learning (Amazon Sagemaker, Azure ML Studio) Streaming Data Ingestion and Analytics (Amazon Kinesis, Apache Kafka) Modern Data Workflows (Apache Airflow, dbt, Dagster)."
That's qualifications/skills.
Benefits and Pay: "Compensation and Benefits" section.
Extract:
"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. Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the Sr. Principal level. The targeted base pay range for these locations is $194,000 - $215,000 the following levels and targeted base pay salary ranges. 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 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 separate Pay and Benefits sections if possible. The posting lumps them together. We could create Benefits section with benefits list, and Pay section with pay range and bonus info.
Benefits list: 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, short/long-term disability, yearly $350 reimbursement account for any well-being-related expenses, discounted home, auto, and pet insurance.
Pay: targeted base pay range $194,000 - $215,000, annual discretionary bonus, note about dependence on skills etc.
We should not include contact email? It's part of compensation info but maybe we can keep as part of Pay section? It's not boilerplate? It's contact for pay questions. Might be okay to keep.
We must not include EEO and Accommodations (boilerplate). Remove.
Also remove duplicated lines like "Slalom is a fiercely human..." appears twice (intro and About Us). We should keep only once.
Also remove "About Us" section which repeats similar content; we can drop it as duplicate.
Now produce HTML fragment with headings and content in
or
- . We need to decide sections: - About the role (intro + Who You’ll Work With) - Responsibilities (What You’ll Do) - Requirements (What You’ll Bring) maybe combine qualifications and skills. - Benefits (list) - Pay (range and bonus) No Schedule. We must not repeat job title as heading. Let's craft. About the role: combine company intro and Who You’ll Work With. Company intro: "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." Who You’ll Work With: "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." We can put that as a paragraph. Responsibilities: as above. Requirements: we could list bullet points for skills/experience. The "What You’ll Bring" includes mindset traits and then a list of technologies. We could break into two paragraphs: mindset and experience, then a ul of tech stacks. Let's extract mindset paragraph: "As a Senior Principal in the Data Architecture & Engineering team, you will bring a curious mindset to your client’s engagement, a thirst for knowledge and a hunger for fearless experimentation in new and interesting ways to meet our clients’ most pressing data challenges. You are self-starter, effective in breaking down large problems into smaller ones, and eager to regularly share what you learn with others within your projects and in the broader Slalom Build community. You are skilled at leading and growing direct reports. You will have an insatiable need to become the best at what you do and have hands-on experience with data platforms, migrating data to cloud platforms, and programming languages as you explore the range of technologies we help our clients with, including:" Then list. We'll create ul with items: Big Data Platforms (Apache Spark, Presto, Amazon EMR); Cloud Data Warehouses (Amazon Redshift, Snowflake, Google BigQuery, Databricks); Object-Oriented Coding (Java, Python); NoSQL Databases (DynamoDB, Cosmos DB, MongoDB); Container Management Systems (Kubernetes, Amazon ECS); Artificial Intelligence / Machine Learning (Amazon Sagemaker, Azure ML Studio); Streaming Data Ingestion and Analytics (Amazon Kinesis, Apache Kafka); Modern Data Workflows (Apache Airflow, dbt, Dagster). Now Benefits: ul list. Benefits items