Senior Interaction Designer, Google Health
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 6 years of interaction design experience in product design or UX design.
- Include a portfolio, website, or any other relevant link to your work in your resume (providing a viewable link or access instructions).
Preferred qualifications:
- Master's degree in Design, Human-Computer Interaction, Computer Science, a related field, or equivalent practical experience.
- 3 years of experience working in a complex, cross-functional organization.
- 2 years of experience leading design projects.
About The Job At Google, we "Focus on the user and all else will follow." Our Interaction Designers transform complex tasks into intuitive, easy-to-use experiences for billions of people. From creating user flows and wireframes to building mockups and prototypes, you will envision and bring product experiences to life with an inspired, refined, and magical feel. You will join our multi-disciplinary UX team, collaborating with Engineering and Product Management, leveraging user insights to create industry-leading products. As an Interaction Designer, you'll apply user-centered design methods to craft industry-leading user experiences from concept to execution, working with design partners to evolve the Google design language to build beautiful, innovative products. In this role, you will design intuitive, trustworthy, and impactful experiences for emerging areas of Google Health that are essential to deliver proactive, personalized coaching that bridges everyday habits with longitudinal medical care. You will lead end-to-end user experience design projects within our three core consumer health pillars: Adaptive Lifestyle Coaching (nutrition, women’s health), Personalized Health Companion (Personal Health Records, lab results, immunization data, and clinical visit prep), and Proactive Health Guardian (passive vitals baselines, irregular rhythm notifications, continuous glucose monitoring, and early health risks). Serving as a critical bridge between UX, Product Management, Engineering, Data Science, and Clinical Research, you will translate complex physiological signals into clear, actionable, medically sound and emotionally resonant user experiences. Google for Health is a company-wide effort to help billions of people be healthier. We work toward this vision by meeting people in their everyday moments and empowering them to stay healthy and partnering with care teams to provide more accurate and accessible care. Our teams are applying our expertise and technology to improve health outcomes globally – with high-quality information and tools to help people manage their health and wellbeing, solutions to transform care delivery, research to catalyze the use of artificial intelligence for the screening and diagnosis of disease, and data and insights to the public health community.
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits
Responsibilities
Learn more about benefits at Google .
Collaborate with product managers, engineers, and cross-functional stakeholders to understand requirements, and provide creative, thoughtful solutions.
Communicate the user experience at various stages of the design process with wireframes, flow diagrams, storyboards, mockups, or high fidelity prototypes.
Integrate user feedback and business requirements into ongoing product experience updates.
Advocate for the prioritization of design centered changes, refinements, and improvements.
Then there is EEO boilerplate etc which we need to remove.
We need to decide sections: About the role (the "About The Job" paragraph). Responsibilities (list). Requirements/Qualifications: we have Minimum qualifications and Preferred qualifications. Could combine into a "Qualifications" section with sub-lists? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Qualifications, Pay, Benefits? Benefits mentioned: "equity + benefits". Also "Learn more about benefits at Google." There's no explicit benefits list. We have "equity + benefits" as part of pay line. So we could have a Benefits section? The posting mentions benefits generically but not specifics. According to rule: never create Benefits section unless posting actually states them. It says "equity + benefits" but not listing specifics. That's vague. Might be considered stating benefits exist but not details. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "equity + benefits". That's a statement that benefits are included, but not specifics. Is that enough to create a Benefits section? Probably yes, we can include a short
saying "Benefits include equity and other benefits (details available at Google)." But we must not invent details. We could just note that benefits are mentioned. However we need to avoid filler. Maybe better to not create a Benefits section because we don't have specific benefits listed. The phrase "equity + benefits" is part of compensation line. Could treat that as part of Pay section. So we can have Pay section that includes salary range, bonus target, equity, benefits. That seems appropriate.
Schedule: not mentioned, so omit.
Skills: not explicitly listed as a separate section; we could infer from qualifications but better not to create unless explicit. The posting does not have a "Skills" heading. So we skip Skills.
Thus sections: About the role, Responsibilities, Qualifications, Pay.
We need to use
for each section heading.
Inside sections: For prose use
. For lists use
- .
We need to preserve all substantive information. Let's extract.
About the role: The paragraph after "About The Job At Google, we ..." up to before "Individual pay is determined...". That's a long paragraph. We'll keep as
.
Responsibilities: list items after "Responsibilities". There's also a line "Learn more about benefits at Google ." That seems like a link instruction; maybe we should treat as part of responsibilities? It's a sentence about learning more about benefits. It's not a duty but a link. Could be considered part of responsibilities? Probably it's a note. We could include it as a responsibility item? It's not a duty but a reference. Might be considered boilerplate? It's not EEO but it's a link to benefits. Might be considered part of responsibilities? The instruction says remove application instructions. This is not application instruction but a link to benefits. Might be okay to keep as a responsibility item? It's not a duty. Safer to treat as a responsibility item? The list includes: Collaborate..., Communicate..., Integrate..., Advocate... plus "Learn more about benefits at Google ." That seems like a placeholder. I'd include it as a list item? It's not a duty but it's part of the responsibilities section. Could be considered a responsibility to learn about benefits? Not really. Might be better to omit it as it's not a substantive duty. However we must preserve ALL substantive information; this line is not substantive about the job duties. It's more like a link. Could be considered boilerplate? Not exactly EEO. But it's not a duty. I'd omit it to avoid filler. However we need to be careful not to remove substantive info. I'd keep it as a list item? It's not substantive. I'd omit.
Thus responsibilities list: 4 items.
Qualifications: We have Minimum qualifications and Preferred qualifications. Could combine into one list with headings? But we need to use
- for any list. Could have two subheadings? Not allowed as only
for section headings. Could embed or inside? Probably okay to have a
describing Minimum qualifications and Preferred qualifications then lists. But we must preserve all info. Let's do:
Qualifications
Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 6 years of interaction design experience in product design or UX design.
- Include a portfolio, website, or any other relevant link to your work in your resume (providing a viewable link or access instructions).
Preferred qualifications:
- Master's degree in Design, Human-Computer Interaction, Computer Science, a related field, or equivalent practical experience.
- 3 years of experience working in a complex, cross-functional organization.
- 2 years of experience leading design projects.
That preserves.
Pay: The line: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". We'll put as .
We should not include "Learn more about benefits at Google ." anywhere else.
We must not include any boilerplate like EEO etc.
Thus final HTML fragment:
About the role
At Google, we "Focus on the user and all else will follow." Our Interaction Designers transform complex tasks into intuitive, easy-to-use experiences for billions of people. From creating user flows and wireframes to building mockups and prototypes, you will envision and bring product experiences to life with an inspired, refined, and magical feel. You will join our multi-disciplinary UX team, collaborating with Engineering and Product Management, leveraging user insights to create industry-leading products. As an Interaction Designer, you'll apply user-centered design methods to craft industry-leading user experiences from concept to execution, working with design partners to evolve the Google design language to build beautiful, innovative products. In this role, you will design intuitive, trustworthy, and impactful experiences for emerging areas of Google Health that are essential to deliver proactive, personalized coaching that bridges everyday habits with longitudinal medical care. You will lead end-to-end user experience design projects within our three core consumer health pillars: Adaptive Lifestyle Coaching (nutrition, women’s health), Personalized Health Companion (Personal Health Records, lab results, immunization data, and clinical visit prep), and Proactive Health Guardian (passive vitals baselines, irregular rhythm notifications, continuous glucose monitoring, and early health risks). Serving as a critical bridge between UX, Product Management, Engineering, Data Science, and Clinical Research, you will translate complex physiological signals into clear, actionable, medically sound and emotionally resonant user experiences. Google for Health is a company-wide effort to help billions of people be healthier. We work toward this vision by meeting people in their everyday moments and empowering them to stay healthy and partnering with care teams to provide more accurate and accessible care. Our teams are applying our expertise and technology to improve health outcomes globally – with high-quality information and tools to help people manage their health and wellbeing, solutions to transform care delivery, research to catalyze the use of artificial intelligence for the screening and diagnosis of disease, and data and insights to the public health community.
Responsibilities
- Collaborate with product managers, engineers, and cross-functional stakeholders to understand requirements, and provide creative, thoughtful solutions.
- Communicate the user experience at various stages of the design process with wireframes, flow diagrams, storyboards, mockups, or high fidelity prototypes.
- Integrate user feedback and business requirements into ongoing product experience updates.
- Advocate for the priorit
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: Minimum qualifications: - Bachelor's degree or equivalent practical experience. - 6 years of interaction design experience in product design or UX design. - Include a portfolio, website, or any other relevant link to your work in your resume (providing a viewable link or access instructions). Preferred qualifications: - Master's degree in Design, Human-Computer Interaction, Computer Science, a related field, or equivalent practical experience. - 3 years of experience working in a complex, cross-functional organization. - 2 years of experience leading design projects. About The Job At Google, we "Focus on the user and all else will follow." Our Interaction Designers transform complex tasks into intuitive, easy-to-use experiences for billions of people. From creating user flows and wireframes to building mockups and prototypes, you will envision and bring product experiences to life with an inspired, refined, and magical feel. You will join our multi-disciplinary UX team, collaborating with Engineering and Product Management, leveraging user insights to create industry-leading products. As an Interaction Designer, you'll apply user-centered design methods to craft industry-leading user experiences from concept to execution, working with design partners to evolve the Google design language to build beautiful, innovative products. In this role, you will design intuitive, trustworthy, and impactful experiences for emerging areas of Google Health that are essential to deliver proactive, personalized coaching that bridges everyday habits with longitudinal medical care. You will lead end-to-end user experience design projects within our three core consumer health pillars: Adaptive Lifestyle Coaching (nutrition, women’s health), Personalized Health Companion (Personal Health Records, lab results, immunization data, and clinical visit prep), and Proactive Health Guardian (passive vitals baselines, irregular rhythm notifications, continuous glucose monitoring, and early health risks). Serving as a critical bridge between UX, Product Management, Engineering, Data Science, and Clinical Research, you will translate complex physiological signals into clear, actionable, medically sound and emotionally resonant user experiences. Google for Health is a company-wide effort to help billions of people be healthier. We work toward this vision by meeting people in their everyday moments and empowering them to stay healthy and partnering with care teams to provide more accurate and accessible care. Our teams are applying our expertise and technology to improve health outcomes globally – with high-quality information and tools to help people manage their health and wellbeing, solutions to transform care delivery, research to catalyze the use of artificial intelligence for the screening and diagnosis of disease, and data and insights to the public health community. Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits Responsibilities Learn more about benefits at Google . Collaborate with product managers, engineers, and cross-functional stakeholders to understand requirements, and provide creative, thoughtful solutions. Communicate the user experience at various stages of the design process with wireframes, flow diagrams, storyboards, mockups, or high fidelity prototypes. Integrate user feedback and business requirements into ongoing product experience updates. Advocate for the prioritization of design centered changes, refinements, and improvements. Then there is EEO boilerplate etc which we need to remove. We need to decide sections: About the role (the "About The Job" paragraph). Responsibilities (list). Requirements/Qualifications: we have Minimum qualifications and Preferred qualifications. Could combine into a "Qualifications" section with sub-lists? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Qualifications, Pay, Benefits? Benefits mentioned: "equity + benefits". Also "Learn more about benefits at Google." There's no explicit benefits list. We have "equity + benefits" as part of pay line. So we could have a Benefits section? The posting mentions benefits generically but not specifics. According to rule: never create Benefits section unless posting actually states them. It says "equity + benefits" but not listing specifics. That's vague. Might be considered stating benefits exist but not details. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "equity + benefits". That's a statement that benefits are included, but not specifics. Is that enough to create a Benefits section? Probably yes, we can include a short
saying "Benefits include equity and other benefits (details available at Google)." But we must not invent details. We could just note that benefits are mentioned. However we need to avoid filler. Maybe better to not create a Benefits section because we don't have specific benefits listed. The phrase "equity + benefits" is part of compensation line. Could treat that as part of Pay section. So we can have Pay section that includes salary range, bonus target, equity, benefits. That seems appropriate. Schedule: not mentioned, so omit. Skills: not explicitly listed as a separate section; we could infer from qualifications but better not to create unless explicit. The posting does not have a "Skills" heading. So we skip Skills. Thus sections: About the role, Responsibilities, Qualifications, Pay. We need to use
for each section heading. Inside sections: For prose use
. For lists use
- .
We need to preserve all substantive information. Let's extract.
About the role: The paragraph after "About The Job At Google, we ..." up to before "Individual pay is determined...". That's a long paragraph. We'll keep as
. Responsibilities: list items after "Responsibilities". There's also a line "Learn more about benefits at Google ." That seems like a link instruction; maybe we should treat as part of responsibilities? It's a sentence about learning more about benefits. It's not a duty but a link. Could be considered part of responsibilities? Probably it's a note. We could include it as a responsibility item? It's not a duty but a reference. Might be considered boilerplate? It's not EEO but it's a link to benefits. Might be considered part of responsibilities? The instruction says remove application instructions. This is not application instruction but a link to benefits. Might be okay to keep as a responsibility item? It's not a duty. Safer to treat as a responsibility item? The list includes: Collaborate..., Communicate..., Integrate..., Advocate... plus "Learn more about benefits at Google ." That seems like a placeholder. I'd include it as a list item? It's not a duty but it's part of the responsibilities section. Could be considered a responsibility to learn about benefits? Not really. Might be better to omit it as it's not a substantive duty. However we must preserve ALL substantive information; this line is not substantive about the job duties. It's more like a link. Could be considered boilerplate? Not exactly EEO. But it's not a duty. I'd omit it to avoid filler. However we need to be careful not to remove substantive info. I'd keep it as a list item? It's not substantive. I'd omit. Thus responsibilities list: 4 items. Qualifications: We have Minimum qualifications and Preferred qualifications. Could combine into one list with headings? But we need to use
- for any list. Could have two subheadings? Not allowed as only
for section headings. Could embed or
inside? Probably okay to have a
describing Minimum qualifications and Preferred qualifications then lists. But we must preserve all info. Let's do:
Qualifications
Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 6 years of interaction design experience in product design or UX design.
- Include a portfolio, website, or any other relevant link to your work in your resume (providing a viewable link or access instructions).
Preferred qualifications:
- Master's degree in Design, Human-Computer Interaction, Computer Science, a related field, or equivalent practical experience.
- 3 years of experience working in a complex, cross-functional organization.
- 2 years of experience leading design projects.
. We should not include "Learn more about benefits at Google ." anywhere else. We must not include any boilerplate like EEO etc. Thus final HTML fragment:
About the role
At Google, we "Focus on the user and all else will follow." Our Interaction Designers transform complex tasks into intuitive, easy-to-use experiences for billions of people. From creating user flows and wireframes to building mockups and prototypes, you will envision and bring product experiences to life with an inspired, refined, and magical feel. You will join our multi-disciplinary UX team, collaborating with Engineering and Product Management, leveraging user insights to create industry-leading products. As an Interaction Designer, you'll apply user-centered design methods to craft industry-leading user experiences from concept to execution, working with design partners to evolve the Google design language to build beautiful, innovative products. In this role, you will design intuitive, trustworthy, and impactful experiences for emerging areas of Google Health that are essential to deliver proactive, personalized coaching that bridges everyday habits with longitudinal medical care. You will lead end-to-end user experience design projects within our three core consumer health pillars: Adaptive Lifestyle Coaching (nutrition, women’s health), Personalized Health Companion (Personal Health Records, lab results, immunization data, and clinical visit prep), and Proactive Health Guardian (passive vitals baselines, irregular rhythm notifications, continuous glucose monitoring, and early health risks). Serving as a critical bridge between UX, Product Management, Engineering, Data Science, and Clinical Research, you will translate complex physiological signals into clear, actionable, medically sound and emotionally resonant user experiences. Google for Health is a company-wide effort to help billions of people be healthier. We work toward this vision by meeting people in their everyday moments and empowering them to stay healthy and partnering with care teams to provide more accurate and accessible care. Our teams are applying our expertise and technology to improve health outcomes globally – with high-quality information and tools to help people manage their health and wellbeing, solutions to transform care delivery, research to catalyze the use of artificial intelligence for the screening and diagnosis of disease, and data and insights to the public health community.
Responsibilities
- Collaborate with product managers, engineers, and cross-functional stakeholders to understand requirements, and provide creative, thoughtful solutions.
- Communicate the user experience at various stages of the design process with wireframes, flow diagrams, storyboards, mockups, or high fidelity prototypes.
- Integrate user feedback and business requirements into ongoing product experience updates.
- Advocate for the priorit
- for any list. Could have two subheadings? Not allowed as only