Senior Software Engineer, AI/ML GenAI, Google Workspace
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes:
- About The Job (prose)
- Minimum qualifications (list)
- Preferred qualifications (list)
- Responsibilities (list)
- Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $174000 - $252000 (USD) + 15% bonus target + equity + benefits"
- Benefits: mention "benefits" but not detailed; we have a line "Learn more about benefits at Google ." That's not specific benefits. The rule: do NOT create Benefits section unless posting actually states them. It only says "benefits" generically, no specifics. So we should not create a Benefits section. However we could include Pay section (since pay details given). Schedule: not mentioned. So no Schedule.
We also have some boilerplate: EEO, accommodation, etc. Remove.
We need to preserve all substantive info: include minimum qualifications, preferred qualifications, responsibilities, about the job, pay.
We need to format lists with - . For qualifications, we have multiple bullet-like sentences separated by periods. We need to parse them into list items.
Minimum qualifications: "Bachelor’s degree or equivalent practical experience. 5 years of experience with software development in one or more programming languages.3 years of experience testing, maintaining, or launching software products, and 1 year of experience with software design and architecture. 3 years of experience with ML infrastructure (e.g., model deployment, model evaluation, optimization, data processing, debugging).1 year of experience with GenAI techniques (e.g., LLMs, Multi-Modal, Large Vision Models) or with GenAI-related concepts (language modeling, computer vision)."
We need to split each sentence into list items. Note there are missing spaces after periods in some places (e.g., "languages.3 years"). We'll treat as separate items.
Thus list items:
- Bachelor’s degree or equivalent practical experience.
- 5 years of experience with software development in one or more programming languages.
- 3 years of experience testing, maintaining, or launching software products, and 1 year of experience with software design and architecture.
- 3 years of experience with ML infrastructure (e.g., model deployment, model evaluation, optimization, data processing, debugging).
- 1 year of experience with GenAI techniques (e.g., LLMs, Multi-Modal, Large Vision Models) or with GenAI-related concepts (language modeling, computer vision).
Preferred qualifications: "Master's degree or PhD in Computer Science or related technical field. 5 years of experience with data structures and algorithms.3 years of experience working in a complex, matrixed organization involving cross-functional, or cross-business projects.1 year of experience in a technical leadership role. Experience developing accessible technologies."
List items:
- Master's degree or PhD in Computer Science or related technical field.
- 5 years of experience with data structures and algorithms.
- 3 years of experience working in a complex, matrixed organization involving cross-functional, or cross-business projects.
- 1 year of experience in a technical leadership role.
- Experience developing accessible technologies.
Responsibilities: list after "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google . Write and test product or system development code.Participate in, or lead design reviews with peers and stakeholders to decide amongst available technologies. Review code developed by other developers and provide feedback to ensure best practices (e.g., style guidelines, checking code in, accuracy, testability, and efficiency).Contribute to existing documentation or educational content and adapt content based on product/program updates and user feedback. Triage product or system issues and debug/track/resolve by analyzing the sources of issues and the impact on hardware, network, or service operations and quality."
We need to split into list items. The first phrase "Learn more about benefits at Google ." is not a responsibility; it's a link. Should we include? It's not a responsibility; but it's part of the responsibilities section? The heading "Responsibilities" then immediate text "Learn more about benefits at Google ." That seems like a stray. We should probably ignore that as boilerplate/link. The rule: remove duplicated lines, application instructions, etc. This is not exactly instruction but maybe a link. Safer to omit it as it's not a responsibility. We'll start list after that.
Thus responsibilities items:
- Write and test product or system development code.
- Participate in, or lead design reviews with peers and stakeholders to decide amongst available technologies.
- Review code developed by other developers and provide feedback to ensure best practices (e.g., style guidelines, checking code in, accuracy, testability, and efficiency).
- Contribute to existing documentation or educational content and adapt content based on product/program updates and user feedback.
- Triage product or system issues and debug/track/resolve by analyzing the sources of issues and the impact on hardware, network, or service operations and quality.
About the Job: prose paragraph(s). We'll combine into
. The text: "About The Job Google Cloud's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google Cloud's needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. You will anticipate our customer needs and be empowered to act like an owner, take action and innovate. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. With your technical expertise you will manage project priorities, deadlines, and deliverables. You will design, develop, test, deploy, maintain, and enhance software solutions. AI will change the future of work in profound ways, and our products— Gmail, Docs, Drive, Calendar, Sheets, Vids and Meet are at the forefront. From pre-computed summaries for email threads, summaries for meetings, and videos created from a document using lifelike AI avatars, our AI opportunity is huge. Our mission is to meaningfully connect people so they can create, build, and grow together and as part of the team you can build how productivity tools should work 5-10 years into the future. You will work with model builders (Google DeepMind), work with exceptional leaders, and have the ability to impact billions of users across the world."
We'll put that in a
.
Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $174000 - $252000 (USD) + 15% bonus target + equity + benefits"
We'll put in
under
Pay
.
We should not include Benefits section.
We need to output only HTML fragment, no extra markdown.
Thus:
About the role
maybe? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples. We need to decide which headings to use. We have About the Job (could be About the role). We'll use "About the role". Responsibilities. Requirements (maybe combine minimum qualifications?). Qualifications (maybe preferred). But we have both minimum and preferred qualifications. Could combine under "Requirements" for minimum and "Preferred qualifications" as separate? The instruction: use headings like Requirements, Qualifications, Skills. We could have:
- About the role
- Responsibilities
- Minimum qualifications
(but they said Requirements, Qualifications, Skills). Could use "Requirements" for minimum qualifications and "Preferred qualifications" for preferred. Or combine both under "Qualifications". But they said prefer few substantive sections over many thin ones. We have substantive content for both minimum and preferred; we could combine into one "Qualifications" section with two sublists? But we need to use - for any list. Could have a single qualifications section with two headings inside? Not allowed; only
for section headings. Could embed a
introducing then two
? Might be okay. But better to follow examples: they gave Requirements, Qualifications, Skills as possible headings. We could use "Requirements" for minimum qualifications and "Preferred qualifications" as a separate heading? That would be two sections. That's okay.
We'll do:
About the role
...
Responsibilities
...
Requirements
...
(minimum qualifications)
Preferred qualifications
...
Pay
...
We must not include Schedule, Benefits, Skills.
Check for any other substantive info: mention "application window will be open until at least September 29, 2026." That's a date; could be considered metadata. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. This is minor metadata (application window). Could fold into a short
maybe under About the role? But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those; it's about application window. Might be considered minor metadata; we could include as a short paragraph under About the role or separate? The instruction: "fold minor metadata into a short
or drop it." So we could include a short
after About the role: "The application window will be open until at least September 29, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." That's two sentences. Could be a short
. We'll include that.
Also "In most instances, this position requires in-person interviews as part of the hiring process." That's also metadata about interview process. Could fold into short
as well.
We'll combine those into a
after About the role maybe.
Thus About the role section will have
with the about job prose, then maybe a
for metadata? Better to keep one
for about job and another
for metadata. That's fine.
Now ensure we don't repeat job title as heading. Not.
Now produce HTML.
Let's craft.
About the role prose: we need to ensure we keep all content. We'll copy the About The Job paragraph exactly as given, but ensure proper punctuation.
We'll produce:
About the role
Google Cloud's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google Cloud's needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. You will anticipate our customer needs and be empowered to act like an owner, take action and innovate. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. With your technical expertise you will manage project priorities, deadlines,
. The text: "About The Job Google Cloud's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google Cloud's needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. You will anticipate our customer needs and be empowered to act like an owner, take action and innovate. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. With your technical expertise you will manage project priorities, deadlines, and deliverables. You will design, develop, test, deploy, maintain, and enhance software solutions. AI will change the future of work in profound ways, and our products— Gmail, Docs, Drive, Calendar, Sheets, Vids and Meet are at the forefront. From pre-computed summaries for email threads, summaries for meetings, and videos created from a document using lifelike AI avatars, our AI opportunity is huge. Our mission is to meaningfully connect people so they can create, build, and grow together and as part of the team you can build how productivity tools should work 5-10 years into the future. You will work with model builders (Google DeepMind), work with exceptional leaders, and have the ability to impact billions of users across the world." We'll put that in a
. Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $174000 - $252000 (USD) + 15% bonus target + equity + benefits" We'll put in
under
Pay
. We should not include Benefits section. We need to output only HTML fragment, no extra markdown. Thus:About the role
maybe? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples. We need to decide which headings to use. We have About the Job (could be About the role). We'll use "About the role". Responsibilities. Requirements (maybe combine minimum qualifications?). Qualifications (maybe preferred). But we have both minimum and preferred qualifications. Could combine under "Requirements" for minimum and "Preferred qualifications" as separate? The instruction: use headings like Requirements, Qualifications, Skills. We could have:
- About the role
- Responsibilities
- Minimum qualifications
(but they said Requirements, Qualifications, Skills). Could use "Requirements" for minimum qualifications and "Preferred qualifications" for preferred. Or combine both under "Qualifications". But they said prefer few substantive sections over many thin ones. We have substantive content for both minimum and preferred; we could combine into one "Qualifications" section with two sublists? But we need to use - for any list. Could have a single qualifications section with two headings inside? Not allowed; only
for section headings. Could embed a
introducing then two
? Might be okay. But better to follow examples: they gave Requirements, Qualifications, Skills as possible headings. We could use "Requirements" for minimum qualifications and "Preferred qualifications" as a separate heading? That would be two sections. That's okay.
We'll do:
About the role
...
Responsibilities
...
Requirements
...
(minimum qualifications)
Preferred qualifications
...
Pay
...
We must not include Schedule, Benefits, Skills.
Check for any other substantive info: mention "application window will be open until at least September 29, 2026." That's a date; could be considered metadata. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. This is minor metadata (application window). Could fold into a short
maybe under About the role? But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those; it's about application window. Might be considered minor metadata; we could include as a short paragraph under About the role or separate? The instruction: "fold minor metadata into a short
or drop it." So we could include a short
after About the role: "The application window will be open until at least September 29, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." That's two sentences. Could be a short
. We'll include that.
Also "In most instances, this position requires in-person interviews as part of the hiring process." That's also metadata about interview process. Could fold into short
as well.
We'll combine those into a
after About the role maybe.
Thus About the role section will have
with the about job prose, then maybe a
for metadata? Better to keep one
for about job and another
for metadata. That's fine.
Now ensure we don't repeat job title as heading. Not.
Now produce HTML.
Let's craft.
About the role prose: we need to ensure we keep all content. We'll copy the About The Job paragraph exactly as given, but ensure proper punctuation.
We'll produce:
About the role
Google Cloud's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google Cloud's needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. You will anticipate our customer needs and be empowered to act like an owner, take action and innovate. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. With your technical expertise you will manage project priorities, deadlines,
for section headings. Could embed a
introducing then two
- ? Might be okay. But better to follow examples: they gave Requirements, Qualifications, Skills as possible headings. We could use "Requirements" for minimum qualifications and "Preferred qualifications" as a separate heading? That would be two sections. That's okay.
We'll do:
About the role
...
Responsibilities
- ...
Requirements
- ...
Preferred qualifications
- ...
Pay
...
We must not include Schedule, Benefits, Skills. Check for any other substantive info: mention "application window will be open until at least September 29, 2026." That's a date; could be considered metadata. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. This is minor metadata (application window). Could fold into a short
maybe under About the role? But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those; it's about application window. Might be considered minor metadata; we could include as a short paragraph under About the role or separate? The instruction: "fold minor metadata into a short
or drop it." So we could include a short
after About the role: "The application window will be open until at least September 29, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." That's two sentences. Could be a short
. We'll include that. Also "In most instances, this position requires in-person interviews as part of the hiring process." That's also metadata about interview process. Could fold into short
as well. We'll combine those into a
after About the role maybe. Thus About the role section will have
with the about job prose, then maybe a
for metadata? Better to keep one
for about job and another
for metadata. That's fine. Now ensure we don't repeat job title as heading. Not. Now produce HTML. Let's craft. About the role prose: we need to ensure we keep all content. We'll copy the About The Job paragraph exactly as given, but ensure proper punctuation. We'll produce:
About the role
Google Cloud's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google Cloud's needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. You will anticipate our customer needs and be empowered to act like an owner, take action and innovate. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. With your technical expertise you will manage project priorities, deadlines,