Payments Solutions Engineer, Consumer Payments Partner Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, application instructions, etc. Must preserve all substantive info. Let's parse the posting. Content: - Application window open until at least October 07, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA. - Minimum qualifications: Bachelor’s degree in Engineering, Computer Science, a related field, or equivalent practical experience. 3 years of experience working with client-side web technologies (e.g., HTML, CSS, JavaScript, or HTTP). 3 years of experience coding with one or more programming languages (e.g., Java, C/C++, Python). Experience troubleshooting technical issues for internal/external partners or customers. Experience using AI for workflows. - Preferred qualifications: 5 years of experience in technical troubleshooting. 3 years of experience in data analysis using SQL/MySQL. 3 years of experience in the Payments industry. Experience working with and managing external partners or customers. Strong program management skills with experience coordinating cross-functional teams. Excellent communication (written and verbal), people management, and stakeholder management skills. - About the job: paragraph describing gTech Users and Products (gUP) mission, role description: help businesses deliver seamless and secure digital payment experiences while collaborating with internal cross-functional teams. Supporting external partners as they adopt solutions, troubleshooting web and mobile checkout flows. Primary technical bridge to partners, identify friction points and shape future platform enhancements. Additional description about Google, gTech, etc. - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $127000 - $182000 (USD) + 15% bonus target + equity + benefits - Responsibilities: list: Maintain Google Pay developer documentation, integration playbooks, and partner resources, while managing and triaging technical issues submitted by developers and partners. Act as a trusted technical advisor for merchants, payment service providers (PSPs), and e-commerce platforms, guiding them through the architectural design and end-to-end implementation of Google Pay across web and mobile surfaces. Diagnose and resolve complex integration and transactional issues, collaborating closely with external engineering teams to ensure optimal checkout reliability, performance, and security. Gather real-world partner insights and technical feedback to advocate for platform enhancements, translating integration issues into actionable requirements for internal Google Product and Engineering teams. Create and maintain reference implementations, code samples, testing guides, and integration tools that streamline onboarding and make adopting Google Pay fast and frictionless for developers. - Benefits: mention "benefits" in pay line: "+ equity + benefits". Also there is a link "Learn more about benefits at Google ." So we have benefits info: equity, benefits (unspecified). But we should only include Benefits section if posting actually states them. It does mention benefits generically, but not specifics. The rule: never create Benefits section unless posting actually states them. It does state "+ equity + benefits". That's a statement of benefits (equity and benefits). It's vague but it's stating benefits exist. Should we include? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (equity + benefits). So we can include a Benefits section with that info. However we should avoid filler like "not specified". We have "equity + benefits". That's specific enough? It mentions equity and benefits. We'll include. - Pay: we have salary range and bonus target. So include Pay section. - Schedule: not mentioned. So omit Schedule. - Skills: Could be derived from qualifications but we might combine Requirements and Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have About the job (About the role). We have Responsibilities. We have Minimum qualifications and Preferred qualifications. Could combine into Requirements and Qualifications? Usually Minimum qualifications = Requirements, Preferred qualifications = Qualifications. We'll make Requirements (minimum) and Qualifications (preferred). Skills could be separate but we may not have explicit skills list beyond qualifications. Could combine skills into Qualifications. Safer to include Requirements and Qualifications sections. We also have location info (preferred working location). Could be part of About the role? Might be separate but not a standard heading. Could include in a short paragraph under About the role or maybe a separate "Location" but not in allowed headings. Probably we can include location info in a paragraph under About the role (or as a note). The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata, we can fold into a short

. We'll include a paragraph after About the role heading maybe. We must remove boilerplate: EEO, accommodation, application instructions, "Learn more about benefits at Google ." (that's a link but we can keep mention of benefits but drop the link). Also remove "Google is proud to be an equal opportunity workplace..." etc. Also remove "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's part of pay description; we can keep that as part of Pay section. We must preserve all substantive information. So we need to keep the description about gTech, mission, role, etc. Keep the responsibilities list. Keep qualifications. Keep pay details. Keep location note. Keep benefits mention (equity + benefits). Keep the note about application window and location preference. Now produce HTML fragment. Structure:

About the role

... description ...

Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA.

The application window will be open until at least October 07, 2026. This opportunity will remain online based on business needs which may be before or after the specified date.

