Compliance Operations Program Manager, Risk, Compliance and Integrity
Google · Chicago, IL · 1 mo ago
On-siteProject ManagementFull-time
We need to output HTML fragment with headings .
- Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $111000 - $159000 (USD) + 15% bonus target + equity + benefits". So we have pay range and bonus etc. Should we create Pay section? Yes, we have specific pay info. So include Pay section with that info.
- Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
- Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create unless explicit. The instructions: include a section ONLY when the posting has real, specific content for it. So we should not create Skills unless there is explicit skills list. There's no explicit skills section. So omit.
- Qualifications: We have Minimum qualifications and Preferred qualifications. Could combine into Qualifications section with subheadings? But we only allowed headings for section headings. Could we have subheadings? Not specified; but we could just list them as
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract from posting. Let's parse content. The posting includes: - Location note: "This role may also be located in our Playa Vista, CA campus." Also location options: Austin, TX; Chicago, IL; Los Angeles, CA; Washington D.C., DC. Also mention about Fair Chance Ordinance etc. That's boilerplate? It's about legal compliance; we should remove EEO/equal-opportunity/boilerplate. The instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the Fair Chance Ordinance lines, the Washington state law benefits highlight? Actually they mention benefits for Washington state law: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's a preamble to benefits; we can keep benefits details but remove the preamble if it's just legal. Probably we can keep benefits details. - Benefits list: Health, dental, vision, life, disability insurance; Retirement Benefits: 401(k) with company match; Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment; Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance; Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks; Baby Bonding Leave: 18 weeks; Holidays: 13 paid days per year. - Minimum qualifications: Bachelor's degree or equivalent practical experience; 3 years of experience in program or project management; 2 years of experience working with data analytics tools and reporting platforms. - Preferred qualifications: Program Management certification or experience in program management with a technology company; 3 years of experience managing cross-functional or cross-team projects; Experience operating in a compliance, regulatory, or risk management environment; Experience in stakeholder management; Demonstrated ability to adapt to novel technologies to solve data and process problems, particularly in the legal/compliance space. - About The Job: description paragraph(s). We'll put under About the role (or About The Job). Use heading About the role. - Responsibilities: list bullet points after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google . Partner directly with senior leads ..." So responsibilities list includes several bullet-like sentences. We'll extract each as
for section headings. Could we have subheadings? Not specified; but we could just list them as - under Qualifications. Might be okay to separate Minimum and Preferred as separate
? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a Qualifications section. Inside we can list both minimum and preferred as items, maybe with labels. But we must preserve all substantive information; we can include both.
- Requirements: Might be similar to qualifications; but we have Minimum qualifications and Preferred qualifications. Could treat Requirements as Minimum qualifications? The list includes Requirements as a possible heading. We could put Minimum qualifications under Requirements, and Preferred under Qualifications? But we have both headings available. To avoid thin sections, better to combine into Qualifications. However we have both Minimum and Preferred; we could put Minimum under Requirements and Preferred under Qualifications. But that splits info. The instruction: Prefer a few substantive sections over many thin ones. So better to have one Qualifications section containing both minimum and preferred, maybe with sub-bullets labeled. That's still one section.
- About the role: we have About The Job paragraph.
- Responsibilities: we have list.
- Benefits: we have list.
- Pay: we have info.
Now we need to strip boilerplate: EEO statements, accommodation request, etc. Also remove lines like "Learn more about benefits at Google ." (that's part of responsibilities line). Actually the responsibilities line begins with "Responsibilities Learn more about benefits at Google . Partner directly with senior leads..." That seems like a mistake; we should remove "Learn more about benefits at Google ." as it's likely a link placeholder. So responsibilities start after that.
Also remove "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's part of Pay section; we can keep that as prose.
Now produce HTML.
Structure:
About the role
... (the About The Job paragraph(s))...
Responsibilities
- Partner directly with senior leads to actively balancing daily core compliance operations with the rapid development of newly automated solutions.
- Execute day-to-day programmatic tracking of end-to-end compliance processes, ensuring timely project delivery and proactively identifying operational risks across the portfolio.
- Evaluate, test and validate emerging technical tooling, actively assisting the organization in transitioning from manual compliance mapping to highly scalable, AI-driven processes.
- Translate complex regulatory and compliance requirements into structured data formats to directly support downstream engineering and automation initiatives.
- Develop creative, agile operational solutions using internal business intelligence tools to unblock process bottlenecks and continuously improve overall workflow velocity.
- Engage in continuous process improvement, navigating ambiguous situations and adapting to changing business contexts to deliver high-quality outcomes.
Qualifications
- Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 3 years of experience in program or project management.
- 2 years of experience working with data analytics tools and reporting platforms.
- Preferred qualifications:
- Program Management certification or experience in program management with a technology company.
- 3 years of experience managing cross-functional or cross-team projects.
- Experience operating in a compliance, regulatory, or risk management environment.
- Experience in stakeholder management.
- Demonstrated ability to adapt to novel technologies to solve data and process problems, particularly in the legal/compliance space.
But we used nested which is okay. However we need to ensure we only use - for any list of duties/requirements/benefits. Using nested lists is still
- . Acceptable.
Alternatively we could flatten: list each qualification with label. But nested is fine.
Benefits
- Health, dental, vision, life, disability insurance
- Retirement Benefits: 401(k) with company match
- Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holidays: 13 paid days per year
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $111000 - $159000 (USD) + 15% bonus target + equity + benefits
We should also maybe include location info? Not a section; could be a short paragraph under About the role? The location note: "This role may also be located in our Playa Vista, CA campus." and location options list. That's substantive info about location. Should we include? The instructions: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep location info. Where to put? Could be a short paragraph under About the role or maybe a separate section? There's no heading for Location in the allowed list. So we can incorporate into About the role paragraph.
Add location note after About The Job description.
Thus About the role paragraph: combine the About The Job text plus location note.
Let's extract About The Job paragraph:
"The Risk, Compliance and Integrity (RCI) Process Transformation team operates at the critical intersection of regulatory compliance and technological innovation. In an era defined by rapid AI expansion and complex global regulations, our team is tasked with transforming Google’s compliance operations from a manual, human-heavy process to a highly scalable, AI-first model. We act as the tip of the spear for the regulatory lifecycle ingesting and deconstructing new obligations so downstream product teams can innovate safely and quickly. Our mission is to maintain the highest standard of risk mitigation in our day-to-day operations while pushing the boundaries of automation, AI integration, and process design. As a Compliance Operations Program Manager, you will serve as the agile, operational partner to our executive technical leadership during a pivotal transformation within the Risk, Compliance and Integrity (RCI) organization. You will actively balance the immediate needs of running our core compliance operations with the strategic imperative to test, evaluate, and implement next-generation automated tooling. Operating as a flexible, tech-curious problem solver, you will bridge the gap between day-to-day execution and future-state automation. While you don't need to be a software engineer, your technical intuition, creativity with data, and ability to translate complex workflows into scalable processes will directly accelerate Google's transition toward an AI-driven regulatory compliance model."
Then location note: "This role may also be located in our Playa Vista, CA campus. Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees. Benefits for this role include: ..." Wait that part includes benefits preamble; we already have benefits section. The location note also includes the Fair Chance Ordinance lines (legal) which we should remove. Also the Washington state law line is legal preamble; we can remove. The benefits list we already captured.
Thus location info: "This role may also be located in our Playa Vista, CA campus." Also the list of possible work locations: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Austin, TX, USA; Chicago, IL, USA; Los Angeles, CA, USA; Washington D.C., DC, USA." That's also location info. We should keep that.
Thus we can add a sentence: "This role may also be located in our Playa Vista, CA campus
? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have a Qualifications section. Inside we can list both minimum and preferred as items, maybe with labels. But we must preserve all substantive information; we can include both.
- Requirements: Might be similar to qualifications; but we have Minimum qualifications and Preferred qualifications. Could treat Requirements as Minimum qualifications? The list includes Requirements as a possible heading. We could put Minimum qualifications under Requirements, and Preferred under Qualifications? But we have both headings available. To avoid thin sections, better to combine into Qualifications. However we have both Minimum and Preferred; we could put Minimum under Requirements and Preferred under Qualifications. But that splits info. The instruction: Prefer a few substantive sections over many thin ones. So better to have one Qualifications section containing both minimum and preferred, maybe with sub-bullets labeled. That's still one section.
- About the role: we have About The Job paragraph.
- Responsibilities: we have list.
- Benefits: we have list.
- Pay: we have info.
Now we need to strip boilerplate: EEO statements, accommodation request, etc. Also remove lines like "Learn more about benefits at Google ." (that's part of responsibilities line). Actually the responsibilities line begins with "Responsibilities Learn more about benefits at Google . Partner directly with senior leads..." That seems like a mistake; we should remove "Learn more about benefits at Google ." as it's likely a link placeholder. So responsibilities start after that.
Also remove "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's part of Pay section; we can keep that as prose.
Now produce HTML.
Structure:
About the role
About the role
... (the About The Job paragraph(s))...
Responsibilities
- Partner directly with senior leads to actively balancing daily core compliance operations with the rapid development of newly automated solutions.
- Execute day-to-day programmatic tracking of end-to-end compliance processes, ensuring timely project delivery and proactively identifying operational risks across the portfolio.
- Evaluate, test and validate emerging technical tooling, actively assisting the organization in transitioning from manual compliance mapping to highly scalable, AI-driven processes.
- Translate complex regulatory and compliance requirements into structured data formats to directly support downstream engineering and automation initiatives.
- Develop creative, agile operational solutions using internal business intelligence tools to unblock process bottlenecks and continuously improve overall workflow velocity.
- Engage in continuous process improvement, navigating ambiguous situations and adapting to changing business contexts to deliver high-quality outcomes.
Qualifications
- Minimum qualifications:
- Bachelor's degree or equivalent practical experience.
- 3 years of experience in program or project management.
- 2 years of experience working with data analytics tools and reporting platforms.
- Preferred qualifications:
- Program Management certification or experience in program management with a technology company.
- 3 years of experience managing cross-functional or cross-team projects.
- Experience operating in a compliance, regulatory, or risk management environment.
- Experience in stakeholder management.
- Demonstrated ability to adapt to novel technologies to solve data and process problems, particularly in the legal/compliance space.
- which is okay. However we need to ensure we only use
- for any list of duties/requirements/benefits. Using nested lists is still
- . Acceptable.
Alternatively we could flatten: list each qualification with label. But nested is fine.
Benefits
- Health, dental, vision, life, disability insurance
- Retirement Benefits: 401(k) with company match
- Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holidays: 13 paid days per year
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $111000 - $159000 (USD) + 15% bonus target + equity + benefits
We should also maybe include location info? Not a section; could be a short paragraph under About the role? The location note: "This role may also be located in our Playa Vista, CA campus." and location options list. That's substantive info about location. Should we include? The instructions: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep location info. Where to put? Could be a short paragraph under About the role or maybe a separate section? There's no heading for Location in the allowed list. So we can incorporate into About the role paragraph. Add location note after About The Job description. Thus About the role paragraph: combine the About The Job text plus location note. Let's extract About The Job paragraph: "The Risk, Compliance and Integrity (RCI) Process Transformation team operates at the critical intersection of regulatory compliance and technological innovation. In an era defined by rapid AI expansion and complex global regulations, our team is tasked with transforming Google’s compliance operations from a manual, human-heavy process to a highly scalable, AI-first model. We act as the tip of the spear for the regulatory lifecycle ingesting and deconstructing new obligations so downstream product teams can innovate safely and quickly. Our mission is to maintain the highest standard of risk mitigation in our day-to-day operations while pushing the boundaries of automation, AI integration, and process design. As a Compliance Operations Program Manager, you will serve as the agile, operational partner to our executive technical leadership during a pivotal transformation within the Risk, Compliance and Integrity (RCI) organization. You will actively balance the immediate needs of running our core compliance operations with the strategic imperative to test, evaluate, and implement next-generation automated tooling. Operating as a flexible, tech-curious problem solver, you will bridge the gap between day-to-day execution and future-state automation. While you don't need to be a software engineer, your technical intuition, creativity with data, and ability to translate complex workflows into scalable processes will directly accelerate Google's transition toward an AI-driven regulatory compliance model." Then location note: "This role may also be located in our Playa Vista, CA campus. Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees. Benefits for this role include: ..." Wait that part includes benefits preamble; we already have benefits section. The location note also includes the Fair Chance Ordinance lines (legal) which we should remove. Also the Washington state law line is legal preamble; we can remove. The benefits list we already captured. Thus location info: "This role may also be located in our Playa Vista, CA campus." Also the list of possible work locations: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Austin, TX, USA; Chicago, IL, USA; Los Angeles, CA, USA; Washington D.C., DC, USA." That's also location info. We should keep that. Thus we can add a sentence: "This role may also be located in our Playa Vista, CA campus
- . Acceptable.
Alternatively we could flatten: list each qualification with label. But nested is fine.