Data Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment
Looking at the content:
"Why Join Q2?" and "What Makes Q2 Special?" - This is company overview/culture. Could be "About the company" or similar. But the rules say use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". "Why Join Q2?" is essentially benefits/culture. There's a "Health & Wellness" section later with benefits listed. Also "Our Culture & Commitment" repeats benefits.
"Our Team" - describes the team. Could be part of "About the role" or separate.
"The Role" - this is the role description. Should be "About the role" heading.
"Requirements" - this is a list of requirements. Should be "Requirements" heading with ul/li.
"Health & Wellness" - lists benefits: Hybrid Work Opportunities, Flexible Time Off, Career Development & Mentoring Programs, Health & Wellness Benefits, Community Volunteering, Employee Peer Recognition Programs. This is a Benefits section.
"Our Culture & Commitment" - more culture description, mentions benefits again, Spark Program, EEO statement. EEO should be removed.
Also there's a line: "This position requires fluent written and oral communication in English. Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is requirements/qualifications.
And "Applicants in California or Washington State may not be exempt from federal and state overtime requirements" - legal boilerplate, remove.
Also "Click here to find out more about the benefits we offer." appears twice - remove as application instruction/navigation.
Now, I need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
The posting doesn't have explicit "Responsibilities" section, but "The Role" describes what you'll do. Could be "About the role" or "Responsibilities". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use those exact headings when appropriate.
Let's structure:
1. About the role - from "The Role" paragraph.
2. Responsibilities - not explicitly listed, but the role description says "you will work closely with experienced engineers to design, implement, test, and operate cloud-native, data-driven services and applications across Q2’s Fraud Intelligence Platform." That's responsibilities. Could put under About the role or separate Responsibilities. Since there's no bullet list, maybe keep as prose under About the role.
3. Requirements - the list under "Requirements" heading. That's a mix of degree/experience, technical skills, tools. Could split into Qualifications (degree/experience) and Skills (technical). But the rules have both Qualifications and Skills as possible headings. The posting has "Requirements" as a heading with a list. I'll use "Requirements" as heading and list all items.
But the rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Requirements" is allowed. I'll use that.
4. Benefits - from "Health & Wellness" section and "Our Culture & Commitment". There's a list of benefits. I'll create a Benefits section with ul/li.
5. There's no Pay or Schedule info, so omit.
6. "Our Team" - could be part of About the role or separate. Since it's about the team context, maybe include as a paragraph under About the role or a separate "About the team" but not in allowed headings. The allowed headings are specific. I could include as a paragraph before About the role.
7. "Why Join Q2?" and "What Makes Q2 Special?" - company mission/culture. Could be a brief intro paragraph.
But the rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can have a brief introductory paragraph about the company.
Also: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to keep all details.
Let me draft HTML:
First, a paragraph about company: "Q2 is a leading provider of digital banking and lending solutions... mission is simple: build strong and diverse communities through innovative financial technology—and we do that by empowering our people to help create success for our customers."
Then "What Makes Q2 Special?" content: "Being as passionate about our people as we are about our mission. We celebrate our employees... Q2 Homecoming Week..." This is culture/benefits. Could be part of Benefits or separate. Since Benefits section will list specific benefits, maybe keep this as a paragraph under a "About the company" but not a heading. The rules don't have "About the company" heading. I could just include as prose before sections.
But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". So I should only use those headings when there's content.
I think I'll have:
- A brief introductory paragraph (no heading) about Q2 and culture.
- About the role
with prose from "The Role" and "Our Team".
- Requirements
with ul/li for each requirement bullet.
- Benefits
with ul/li for benefits listed.
But the Requirements list includes both qualifications (degree, experience) and skills (technologies). Could split into Qualifications and Skills. However the posting groups them under "Requirements". The rules allow both Qualifications and Skills headings. I could split: Qualifications for degree/experience, Skills for technical skills. But the posting doesn't separate. I'll keep as Requirements with all items.
Also there's a line: "This position requires fluent written and oral communication in English. Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is a requirement. Should be included in Requirements list.
Now, the Benefits list: from "Health & Wellness" section: "Hybrid Work Opportunities", "Flexible Time Off", "Career Development & Mentoring Programs", "Health & Wellness Benefits, including competitive health insurance offerings and generous paid parental leave for eligible new parents", "Community Volunteering & Company Philanthropy Programs", "Employee Peer Recognition Programs – “You Earned it”". Also from "Our Culture & Commitment": "resources for physical, mental, and professional well-being", "Spark Program". But "Click here to find out more about the benefits we offer." is a link, remove.
I'll create a Benefits section with these as list items.
Now, remove EEO statement, California/Washington overtime line, "Click here..." lines, "We are an Equal Opportunity Employer..." etc.
Also remove duplicated "Click here to find out more about the benefits we offer." appears twice.
Now, write HTML.
Let's start:
Q2 is a leading provider of digital banking and lending solutions to banks, credit unions, alternative finance companies, and fintechs in the U.S. and internationally. Our mission is simple: build strong and diverse communities through innovative financial technology—and we do that by empowering our people to help create success for our customers.
We celebrate our employees through our year-round Q2 ChangeMakers awards program and global moments of recognition and connection. We invest in the growth and development of our team members through ongoing learning opportunities, internal mobility, and meaningful leadership relationships. From company-wide volunteer days to events like our Q2 Homecoming Week—featuring learning, community service, and culture-building experiences—we create opportunities to connect, grow, and make an impact.
About the role
The Risk & Fraud team at Q2 is responsible for helping our customers take a proactive stance against fraud and managing the risks of their business. We build and enhance products that evolve with the ever-changing fraud landscape, delivering tangible value for our customers. Our solutions enable them to focus more of their time and energy on their mission: best serving their customers and communities.
In this role, you will work closely with experienced engineers to design, implement, test, and operate cloud-native, data-driven services and applications across Q2’s Fraud Intelligence Platform. This is a production-focused role where you will gradually take on more responsibility as you gain experience working with real-world systems and data. We are looking for engineers who are eager to learn, enjoy working across the stack, and care about building reliable software in environments where quality and correctness matter.
Requirements
- A Bachelor’s degree in Computer Science, Information Systems or similar plus a minimum of 2 years of related work experience; or an advanced degree
- Working knowledge of data transformations, data orchestration and pipelines, data replication
- Working knowledge of SQL and NoSQL databases, data warehouses, distributed file storage and compute platforms
- Good understanding of software engineering, distributed software design and data-centric systems architecture
- Data Movement and Pipelines: Apache Airflow, dbt, Kafka
- Data Warehouse: Snowflake
- Databases: SQL Server, Postgres, DynamoDB
- Languages: Python, C#, Golang, Bash, SQL
- CI/CD tools and infrastructure as code deployment: GitLab, Azure DevOps, Terraform, Argo CD
- Containerization: Kubernetes, Docker
- Data Tools: Pyspark, Snowpark, AWS Glue, Pandas, Databricks, SageMaker
- Fluent written and oral communication in English
- Authorization to work for any employer in the U.S. (visa sponsorship not available)
Benefits
- Hybrid work opportunities
- Flexible time off
- Career development and mentoring programs
- Health and wellness benefits, including competitive health insurance offerings and generous paid parental leave for eligible new parents
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Looking at the content: "Why Join Q2?" and "What Makes Q2 Special?" - This is company overview/culture. Could be "About the company" or similar. But the rules say use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". "Why Join Q2?" is essentially benefits/culture. There's a "Health & Wellness" section later with benefits listed. Also "Our Culture & Commitment" repeats benefits. "Our Team" - describes the team. Could be part of "About the role" or separate. "The Role" - this is the role description. Should be "About the role" heading. "Requirements" - this is a list of requirements. Should be "Requirements" heading with ul/li. "Health & Wellness" - lists benefits: Hybrid Work Opportunities, Flexible Time Off, Career Development & Mentoring Programs, Health & Wellness Benefits, Community Volunteering, Employee Peer Recognition Programs. This is a Benefits section. "Our Culture & Commitment" - more culture description, mentions benefits again, Spark Program, EEO statement. EEO should be removed. Also there's a line: "This position requires fluent written and oral communication in English. Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is requirements/qualifications. And "Applicants in California or Washington State may not be exempt from federal and state overtime requirements" - legal boilerplate, remove. Also "Click here to find out more about the benefits we offer." appears twice - remove as application instruction/navigation. Now, I need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting doesn't have explicit "Responsibilities" section, but "The Role" describes what you'll do. Could be "About the role" or "Responsibilities". The rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use those exact headings when appropriate.
Let's structure:
1. About the role - from "The Role" paragraph.
2. Responsibilities - not explicitly listed, but the role description says "you will work closely with experienced engineers to design, implement, test, and operate cloud-native, data-driven services and applications across Q2’s Fraud Intelligence Platform." That's responsibilities. Could put under About the role or separate Responsibilities. Since there's no bullet list, maybe keep as prose under About the role.
3. Requirements - the list under "Requirements" heading. That's a mix of degree/experience, technical skills, tools. Could split into Qualifications (degree/experience) and Skills (technical). But the rules have both Qualifications and Skills as possible headings. The posting has "Requirements" as a heading with a list. I'll use "Requirements" as heading and list all items.
But the rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Requirements" is allowed. I'll use that.
4. Benefits - from "Health & Wellness" section and "Our Culture & Commitment". There's a list of benefits. I'll create a Benefits section with ul/li.
5. There's no Pay or Schedule info, so omit.
6. "Our Team" - could be part of About the role or separate. Since it's about the team context, maybe include as a paragraph under About the role or a separate "About the team" but not in allowed headings. The allowed headings are specific. I could include as a paragraph before About the role.
7. "Why Join Q2?" and "What Makes Q2 Special?" - company mission/culture. Could be a brief intro paragraph.
But the rules: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can have a brief introductory paragraph about the company. Also: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to keep all details. Let me draft HTML: First, a paragraph about company: "Q2 is a leading provider of digital banking and lending solutions... mission is simple: build strong and diverse communities through innovative financial technology—and we do that by empowering our people to help create success for our customers." Then "What Makes Q2 Special?" content: "Being as passionate about our people as we are about our mission. We celebrate our employees... Q2 Homecoming Week..." This is culture/benefits. Could be part of Benefits or separate. Since Benefits section will list specific benefits, maybe keep this as a paragraph under a "About the company" but not a heading. The rules don't have "About the company" heading. I could just include as prose before sections. But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". So I should only use those headings when there's content.
I think I'll have:
- A brief introductory paragraph (no heading) about Q2 and culture.
- About the role
with prose from "The Role" and "Our Team".
- Requirements
with ul/li for each requirement bullet.
- Benefits
with ul/li for benefits listed.
But the Requirements list includes both qualifications (degree, experience) and skills (technologies). Could split into Qualifications and Skills. However the posting groups them under "Requirements". The rules allow both Qualifications and Skills headings. I could split: Qualifications for degree/experience, Skills for technical skills. But the posting doesn't separate. I'll keep as Requirements with all items.
Also there's a line: "This position requires fluent written and oral communication in English. Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is a requirement. Should be included in Requirements list.
Now, the Benefits list: from "Health & Wellness" section: "Hybrid Work Opportunities", "Flexible Time Off", "Career Development & Mentoring Programs", "Health & Wellness Benefits, including competitive health insurance offerings and generous paid parental leave for eligible new parents", "Community Volunteering & Company Philanthropy Programs", "Employee Peer Recognition Programs – “You Earned it”". Also from "Our Culture & Commitment": "resources for physical, mental, and professional well-being", "Spark Program". But "Click here to find out more about the benefits we offer." is a link, remove.
I'll create a Benefits section with these as list items.
Now, remove EEO statement, California/Washington overtime line, "Click here..." lines, "We are an Equal Opportunity Employer..." etc.
Also remove duplicated "Click here to find out more about the benefits we offer." appears twice.
Now, write HTML.
Let's start:
Q2 is a leading provider of digital banking and lending solutions to banks, credit unions, alternative finance companies, and fintechs in the U.S. and internationally. Our mission is simple: build strong and diverse communities through innovative financial technology—and we do that by empowering our people to help create success for our customers.
We celebrate our employees through our year-round Q2 ChangeMakers awards program and global moments of recognition and connection. We invest in the growth and development of our team members through ongoing learning opportunities, internal mobility, and meaningful leadership relationships. From company-wide volunteer days to events like our Q2 Homecoming Week—featuring learning, community service, and culture-building experiences—we create opportunities to connect, grow, and make an impact.
About the role
The Risk & Fraud team at Q2 is responsible for helping our customers take a proactive stance against fraud and managing the risks of their business. We build and enhance products that evolve with the ever-changing fraud landscape, delivering tangible value for our customers. Our solutions enable them to focus more of their time and energy on their mission: best serving their customers and communities.
In this role, you will work closely with experienced engineers to design, implement, test, and operate cloud-native, data-driven services and applications across Q2’s Fraud Intelligence Platform. This is a production-focused role where you will gradually take on more responsibility as you gain experience working with real-world systems and data. We are looking for engineers who are eager to learn, enjoy working across the stack, and care about building reliable software in environments where quality and correctness matter.
Requirements
- A Bachelor’s degree in Computer Science, Information Systems or similar plus a minimum of 2 years of related work experience; or an advanced degree
- Working knowledge of data transformations, data orchestration and pipelines, data replication
- Working knowledge of SQL and NoSQL databases, data warehouses, distributed file storage and compute platforms
- Good understanding of software engineering, distributed software design and data-centric systems architecture
- Data Movement and Pipelines: Apache Airflow, dbt, Kafka
- Data Warehouse: Snowflake
- Databases: SQL Server, Postgres, DynamoDB
- Languages: Python, C#, Golang, Bash, SQL
- CI/CD tools and infrastructure as code deployment: GitLab, Azure DevOps, Terraform, Argo CD
- Containerization: Kubernetes, Docker
- Data Tools: Pyspark, Snowpark, AWS Glue, Pandas, Databricks, SageMaker
- Fluent written and oral communication in English
- Authorization to work for any employer in the U.S. (visa sponsorship not available)
Benefits
- Hybrid work opportunities
- Flexible time off
- Career development and mentoring programs
- Health and wellness benefits, including competitive health insurance offerings and generous paid parental leave for eligible new parents