Then

Responsibilities

• ... each responsibility ...

Then

Requirements

• ... minimum qualifications ...

Then

Qualifications

• ... preferred qualifications ...

Then

Pay

Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $127000 - $182000 (USD) + 15% bonus target + equity + benefits

Then

Benefits

Equity and benefits are included as part of the compensation package.

(but we need to avoid filler; we have "equity + benefits". We can phrase: "The compensation package includes equity and benefits." That's derived from posting.) We should not add extra info not in posting. The posting says "+ equity + benefits". So we can say "Equity and benefits are included." That's essentially same. Check for any other substantive info: "Experience using AI for workflows." included in minimum qualifications. "Experience troubleshooting technical issues for internal/external partners or customers." included. "Experience using AI for workflows." included. Also "Experience working with and managing external partners or customers." in preferred qualifications. Also "Strong program management skills with experience coordinating cross-functional teams." etc. Also "Excellent communication (written and verbal), people management, and stakeholder management skills." All good. Now ensure we didn't include any boilerplate: removed EEO, accommodation, "Learn more about benefits at Google .", "Google is proud to be an equal opportunity workplace..." etc. Also removed "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." we kept that in Pay section. Now output only HTML fragment. Let's craft the About the role paragraph: combine the mission description. Original About the job paragraph: "In gTech Users and Products (gUP), our mission is to advocate for Google’s users by creating helpful and trusted experiences across the product ecosystem. We achieve this by meeting partners and consumers where they are with support and help, representing their needs with our product partners and proposing fixes and features that elevate their engagement with Google's diverse product ecosystem. Additionally we provide a range of product services that ensure our products are optimized for every user, no matter where they are in the world (e.g., localization, digitization, partner integration, and more). In this role, you will help businesses around the world deliver seamless and secure digital payment experiences while collaborating closely with internal cross-functional teams. You will spend your days supporting external partners as they adopt our solutions, troubleshooting web and mobile checkout flows. As the primary technical bridge to our partners, you will identify friction points and shape future platform enhancements. Google creates products and services that make the world a better place, and gTech’s role is to help bring them to life. Our teams of trusted advisors support customers globally. Our solutions are rooted in our technical skill, product expertise, and a thorough understanding of our customers’ complex needs. Whether the answer is a bespoke solution to solve a unique problem, or a new tool that can scale across Google, everything we do aims to ensure our customers benefit from the full potential of Google products. To learn more about gTech, check out our video ." We need to remove the video link mention maybe but keep the sentence? It's not substantive? It's a reference to video; could be considered boilerplate? It's a link to learn more; might be considered navigation? Probably we can drop "To learn more about gTech, check out our video ." as it's a link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is a navigation link to learn more; could be considered navigation. Safer to remove that sentence. Thus About the role paragraph will be everything except that final sentence. Let's craft: "In gTech Users and Products (gUP), our mission is to advocate for Google’s users by creating helpful and trusted experiences across the product ecosystem. We achieve this by meeting partners and consumers where they are with support and help, representing their needs with our product partners and proposing fixes and features that elevate their engagement with Google's diverse product ecosystem. Additionally we provide a range of product services that ensure our products are optimized for every user, no matter where they are in the world (e.g., localization, digitization, partner integration, and more). In this role, you will help businesses around the world deliver seamless and secure digital payment experiences while collaborating closely with internal cross-functional teams. You will spend your days supporting external partners as they adopt our solutions, troubleshooting web and mobile checkout flows. As the primary technical bridge to our partners, you will identify friction points and shape future platform enhancements. Google creates products and services that make the world a better place, and gTech’s role is to help bring them to life. Our teams of trusted advisors support customers globally. Our solutions are rooted in our technical skill, product expertise, and a thorough understanding of our customers’ complex needs. Whether the answer is a bespoke solution to solve a unique problem, or a new tool that can scale across Google, everything we do aims to ensure our customers benefit from the full potential of Google products." Now location note and application window note as separate paragraphs. Now Responsibilities list items: - Maintain Google Pay developer documentation, integration playbooks, and partner resources, while managing and triaging technical issues submitted by developers and partners. - Act as a trusted technical advisor for merchants, payment service providers (PSPs), and e-commerce platforms, guiding them through the architectural design and end-to-end implementation of Google Pay