Senior GCP Architect
for section headings.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details.
Let's extract content.
About the role paragraph: "As a Senior GCP Architect (Lead Cloud Infrastructure Engineer II) at Deloitte, you will lead the architecture and delivery of secure, scalable Google Cloud solutions for Public Sector customers. You will serve as a senior technical advisor, guide cloud modernization and operational planning, and coordinate resolution of complex technical issues across customer and delivery teams. You will help customers achieve reliable, secure cloud outcomes in complex public-sector environments. This remote role is available to candidates who can work from within the continental United States. Recruiting for this role ends on 11/21/2026."
We could split into maybe two paragraphs but okay.
Responsibilities: bullet list:
- Lead the architecture and delivery of secure, scalable Google Cloud solutions; establish architecture standards, technical roadmaps, and implementation plans.
- Serve as a senior technical advisor to customer engineers, technology leaders, and executives; evaluate architecture and product tradeoffs and recommend integration, infrastructure, security, networking, and application strategies.
- Provide hands-on engineering leadership through coding, prototyping, troubleshooting, and technical validation.
- Lead cloud modernization, migration, and transformation initiatives; identify and manage architecture risks, technical dependencies, and delivery constraints.
- Coordinate with client engineering teams to resolve complex product and technical issues; review technical deliverables and mentor junior architects and engineers.
That's from "Work you'll do" section.
Requirements: Might include citizenship, clearance, degree, years experience, travel, legal authorization. Also maybe "Must be a U.S. citizen and able to obtain a U.S. Government Top Secret/Sensitive Compartmented Information (TS/SCI) security clearance." "Bachelor's degree or have 12+ years of professional experience in cloud infrastructure, cloud operations, software development, or technical consulting." "8+ years of experience in enterprise or government cloud architecture, technical consulting, or professional services, including 5+ years of hands-on software engineering experience using Python or C++." "Experience leading cloud deployments, migrations, or modernization programs and advising engineering teams and senior executives on cloud architecture, infrastructure, or modernization decisions." "Experience designing, implementing, or operating Google Cloud infrastructure, networking, security, data, application, and Kubernetes services." "Hold a current Google Cloud Professional certification in at least one of the following: Professional Cloud Architect; Professional Cloud Database Engineer; Professional Cloud Developer; Professional Cloud DevOps Engineer; Professional Cloud Network Engineer; Professional Cloud Security Engineer; Professional Data Engineer; Professional Machine Learning Engineer; or Professional Security Operations Engineer." "Ability to travel up to 10%, on average, based on the work you do and the clients and industries/sectors you serve." "Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future."
We could treat these as Requirements.
Qualifications: Might be overlapping with Requirements. But the posting lumps "Qualifications Required:" then list. Could treat that as Qualifications. However we already used Requirements for similar items. To avoid duplication, we need to decide which section to use. The instruction: include a section ONLY when posting has real, specific content for it. We have both Requirements and Qualifications content. Could split: Requirements: citizenship, clearance, degree, experience, travel, legal auth. Qualifications: certifications, maybe also the experience leading deployments etc. But there is overlap. Safer: treat the "Qualifications Required:" block as Qualifications, and treat the earlier bullet about "Ability to work independently..." as Skills. The "Required" block includes many items; we can put them under Qualifications.
Skills: The list under "A successful candidate would possess these skills:" includes soft skills.
Thus:
- About the role: prose.
- Responsibilities: ul.
- Qualifications: ul (or maybe mix of prose and list). The qualifications block includes multiple items, some are sentences with semicolons. Could break into list items each sentence.
- Skills: ul.
- Pay: prose with wage range and discretionary annual incentive.
We should not include Benefits section because not explicitly stated (though incentive program could be considered benefit but it's compensation). We'll put incentive under Pay.
Schedule: not present.
Now ensure we don't include boilerplate like EEO etc. Not present.
Now produce HTML fragment:
About the role
As a Senior GCP Architect (Lead Cloud Infrastructure Engineer II) at Deloitte, you will lead the architecture and delivery of secure, scalable Google Cloud solutions for Public Sector customers. You will serve as a senior technical advisor, guide cloud modernization and operational planning, and coordinate resolution of complex technical issues across customer and delivery teams. You will help customers achieve reliable, secure cloud outcomes in complex public-sector environments. This remote role is available to candidates who can work from within the continental United States. Recruiting for this role ends on 11/21/2026.
Responsibilities
- Lead the architecture and delivery of secure, scalable Google Cloud solutions; establish architecture standards, technical roadmaps, and implementation plans.
- Serve as a senior technical advisor to customer engineers, technology leaders, and executives; evaluate architecture and product tradeoffs and recommend integration, infrastructure, security, networking, and application strategies.
- Provide hands-on engineering leadership through coding, prototyping, troubleshooting, and technical validation.
- Lead cloud modernization, migration, and transformation initiatives; identify and manage architecture risks, technical dependencies, and delivery constraints.
- Coordinate with client engineering teams to resolve complex product and technical issues; review technical deliverables and mentor junior architects and engineers.
Qualifications
- Must be a U.S. citizen and able to obtain a U.S. Government Top Secret/Sensitive Compartmented Information (TS/SCI) security clearance.
- Bachelor's degree or have 12+ years of professional experience in cloud infrastructure, cloud operations, software development, or technical consulting.
- 8+ years of experience in enterprise or government cloud architecture, technical consulting, or professional services, including 5+ years of hands-on software engineering experience using Python or C++.
- Experience leading cloud deployments, migrations, or modernization programs and advising engineering teams and senior executives on cloud architecture, infrastructure, or modernization decisions.
- Experience designing, implementing, or operating Google Cloud infrastructure, networking, security, data, application, and Kubernetes services.
- Hold a current Google Cloud Professional certification in at least one of the following: Professional Cloud Architect; Professional Cloud Database Engineer; Professional Cloud Developer; Professional Cloud DevOps Engineer; Professional Cloud Network Engineer; Professional Cloud Security Engineer; Professional Data Engineer; Professional Machine Learning Engineer; or Professional Security Operations Engineer.
- Ability to travel up to 10%, on average, based on the work you do and the clients and industries/sectors you serve.
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
Skills
- Ability to work independently and collaborate as part of a team
- Effective written and verbal communication skills
- Meticulous attention to detail and quality of work product
- Ability to build and sustain professional relationships
- Ability to lead projects or workstreams
- Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment
- Strong interpersonal skills and professional demeanor
- Ability to meet deadlines
- Ability to mentor and provide clear guidance to others
Pay
A reasonable estimate of the current range is $135,000 to $205,000. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
We should not include any extra text. Ensure no markdown fences. Just raw HTML.
Check for any repeated content: we included all details. Did we miss any? The posting also mentions "The Team At Deloitte, AI & Engineering leverages engineering capabilities..." That's substantive but not covered in any section. Should we include it? It's about the team description. Could be part of About the role or a separate section like "About the team". But we only have predefined headings; we could add it under About the role as additional paragraph. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other headings, but says use those for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings if we have content for those sections. It doesn't prohibit other headings, but better to stick to those. The team description could be included in About the role paragraph.
Let's add a second paragraph under About the role: "At Deloitte, AI & Engineering leverages engineering capabilities to build, deploy, and operate integrated, sector-focused solutions across software, data, artificial intelligence, networks, and hybrid cloud infrastructure. Our teams help clients modernize technology and data platforms, improve mission-critical operations, and enable business advantage through scalable engineering solutions. We tailor our delivery approach to each client's priorities, operating environment, and transformation goals."
Thus About the role will have two
elements.
Now ensure we didn't miss any other content: The posting also mentions "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case." That's substantive about pay. Should we include under Pay? Yes, we can add that as prose.
Thus Pay section will
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details. Let's extract content. About the role paragraph: "As a Senior GCP Architect (Lead Cloud Infrastructure Engineer II) at Deloitte, you will lead the architecture and delivery of secure, scalable Google Cloud solutions for Public Sector customers. You will serve as a senior technical advisor, guide cloud modernization and operational planning, and coordinate resolution of complex technical issues across customer and delivery teams. You will help customers achieve reliable, secure cloud outcomes in complex public-sector environments. This remote role is available to candidates who can work from within the continental United States. Recruiting for this role ends on 11/21/2026." We could split into maybe two paragraphs but okay. Responsibilities: bullet list: - Lead the architecture and delivery of secure, scalable Google Cloud solutions; establish architecture standards, technical roadmaps, and implementation plans. - Serve as a senior technical advisor to customer engineers, technology leaders, and executives; evaluate architecture and product tradeoffs and recommend integration, infrastructure, security, networking, and application strategies. - Provide hands-on engineering leadership through coding, prototyping, troubleshooting, and technical validation. - Lead cloud modernization, migration, and transformation initiatives; identify and manage architecture risks, technical dependencies, and delivery constraints. - Coordinate with client engineering teams to resolve complex product and technical issues; review technical deliverables and mentor junior architects and engineers. That's from "Work you'll do" section. Requirements: Might include citizenship, clearance, degree, years experience, travel, legal authorization. Also maybe "Must be a U.S. citizen and able to obtain a U.S. Government Top Secret/Sensitive Compartmented Information (TS/SCI) security clearance." "Bachelor's degree or have 12+ years of professional experience in cloud infrastructure, cloud operations, software development, or technical consulting." "8+ years of experience in enterprise or government cloud architecture, technical consulting, or professional services, including 5+ years of hands-on software engineering experience using Python or C++." "Experience leading cloud deployments, migrations, or modernization programs and advising engineering teams and senior executives on cloud architecture, infrastructure, or modernization decisions." "Experience designing, implementing, or operating Google Cloud infrastructure, networking, security, data, application, and Kubernetes services." "Hold a current Google Cloud Professional certification in at least one of the following: Professional Cloud Architect; Professional Cloud Database Engineer; Professional Cloud Developer; Professional Cloud DevOps Engineer; Professional Cloud Network Engineer; Professional Cloud Security Engineer; Professional Data Engineer; Professional Machine Learning Engineer; or Professional Security Operations Engineer." "Ability to travel up to 10%, on average, based on the work you do and the clients and industries/sectors you serve." "Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future." We could treat these as Requirements. Qualifications: Might be overlapping with Requirements. But the posting lumps "Qualifications Required:" then list. Could treat that as Qualifications. However we already used Requirements for similar items. To avoid duplication, we need to decide which section to use. The instruction: include a section ONLY when posting has real, specific content for it. We have both Requirements and Qualifications content. Could split: Requirements: citizenship, clearance, degree, experience, travel, legal auth. Qualifications: certifications, maybe also the experience leading deployments etc. But there is overlap. Safer: treat the "Qualifications Required:" block as Qualifications, and treat the earlier bullet about "Ability to work independently..." as Skills. The "Required" block includes many items; we can put them under Qualifications. Skills: The list under "A successful candidate would possess these skills:" includes soft skills. Thus: - About the role: prose. - Responsibilities: ul. - Qualifications: ul (or maybe mix of prose and list). The qualifications block includes multiple items, some are sentences with semicolons. Could break into list items each sentence. - Skills: ul. - Pay: prose with wage range and discretionary annual incentive. We should not include Benefits section because not explicitly stated (though incentive program could be considered benefit but it's compensation). We'll put incentive under Pay. Schedule: not present. Now ensure we don't include boilerplate like EEO etc. Not present. Now produce HTML fragment:
About the role
As a Senior GCP Architect (Lead Cloud Infrastructure Engineer II) at Deloitte, you will lead the architecture and delivery of secure, scalable Google Cloud solutions for Public Sector customers. You will serve as a senior technical advisor, guide cloud modernization and operational planning, and coordinate resolution of complex technical issues across customer and delivery teams. You will help customers achieve reliable, secure cloud outcomes in complex public-sector environments. This remote role is available to candidates who can work from within the continental United States. Recruiting for this role ends on 11/21/2026.
Responsibilities
- Lead the architecture and delivery of secure, scalable Google Cloud solutions; establish architecture standards, technical roadmaps, and implementation plans.
- Serve as a senior technical advisor to customer engineers, technology leaders, and executives; evaluate architecture and product tradeoffs and recommend integration, infrastructure, security, networking, and application strategies.
- Provide hands-on engineering leadership through coding, prototyping, troubleshooting, and technical validation.
- Lead cloud modernization, migration, and transformation initiatives; identify and manage architecture risks, technical dependencies, and delivery constraints.
- Coordinate with client engineering teams to resolve complex product and technical issues; review technical deliverables and mentor junior architects and engineers.
Qualifications
- Must be a U.S. citizen and able to obtain a U.S. Government Top Secret/Sensitive Compartmented Information (TS/SCI) security clearance.
- Bachelor's degree or have 12+ years of professional experience in cloud infrastructure, cloud operations, software development, or technical consulting.
- 8+ years of experience in enterprise or government cloud architecture, technical consulting, or professional services, including 5+ years of hands-on software engineering experience using Python or C++.
- Experience leading cloud deployments, migrations, or modernization programs and advising engineering teams and senior executives on cloud architecture, infrastructure, or modernization decisions.
- Experience designing, implementing, or operating Google Cloud infrastructure, networking, security, data, application, and Kubernetes services.
- Hold a current Google Cloud Professional certification in at least one of the following: Professional Cloud Architect; Professional Cloud Database Engineer; Professional Cloud Developer; Professional Cloud DevOps Engineer; Professional Cloud Network Engineer; Professional Cloud Security Engineer; Professional Data Engineer; Professional Machine Learning Engineer; or Professional Security Operations Engineer.
- Ability to travel up to 10%, on average, based on the work you do and the clients and industries/sectors you serve.
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
Skills
- Ability to work independently and collaborate as part of a team
- Effective written and verbal communication skills
- Meticulous attention to detail and quality of work product
- Ability to build and sustain professional relationships
- Ability to lead projects or workstreams
- Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment
- Strong interpersonal skills and professional demeanor
- Ability to meet deadlines
- Ability to mentor and provide clear guidance to others
Pay
A reasonable estimate of the current range is $135,000 to $205,000. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
We should not include any extra text. Ensure no markdown fences. Just raw HTML. Check for any repeated content: we included all details. Did we miss any? The posting also mentions "The Team At Deloitte, AI & Engineering leverages engineering capabilities..." That's substantive but not covered in any section. Should we include it? It's about the team description. Could be part of About the role or a separate section like "About the team". But we only have predefined headings; we could add it under About the role as additional paragraph. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other headings, but says use those for section headings. It says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings if we have content for those sections. It doesn't prohibit other headings, but better to stick to those. The team description could be included in About the role paragraph. Let's add a second paragraph under About the role: "At Deloitte, AI & Engineering leverages engineering capabilities to build, deploy, and operate integrated, sector-focused solutions across software, data, artificial intelligence, networks, and hybrid cloud infrastructure. Our teams help clients modernize technology and data platforms, improve mission-critical operations, and enable business advantage through scalable engineering solutions. We tailor our delivery approach to each client's priorities, operating environment, and transformation goals." Thus About the role will have two
elements. Now ensure we didn't miss any other content: The posting also mentions "The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case." That's substantive about pay. Should we include under Pay? Yes, we can add that as prose. Thus Pay section will