GCP Cloud Architect
Deloitte · Hermitage, TN · 3 wk ago
Hybrid$119k–$198k/yrFull-time
We need to output HTML fragment with sections: Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
First, there is an opening paragraph: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced GCP Cloud Architect, you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery."
That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
First, there is an opening paragraph: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced GCP Cloud Architect, you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery."
That's about the role. So we can have About the role
with that paragraph.
Then "Work You'll Do/Responsibilities" heading. Then list of responsibilities: "As a GCP Cloud Architect, you will design and implement defined components of enterprise Google Cloud solutions. The successful candidate would possess these skills:" then bullet list: "Work with customer engineers to evaluate technical requirements and design options.Develop code, prototypes, configurations, and technical documentation.Support application integration, cloud infrastructure, networking, security, and migration activities.Test and validate solutions against functional, security, performance, and reliability requirements.Troubleshoot technical issues and coordinate resolution with Google Cloud engineering teams.Document architecture decisions, risks, dependencies, and implementation recommendations.Escalate complex architecture decisions and delivery risksAbility to work independently and collaborate as part of a teamEffective written and verbal communication skillsMeticulous attention to detail and quality of work productAbility to build and sustain professional relationshipsAbility to lead projects or workstreamsAbility to manage and prioritize multiple tasks in a fast-paced and dynamic environmentStrong interpersonal skills and professional demeanorAbility to meet deadlinesAbility to provide clear guidance to others"
These are responsibilities/skills. We need to separate responsibilities vs skills? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose.
We have responsibilities list (duties). Also there is a list of skills after "The successful candidate would possess these skills:" which includes many items. Those could be considered Skills section. However the posting lumps them together. We could treat the bullet list as responsibilities (duties) and then maybe a Skills section for the abilities like communication, attention to detail, etc. But the bullet list includes both duties and abilities. Might be better to split: Responsibilities: design and implement defined components... etc. Skills: list of abilities.
Let's parse bullet items:
- Work with customer engineers to evaluate technical requirements and design options.
- Develop code, prototypes, configurations, and technical documentation.
- Support application integration, cloud infrastructure, networking, security, and migration activities.
- Test and validate solutions against functional, security, performance, and reliability requirements.
- Troubleshoot technical issues and coordinate resolution with Google Cloud engineering teams.
- Document architecture decisions, risks, dependencies, and implementation recommendations.
- Escalate complex architecture decisions and delivery risks
- 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 provide clear guidance to others
We could treat first 7 as responsibilities (duties) and the rest as skills. However the instruction says "Use
- for any list of duties/requirements/benefits". So we can have separate lists for responsibilities and skills.
Now after responsibilities, there is "The Team AI & Engineering leverages cutting-edge engineering capabilities..." That's description of team, could be part of About the role or maybe a separate section? Not required headings. Could be included in About the role paragraph.
Then "Qualifications Required" heading. Then list:
- 5+yrs of experience in GCP cloud architecture, technical consulting, professional services, technical project management, or enterprise technology delivery.
- 3+yrs of hands-on software-engineering experience using an object-oriented language such as Python or C++
- 5+yrs of experience working as a hands-on or "keyboard" engineer.
- Familiarity with services such as Compute Engine, Cloud Storage, Cloud SQL, Cloud Networking, and Google Kubernetes Engine.
- Active Google Cloud professional-level certification
- Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or equivalent professional experience.
- Ability to obtain a U.S. Government TS/SCI security clearance
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
- Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve
These are qualifications/requirements. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since they are labeled "Qualifications Required", we could use Qualifications section. Requirements could be similar but we can just use Qualifications.
Then after qualifications, there is "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. A reasonable estimate of the current range is $118,700 to $197,900."
That's Pay information. So we need a Pay section with that paragraph.
Then "Recruiting tips ..." that's boilerplate/application instructions, we should remove.
Then "Benefits This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM". That's a benefits statement but no details. It says to view document. There's no specific benefit details. According to rules: never create Benefits section unless posting actually states them. It does mention benefits but only references a document; no concrete benefits listed. Should we include Benefits? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Here benefits are not specific; just a reference. Likely we should not include Benefits section because no specific benefits listed.
Then "Our people and culture ..." that's fluff, could be considered About the role? Might be considered generic boilerplate; but it's about culture. Could be included in About the role? Might be okay but it's not specific to role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is culture description; not boilerplate but maybe considered generic marketing. Might be okay to keep as part of About the role? However it's not directly about the role. Might be considered filler. Safer to omit.
Then "Professional development ..." also generic.
Then "Qualified applicants with criminal histories..." that's EEO/legal; remove.
Then "You may also be eligible to participate in a discretionary annual incentive program..." that's about compensation but maybe part of Pay? It mentions discretionary annual incentive program. Could be included in Pay section as additional detail. It's specific: discretionary annual incentive program. So we could add that to Pay section.
Thus final sections:
- About the role: includes initial paragraph + team description + maybe culture? We'll keep initial paragraph and team description.
- Responsibilities: list of first 7 duties.
- Skills: list of remaining abilities.
- Qualifications: list of qualifications.
- Pay: wage range paragraph + discretionary annual incentive program sentence.
We should not include Benefits, Schedule.
Check for any Schedule info: none.
Now format HTML.
We need to wrap each section:
About the role
...
etc.
For lists: - ...
.
Make sure to preserve all substantive information, not invent or summarize away detail.
Let's craft About the role paragraph:
Combine: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced GCP Cloud Architect, you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery. The Team AI & Engineering leverages cutting-edge engineering capabilities to build, deploy, and operate integrated/verticalized sector solutions in software, data, AI, network, and hybrid cloud infrastructure. These solutions are powered by engineering for business advantage, transforming mission-critical operations. We enable clients to stay ahead with the latest advancements by transforming engineering teams and modernizing technology & data platforms. Our delivery models are tailored to meet each client's unique requirements."
That's all substantive.
Now Responsibilities list (first 7):
- Work with customer engineers to evaluate technical requirements and design options.
- Develop code, prototypes, configurations, and technical documentation.
- Support application integration, cloud infrastructure, networking, security, and migration activities.
- Test and validate solutions against functional, security, performance, and reliability requirements.
- Troubleshoot technical issues and coordinate resolution with Google Cloud engineering teams.
- Document architecture decisions, risks, dependencies, and implementation recommendations.
- Escalate complex architecture decisions and delivery risks
Now Skills list (remaining):
- 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 provide clear guidance to others
Now Qualifications list:
- 5+yrs of experience in GCP cloud architecture, technical consulting, professional services, technical project management, or enterprise technology delivery.
- 3+yrs of hands-on software-engineering experience using an object-oriented language such as Python or C++
- 5+yrs of experience working as a hands-on or "keyboard" engineer.
- Familiarity with services such as Compute Engine, Cloud Storage, Cloud SQL, Cloud Networking, and Google Kubernetes Engine.
- Active Google Cloud professional-level certification
- Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or equivalent professional experience.
- Ability to obtain a U.S. Government TS/SCI security clearance
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
- Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve
Now Pay paragraph:
"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
- for any list of duties/requirements/benefits, and
for prose. We have responsibilities list (duties). Also there is a list of skills after "The successful candidate would possess these skills:" which includes many items. Those could be considered Skills section. However the posting lumps them together. We could treat the bullet list as responsibilities (duties) and then maybe a Skills section for the abilities like communication, attention to detail, etc. But the bullet list includes both duties and abilities. Might be better to split: Responsibilities: design and implement defined components... etc. Skills: list of abilities. Let's parse bullet items: - Work with customer engineers to evaluate technical requirements and design options. - Develop code, prototypes, configurations, and technical documentation. - Support application integration, cloud infrastructure, networking, security, and migration activities. - Test and validate solutions against functional, security, performance, and reliability requirements. - Troubleshoot technical issues and coordinate resolution with Google Cloud engineering teams. - Document architecture decisions, risks, dependencies, and implementation recommendations. - Escalate complex architecture decisions and delivery risks - 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 provide clear guidance to others We could treat first 7 as responsibilities (duties) and the rest as skills. However the instruction says "Use
- for any list of duties/requirements/benefits". So we can have separate lists for responsibilities and skills.
Now after responsibilities, there is "The Team AI & Engineering leverages cutting-edge engineering capabilities..." That's description of team, could be part of About the role or maybe a separate section? Not required headings. Could be included in About the role paragraph.
Then "Qualifications Required" heading. Then list:
- 5+yrs of experience in GCP cloud architecture, technical consulting, professional services, technical project management, or enterprise technology delivery.
- 3+yrs of hands-on software-engineering experience using an object-oriented language such as Python or C++
- 5+yrs of experience working as a hands-on or "keyboard" engineer.
- Familiarity with services such as Compute Engine, Cloud Storage, Cloud SQL, Cloud Networking, and Google Kubernetes Engine.
- Active Google Cloud professional-level certification
- Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or equivalent professional experience.
- Ability to obtain a U.S. Government TS/SCI security clearance
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
- Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve
These are qualifications/requirements. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since they are labeled "Qualifications Required", we could use Qualifications section. Requirements could be similar but we can just use Qualifications.
Then after qualifications, there is "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. A reasonable estimate of the current range is $118,700 to $197,900."
That's Pay information. So we need a Pay section with that paragraph.
Then "Recruiting tips ..." that's boilerplate/application instructions, we should remove.
Then "Benefits This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM". That's a benefits statement but no details. It says to view document. There's no specific benefit details. According to rules: never create Benefits section unless posting actually states them. It does mention benefits but only references a document; no concrete benefits listed. Should we include Benefits? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Here benefits are not specific; just a reference. Likely we should not include Benefits section because no specific benefits listed.
Then "Our people and culture ..." that's fluff, could be considered About the role? Might be considered generic boilerplate; but it's about culture. Could be included in About the role? Might be okay but it's not specific to role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is culture description; not boilerplate but maybe considered generic marketing. Might be okay to keep as part of About the role? However it's not directly about the role. Might be considered filler. Safer to omit.
Then "Professional development ..." also generic.
Then "Qualified applicants with criminal histories..." that's EEO/legal; remove.
Then "You may also be eligible to participate in a discretionary annual incentive program..." that's about compensation but maybe part of Pay? It mentions discretionary annual incentive program. Could be included in Pay section as additional detail. It's specific: discretionary annual incentive program. So we could add that to Pay section.
Thus final sections:
- About the role: includes initial paragraph + team description + maybe culture? We'll keep initial paragraph and team description.
- Responsibilities: list of first 7 duties.
- Skills: list of remaining abilities.
- Qualifications: list of qualifications.
- Pay: wage range paragraph + discretionary annual incentive program sentence.
We should not include Benefits, Schedule.
Check for any Schedule info: none.
Now format HTML.
We need to wrap each section:
About the role
...
etc. For lists:- ...
- for any list of duties/requirements/benefits". So we can have separate lists for responsibilities and skills.
Now after responsibilities, there is "The Team AI & Engineering leverages cutting-edge engineering capabilities..." That's description of team, could be part of About the role or maybe a separate section? Not required headings. Could be included in About the role paragraph.
Then "Qualifications Required" heading. Then list:
- 5+yrs of experience in GCP cloud architecture, technical consulting, professional services, technical project management, or enterprise technology delivery.
- 3+yrs of hands-on software-engineering experience using an object-oriented language such as Python or C++
- 5+yrs of experience working as a hands-on or "keyboard" engineer.
- Familiarity with services such as Compute Engine, Cloud Storage, Cloud SQL, Cloud Networking, and Google Kubernetes Engine.
- Active Google Cloud professional-level certification
- Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, or equivalent professional experience.
- Ability to obtain a U.S. Government TS/SCI security clearance
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
- Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve
These are qualifications/requirements. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since they are labeled "Qualifications Required", we could use Qualifications section. Requirements could be similar but we can just use Qualifications.
Then after qualifications, there is "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. A reasonable estimate of the current range is $118,700 to $197,900."
That's Pay information. So we need a Pay section with that paragraph.
Then "Recruiting tips ..." that's boilerplate/application instructions, we should remove.
Then "Benefits This position is aligned with the Project Delivery Model. To view the associated benefit package, please reference this document USBenefitsJourneyProjectandCenterTAM". That's a benefits statement but no details. It says to view document. There's no specific benefit details. According to rules: never create Benefits section unless posting actually states them. It does mention benefits but only references a document; no concrete benefits listed. Should we include Benefits? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Here benefits are not specific; just a reference. Likely we should not include Benefits section because no specific benefits listed.
Then "Our people and culture ..." that's fluff, could be considered About the role? Might be considered generic boilerplate; but it's about culture. Could be included in About the role? Might be okay but it's not specific to role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is culture description; not boilerplate but maybe considered generic marketing. Might be okay to keep as part of About the role? However it's not directly about the role. Might be considered filler. Safer to omit.
Then "Professional development ..." also generic.
Then "Qualified applicants with criminal histories..." that's EEO/legal; remove.
Then "You may also be eligible to participate in a discretionary annual incentive program..." that's about compensation but maybe part of Pay? It mentions discretionary annual incentive program. Could be included in Pay section as additional detail. It's specific: discretionary annual incentive program. So we could add that to Pay section.
Thus final sections:
- About the role: includes initial paragraph + team description + maybe culture? We'll keep initial paragraph and team description.
- Responsibilities: list of first 7 duties.
- Skills: list of remaining abilities.
- Qualifications: list of qualifications.
- Pay: wage range paragraph + discretionary annual incentive program sentence.
We should not include Benefits, Schedule.
Check for any Schedule info: none.
Now format HTML.
We need to wrap each section: