Staff Software Engineer
for each section heading.
We must use - for any list of duties/requirements/benefits. Use
for prose.
We must not include boilerplate: EEO, legal, AI Utilization, etc. Also remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail.
We need to ensure we keep all details from the posting that are substantive.
Let's parse the posting text:
"Job Description Team: Technology – Reporting and Analytics Salary Range: USD 175K Location: Remote Opportunity for Impact Applied builds cloud software and AI-powered solutions that are reinventing how the global insurance industry operates, and we do it at a pace that keeps us ahead. What you ship here reaches thousands of agencies and brokers worldwide and sets the standard for what modern insurance technology looks like. We’re looking for a Staff Software Engineer to join our Technology – Reporting and Analytics team. This role involves setting technical direction for the data pipelines and infrastructure that power our customer-facing Data Lake platform across a wide variety of customer data sources and AI-driven and other data products. This is an individual contributor role with organization-wide influence: you will solve our hardest data engineering problems and raise the bar for how the team builds, operates, and scales its infrastructure. As a Staff Software Engineer, you will collaborate with Architects, Product Owners, and Scrum team members to engineer and deliver high-quality technical solutions. You'll play a pivotal role in transforming and orchestrating massive data sets, creating impactful solutions that drive innovation and efficiency for our clients' businesses."
Then "What You’ll Do" list:
- Lead the design and implementation of sophisticated and reliable data pipelines, encompassing extraction, transformation, and data ingestion processes, while ensuring alignment with our product vision and impact across the customer-facing Data Lake
- Own the development of strategic projects from initial conception to completion, delivering large features and improvements with minimal guidance, and providing leadership across multiple projects and teams
- Utilize tools like Debezium, GCP stack (including Pub/Sub and Dataflow), BigQuery, and SQL for managing and processing large scale customer data across various data sources, driving the innovation and optimization of the data services that power AI and other data products
- Define and enforce engineering standards across the team: code review norms, testing strategy, reusable frameworks, and CI/CD practices
- Author high quality code that adheres to internal standards for style, maintainability, and best practices, while leading by example in solving technical problems of the highest scope and complexity
- Mentor engineers across the team through design review, pair programming, and structured technical feedback, coordinating the efforts of cross-functional teams and fostering a culture of innovation and learning
- Partner directly with Engineering, Product, and business leadership to translate ambiguous business problems into technical requirements
- Identify systemic problems no one has asked you to fix, and build the case for addressing them
- Evaluate emerging technologies and contribute to the technical roadmap for the data platform
Then "What We’re Looking For":
- 10+ years of software engineering experience, including 3+ years’ operating at a senior or lead level with demonstrated technical influence beyond your immediate team
- Expert-level proficiency in Python, Golang, SQL, and deep experience with the GCP data and ETL stack (Debezium, Pub/Sub, Dataflow, BigQuery) or equivalent technologies, including deep BigQuery expertise (partitioning and clustering strategy, query performance tuning, and cost optimization at scale)
- Proven track record architecting, building, and scaling RESTful services and APIs on Google Cloud serving multiple consuming teams
- Deep understanding of Agile frameworks, ideally Scrum, and tools like Jira and Confluence
- Exceptional written and verbal communication skills, including design documents that create alignment among senior stakeholders
- Demonstrated ability to influence without authority — driving technical decisions across teams that don't report to you
- Track record of mentoring engineers to promotion
- Strong technical abilities, troubleshooting skills, and research capabilities, with the judgment to know when to depart from established patterns
- Bachelor-level degree in Computer Science, MIS, or CIS, or equivalent experience
Then "Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background. If this role speaks to you, apply."
Then "Why You’ll Like Working on Team Applied" paragraph.
Then "How We’ll Support You" bullet list:
- Medical, Dental, and Vision Coverage
- Holiday and Vacation Time
- Health & Wellness Days
- A Bonus Day for Your Birthday
Then "Compensation Transparency" paragraph: "Our targeted starting base salary in the United States for this position considers a variety of factors, including depth and breadth of experience, skills and role scope. Depending on the role, team members may also be eligible for additional compensation plans (bonus and commission)."
Then "Your Security Matters:" etc (boilerplate). Then "AI Utilization" etc (boilerplate). Then EEO statement (boilerplate). Remove those.
We need to keep substantive info: The "Why You’ll Like Working on Team Applied" and "How We’ll Support You" maybe considered Benefits? The "Why You’ll Like Working on Team Applied" is more about culture; could be part of About the role or separate? The instructions: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
- About the role: includes description of team, impact, role overview.
- Responsibilities: What You'll Do list.
- Requirements: What We're Looking For list (experience, proficiency, etc.)
- Qualifications: Bachelor-level degree etc. Could be separate but also part of Requirements. However we have both Requirements and Qualifications as possible sections. We need to decide if we have enough content for each. The posting includes both experience/skills and degree. We could put degree under Qualifications, and the rest under Requirements or Skills. But we also have Skills section for tools etc.
We need to avoid thin sections. Prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But headings are prescribed; we can omit sections if no real specific content. So we need to decide which sections have real specific content.
We have:
- About the role: yes.
- Responsibilities: yes.
- Requirements: yes (experience, proficiency, track record, Agile, communication, influence, mentoring, troubleshooting).
- Qualifications: yes (Bachelor-level degree or equivalent).
- Skills: could list specific tools: Python, Golang, SQL, Debezium, GCP stack (Pub/Sub, Dataflow, BigQuery), RESTful services/APIs on GCP, Jira, Confluence. That's specific.
- Benefits: yes (Medical, Dental, Vision Coverage, Holiday and Vacation Time, Health & Wellness Days, A Bonus Day for Your Birthday).
- Pay: yes (Salary Range: USD 175K, plus note about bonus/commission).
- Schedule: not mentioned; remote location but no schedule. So omit Schedule.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must not include filler like "commensurate with experience". We have specific salary.
Now we need to format.
Use
for each heading.
For lists, use - .
For prose, use
.
We must not repeat job title.
We must not include Job ID etc.
We must preserve all substantive information: ensure we keep all details from the lists.
Let's craft each section.
About the role: combine the introductory paragraphs up to "What You’ll Do". Should we include the "Opportunity for Impact" paragraph? Yes.
So About the role
containing:
"Opportunity for Impact Applied builds cloud software and AI-powered solutions that are reinventing how the global insurance industry operates, and we do it at a pace that keeps us ahead. What you ship here reaches thousands of agencies and brokers worldwide and sets the standard for what modern insurance technology looks like. We’re looking for a Staff Software Engineer to join our Technology – Reporting and Analytics team. This role involves setting technical direction for the data pipelines and infrastructure that power our customer-facing Data Lake platform across a wide variety of customer data sources and AI-driven and other data products. This is an individual contributor role with organization-wide influence: you will solve our hardest data engineering problems and raise the bar for how the team builds, operates, and scales its infrastructure. As a Staff Software Engineer, you will collaborate with Architects, Product Owners, and Scrum team members to engineer and deliver high-quality technical solutions. You'll play a pivotal role in transforming and orchestrating massive data sets, creating impactful solutions that drive innovation and efficiency for our clients' businesses."
We need to ensure we don't repeat the job title "Staff Software Engineer" maybe it's okay as it's part of description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It's okay to appear in prose.
Now Responsibilities: list each bullet as
- .
We must keep the exact wording.
Let's copy each bullet:
- Lead the design and implementation of sophisticated and reliable data pipelines, encompassing extraction, transformation, and data ingestion processes, while ensuring alignment with our product vision and impact across the customer-facing Data Lake
- Own the development of strategic projects from initial conception to completion, delivering large features and improvements with minimal guidance, and providing leadership across multiple projects and teams
- Utilize tools like Debezium, GCP stack (including Pub/Sub and Dataflow), BigQuery, and SQL for managing and processing large scale customer data across various data sources, driving the innovation and optimization of the data services that power AI and other data products
- Define and enforce engineering standards across the team: code review norms, testing strategy, reusable frameworks, and CI/CD practices
- Author high quality code that adheres to internal standards for style, maintainability, and best practices, while leading by example in solving technical problems of the highest scope and complexity
-
for prose. We must not include boilerplate: EEO, legal, AI Utilization, etc. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we keep all details from the posting that are substantive. Let's parse the posting text: "Job Description Team: Technology – Reporting and Analytics Salary Range: USD 175K Location: Remote Opportunity for Impact Applied builds cloud software and AI-powered solutions that are reinventing how the global insurance industry operates, and we do it at a pace that keeps us ahead. What you ship here reaches thousands of agencies and brokers worldwide and sets the standard for what modern insurance technology looks like. We’re looking for a Staff Software Engineer to join our Technology – Reporting and Analytics team. This role involves setting technical direction for the data pipelines and infrastructure that power our customer-facing Data Lake platform across a wide variety of customer data sources and AI-driven and other data products. This is an individual contributor role with organization-wide influence: you will solve our hardest data engineering problems and raise the bar for how the team builds, operates, and scales its infrastructure. As a Staff Software Engineer, you will collaborate with Architects, Product Owners, and Scrum team members to engineer and deliver high-quality technical solutions. You'll play a pivotal role in transforming and orchestrating massive data sets, creating impactful solutions that drive innovation and efficiency for our clients' businesses." Then "What You’ll Do" list: - Lead the design and implementation of sophisticated and reliable data pipelines, encompassing extraction, transformation, and data ingestion processes, while ensuring alignment with our product vision and impact across the customer-facing Data Lake - Own the development of strategic projects from initial conception to completion, delivering large features and improvements with minimal guidance, and providing leadership across multiple projects and teams - Utilize tools like Debezium, GCP stack (including Pub/Sub and Dataflow), BigQuery, and SQL for managing and processing large scale customer data across various data sources, driving the innovation and optimization of the data services that power AI and other data products - Define and enforce engineering standards across the team: code review norms, testing strategy, reusable frameworks, and CI/CD practices - Author high quality code that adheres to internal standards for style, maintainability, and best practices, while leading by example in solving technical problems of the highest scope and complexity - Mentor engineers across the team through design review, pair programming, and structured technical feedback, coordinating the efforts of cross-functional teams and fostering a culture of innovation and learning - Partner directly with Engineering, Product, and business leadership to translate ambiguous business problems into technical requirements - Identify systemic problems no one has asked you to fix, and build the case for addressing them - Evaluate emerging technologies and contribute to the technical roadmap for the data platform Then "What We’re Looking For": - 10+ years of software engineering experience, including 3+ years’ operating at a senior or lead level with demonstrated technical influence beyond your immediate team - Expert-level proficiency in Python, Golang, SQL, and deep experience with the GCP data and ETL stack (Debezium, Pub/Sub, Dataflow, BigQuery) or equivalent technologies, including deep BigQuery expertise (partitioning and clustering strategy, query performance tuning, and cost optimization at scale) - Proven track record architecting, building, and scaling RESTful services and APIs on Google Cloud serving multiple consuming teams - Deep understanding of Agile frameworks, ideally Scrum, and tools like Jira and Confluence - Exceptional written and verbal communication skills, including design documents that create alignment among senior stakeholders - Demonstrated ability to influence without authority — driving technical decisions across teams that don't report to you - Track record of mentoring engineers to promotion - Strong technical abilities, troubleshooting skills, and research capabilities, with the judgment to know when to depart from established patterns - Bachelor-level degree in Computer Science, MIS, or CIS, or equivalent experience Then "Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background. If this role speaks to you, apply." Then "Why You’ll Like Working on Team Applied" paragraph. Then "How We’ll Support You" bullet list: - Medical, Dental, and Vision Coverage - Holiday and Vacation Time - Health & Wellness Days - A Bonus Day for Your Birthday Then "Compensation Transparency" paragraph: "Our targeted starting base salary in the United States for this position considers a variety of factors, including depth and breadth of experience, skills and role scope. Depending on the role, team members may also be eligible for additional compensation plans (bonus and commission)." Then "Your Security Matters:" etc (boilerplate). Then "AI Utilization" etc (boilerplate). Then EEO statement (boilerplate). Remove those. We need to keep substantive info: The "Why You’ll Like Working on Team Applied" and "How We’ll Support You" maybe considered Benefits? The "Why You’ll Like Working on Team Applied" is more about culture; could be part of About the role or separate? The instructions: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. - About the role: includes description of team, impact, role overview. - Responsibilities: What You'll Do list. - Requirements: What We're Looking For list (experience, proficiency, etc.) - Qualifications: Bachelor-level degree etc. Could be separate but also part of Requirements. However we have both Requirements and Qualifications as possible sections. We need to decide if we have enough content for each. The posting includes both experience/skills and degree. We could put degree under Qualifications, and the rest under Requirements or Skills. But we also have Skills section for tools etc. We need to avoid thin sections. Prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But headings are prescribed; we can omit sections if no real specific content. So we need to decide which sections have real specific content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: yes (experience, proficiency, track record, Agile, communication, influence, mentoring, troubleshooting). - Qualifications: yes (Bachelor-level degree or equivalent). - Skills: could list specific tools: Python, Golang, SQL, Debezium, GCP stack (Pub/Sub, Dataflow, BigQuery), RESTful services/APIs on GCP, Jira, Confluence. That's specific. - Benefits: yes (Medical, Dental, Vision Coverage, Holiday and Vacation Time, Health & Wellness Days, A Bonus Day for Your Birthday). - Pay: yes (Salary Range: USD 175K, plus note about bonus/commission). - Schedule: not mentioned; remote location but no schedule. So omit Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not include filler like "commensurate with experience". We have specific salary. Now we need to format. Use
for each heading.
For lists, use - .
For prose, use
.
We must not repeat job title.
We must not include Job ID etc.
We must preserve all substantive information: ensure we keep all details from the lists.
Let's craft each section.
About the role: combine the introductory paragraphs up to "What You’ll Do". Should we include the "Opportunity for Impact" paragraph? Yes.
So About the role
containing:
"Opportunity for Impact Applied builds cloud software and AI-powered solutions that are reinventing how the global insurance industry operates, and we do it at a pace that keeps us ahead. What you ship here reaches thousands of agencies and brokers worldwide and sets the standard for what modern insurance technology looks like. We’re looking for a Staff Software Engineer to join our Technology – Reporting and Analytics team. This role involves setting technical direction for the data pipelines and infrastructure that power our customer-facing Data Lake platform across a wide variety of customer data sources and AI-driven and other data products. This is an individual contributor role with organization-wide influence: you will solve our hardest data engineering problems and raise the bar for how the team builds, operates, and scales its infrastructure. As a Staff Software Engineer, you will collaborate with Architects, Product Owners, and Scrum team members to engineer and deliver high-quality technical solutions. You'll play a pivotal role in transforming and orchestrating massive data sets, creating impactful solutions that drive innovation and efficiency for our clients' businesses."
We need to ensure we don't repeat the job title "Staff Software Engineer" maybe it's okay as it's part of description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It's okay to appear in prose.
Now Responsibilities: list each bullet as
- .
We must keep the exact wording.
Let's copy each bullet:
- Lead the design and implementation of sophisticated and reliable data pipelines, encompassing extraction, transformation, and data ingestion processes, while ensuring alignment with our product vision and impact across the customer-facing Data Lake
- Own the development of strategic projects from initial conception to completion, delivering large features and improvements with minimal guidance, and providing leadership across multiple projects and teams
- Utilize tools like Debezium, GCP stack (including Pub/Sub and Dataflow), BigQuery, and SQL for managing and processing large scale customer data across various data sources, driving the innovation and optimization of the data services that power AI and other data products
- Define and enforce engineering standards across the team: code review norms, testing strategy, reusable frameworks, and CI/CD practices
- Author high quality code that adheres to internal standards for style, maintainability, and best practices, while leading by example in solving technical problems of the highest scope and complexity
-
. We must not repeat job title. We must not include Job ID etc. We must preserve all substantive information: ensure we keep all details from the lists. Let's craft each section. About the role: combine the introductory paragraphs up to "What You’ll Do". Should we include the "Opportunity for Impact" paragraph? Yes. So About the role
containing: "Opportunity for Impact Applied builds cloud software and AI-powered solutions that are reinventing how the global insurance industry operates, and we do it at a pace that keeps us ahead. What you ship here reaches thousands of agencies and brokers worldwide and sets the standard for what modern insurance technology looks like. We’re looking for a Staff Software Engineer to join our Technology – Reporting and Analytics team. This role involves setting technical direction for the data pipelines and infrastructure that power our customer-facing Data Lake platform across a wide variety of customer data sources and AI-driven and other data products. This is an individual contributor role with organization-wide influence: you will solve our hardest data engineering problems and raise the bar for how the team builds, operates, and scales its infrastructure. As a Staff Software Engineer, you will collaborate with Architects, Product Owners, and Scrum team members to engineer and deliver high-quality technical solutions. You'll play a pivotal role in transforming and orchestrating massive data sets, creating impactful solutions that drive innovation and efficiency for our clients' businesses." We need to ensure we don't repeat the job title "Staff Software Engineer" maybe it's okay as it's part of description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It's okay to appear in prose. Now Responsibilities: list each bullet as