Senior Cloud Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (overview). Responsibilities (list). Requirements? The posting has Qualifications (Bachelor's degree required, 5+ years, etc). Also there is a separate "Qualifications" section later (maybe duplicate). Actually they have "Qualifications" heading then bullet list. Then later "Knowledge", "Skills", "Abilities", "Languages and tools". We need to map to allowed headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay specified: $74,200 to $148,230. Benefits: mention "Baker Tilly offers a comprehensive compensation and benefits package to eligible employees." That's vague but it's a statement about benefits. It's not specific details but it's still a statement. The rule: never create Benefits section unless posting actually states them. It does state they offer a comprehensive compensation and benefits package. That's enough? It's not specific but it's a statement. I'd include Benefits with that sentence.
Schedule: not mentioned. So omit Schedule.
Requirements: Could combine Qualifications and maybe Requirements? The posting has "Qualifications" heading with bullet list. Also there is "Requirements" maybe not explicit. We could treat the bullet list under Qualifications as Requirements. But we have both Requirements and Qualifications allowed headings. We need to decide what to put where. The posting includes "Qualifications" (Bachelor’s degree required, 5+ years...). Then later "Knowledge", "Skills", "Abilities", "Languages and tools". Those could be split into Requirements (maybe knowledge) and Skills. But we have separate Skills heading allowed. So we could put the bullet list under Qualifications (education, experience, certifications). Then put Knowledge, Skills, Abilities, Languages and tools under Skills? But Skills heading is for skills. Could combine knowledge and abilities into Skills? Might be better to have Requirements (education/experience), Qualifications (maybe certifications?), Skills (technical skills). However the instruction: Prefer a few substantive sections over many thin ones. So we should not over-section. Maybe combine everything into About the role, Responsibilities, Qualifications (including education, experience, certifications, knowledge, skills, abilities, tools), Pay, Benefits.
But we need to follow allowed headings list; we can omit some headings if no content. So we could have: About the role, Responsibilities, Qualifications, Pay, Benefits.
Check if we have any content for Requirements separate from Qualifications: The posting has "Qualifications" heading with bullet list (Bachelor’s degree required, 5+ years...). Then later "Knowledge", "Skills", "Abilities", "Languages and tools". Those could be considered part of Qualifications as well. So we can put all under Qualifications.
Thus sections: About the role (overview paragraph), Responsibilities (list), Qualifications (list combining education/experience, knowledge, skills, abilities, languages/tools), Pay (salary range), Benefits (statement).
We must not repeat job title as heading. No Job ID.
We must output only HTML fragment, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from overview, responsibilities, qualifications, knowledge, skills, abilities, languages/tools, pay, benefits.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The overview includes EEO statement etc. We must remove that. Also remove "Please discuss the work location status with your Baker Tilly talent acquisition professional..." maybe that's not boilerplate but it's about work location; could be considered part of overview? It's not a responsibility etc. Might be considered metadata; but it's not a heading. Could keep as part of About the role? It's about work location status; maybe keep as prose. However it's not a substantive job detail; but it's not boilerplate. Might keep.
Also remove "Baker Tilly is an equal opportunity/affirmative action employer..." etc. That's EEO boilerplate; remove.
Also remove "Any unsolicited resumes submitted..." etc. That's legal; remove.
Also remove "In order to be an authorized recruitment agency..." etc; remove.
Also remove "Visit bakertilly.com or join the conversation on LinkedIn, Facebook and Instagram." That's maybe not boilerplate but could be considered navigation; but it's about company; could keep? Might be considered promotional; but it's not substantive job detail. Safer to remove.
Also remove "Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring." That's maybe not boilerplate but it's a note; could keep? It's not a responsibility. Might be considered generic; but I'd keep it as part of About the role? It's about work location; maybe keep.
We need to preserve all substantive information: responsibilities list (with percentages), qualifications list, knowledge, skills, abilities, languages and tools, pay range, benefits statement.
We need to format lists appropriately.
Let's extract content.
Overview (About the role):
"Overview Baker Tilly is a leading advisory, tax and assurance firm, providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the world’s leading financial centers – New York, London, San Francisco, Los Angeles, Chicago and Boston. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP (Baker Tilly) provide professional services through an alternative practice structure in accordance with the AICPA Code of Professional Conduct and applicable laws, regulations and professional standards. Baker Tilly US, LLP is a licensed independent CPA firm that provides attest services to its clients. Baker Tilly Advisory Group, LP and its subsidiary entities provide tax and business advisory services to their clients. Baker Tilly Advisory Group, LP and its subsidiary entities are not licensed CPA firms. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP, trading as Baker Tilly, are independent members of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 141 territories, with 43,000 professionals and a combined worldwide revenue of $5.2 billion. Visit bakertilly.com or join the conversation on LinkedIn, Facebook and Instagram. Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring."
We need to remove the Visit bakertilly... line (maybe). Keep the rest up to before that? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Visit bakertilly... is maybe navigation/promotional; could remove. The Please discuss... maybe keep as it's about work location; but it's not a responsibility. I'd keep it as prose.
Thus About the role paragraph: combine the sentences except the Visit line.
Let's craft:
Baker Tilly is a leading advisory, tax and assurance firm, providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the world’s leading financial centers – New York, London, San Francisco, Los Angeles, Chicago and Boston. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP (Baker Tilly) provide professional services through an alternative practice structure in accordance with the AICPA Code of Professional Conduct and applicable laws, regulations and professional standards. Baker Tilly US, LLP is a licensed independent CPA firm that provides attest services to its clients. Baker Tilly Advisory Group, LP and its subsidiary entities provide tax and business advisory services to their clients. Baker Tilly Advisory Group, LP and its subsidiary entities are not licensed CPA firms. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP, trading as Baker Tilly, are independent members of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 141 territories, with 43,000 professionals and a combined worldwide revenue of $5.2 billion. Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring.
Now Responsibilities: The posting lists responsibilities with percentages and descriptions. Need to preserve all detail. Use
- for each responsibility item. Each item includes the percentage and description. We should keep the percentages as part of the li text.
Responsibilities list:
- Multi-cloud platform engineering and operations (design and operate foundations) (25%) Design, implement, and operate scalable infrastructure across AWS, Azure, and other providers, with hands-on depth in at least two.Engineer and improve foundational services and standard patterns (identity integration, networking, logging/monitoring, compute, storage, security controls).Own lifecycle management for key services (upgrades, deprecation planning, operational readiness). IaC ownership: reusable modules, standardized patterns, environment consistency (25%) Develop and maintain IaC (Terraform, Ansible, Bicep) with focus on reusable modules, standardized patterns, and consistency.Establish code quality expectations (reviews, documentation, versioning, validation) to improve repeatability and reduce risk. Automation-first engineering for efficiency and improve reliability (15%) Build automation workflows and scripts (Python, PowerShell, Bash) to eliminate manual operational tasks and improve reliability. Reliability ownership and operational standards (lead, don’t just participate) (15%) Own reliability outcomes for cloud services.Lead troubleshooting and root cause analysis; implement preventative improvements.Define and improve runbooks, monitoring standards, alerting practices, and support models. Security, compliance, resilience, and vulnerability management as engineered guardrails (12%) Ensure deployments meet security and compliance expectations through guardrails, patterns, and technical controls with Security/Risk.Support audit readiness (SOC, HIPAA, CMMC examples) with evidence support and control implementation.Design and validate backup, recovery, and resilience patterns; ensure objectives are tested and reliable.Lead and automate patching and vulnerability management improvements. Technical leadership: mentoring and cross-team influence (*8%) Translate requirements into designs, implementation plans, and roadmaps aligned to cloud-first.Mentor engineers through pairing, code reviews, and knowledge sharing.Provide technical guidance across teams, influencing patterns and decisions to reduce delivery friction
We need to split into separate li items. The original had bullet points each with a heading and percentage. We'll create li for each.
Now Qualifications: We need to combine education/experience, certifications, knowledge, skills, abilities, languages/tools.
Let's extract:
Qualifications (initial):
Bachelor’s degree required
5+ years in cloud engineering, infrastructure engineering, platform engineering, or related roles.
Hands-on engineering depth in at least two major cloud providers (AWS, Azure, GCP, OCI).
Strong IaC (Terraform preferred and/or Ansible) including module development and pattern standardization.
Strong scripting and automation (Python, PowerShell, Bash or equivalent).
Experience implementing or significantly improving CI/CD practices for infrastructure delivery.
Strong operational ownership: incident response, troubleshooting, root cause analysis, and preventative remediation.
Certifications / licenses (2 or more preferred)
AWS Solutions Architect – Professional
Microsoft Azure Solutions Architect Expert
Google Professional Cloud Architect
Oracle Cloud Infrastructure Architect Professional
Knowledge:
Deep knowledge of multi-cloud design and operations, with hands-on depth in at least two: AWS, Azure, GCP, OCI.
Knowledge of building and improving found
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from overview, responsibilities, qualifications, knowledge, skills, abilities, languages/tools, pay, benefits. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The overview includes EEO statement etc. We must remove that. Also remove "Please discuss the work location status with your Baker Tilly talent acquisition professional..." maybe that's not boilerplate but it's about work location; could be considered part of overview? It's not a responsibility etc. Might be considered metadata; but it's not a heading. Could keep as part of About the role? It's about work location status; maybe keep as prose. However it's not a substantive job detail; but it's not boilerplate. Might keep. Also remove "Baker Tilly is an equal opportunity/affirmative action employer..." etc. That's EEO boilerplate; remove. Also remove "Any unsolicited resumes submitted..." etc. That's legal; remove. Also remove "In order to be an authorized recruitment agency..." etc; remove. Also remove "Visit bakertilly.com or join the conversation on LinkedIn, Facebook and Instagram." That's maybe not boilerplate but could be considered navigation; but it's about company; could keep? Might be considered promotional; but it's not substantive job detail. Safer to remove. Also remove "Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring." That's maybe not boilerplate but it's a note; could keep? It's not a responsibility. Might be considered generic; but I'd keep it as part of About the role? It's about work location; maybe keep. We need to preserve all substantive information: responsibilities list (with percentages), qualifications list, knowledge, skills, abilities, languages and tools, pay range, benefits statement. We need to format lists appropriately. Let's extract content. Overview (About the role): "Overview Baker Tilly is a leading advisory, tax and assurance firm, providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the world’s leading financial centers – New York, London, San Francisco, Los Angeles, Chicago and Boston. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP (Baker Tilly) provide professional services through an alternative practice structure in accordance with the AICPA Code of Professional Conduct and applicable laws, regulations and professional standards. Baker Tilly US, LLP is a licensed independent CPA firm that provides attest services to its clients. Baker Tilly Advisory Group, LP and its subsidiary entities provide tax and business advisory services to their clients. Baker Tilly Advisory Group, LP and its subsidiary entities are not licensed CPA firms. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP, trading as Baker Tilly, are independent members of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 141 territories, with 43,000 professionals and a combined worldwide revenue of $5.2 billion. Visit bakertilly.com or join the conversation on LinkedIn, Facebook and Instagram. Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring." We need to remove the Visit bakertilly... line (maybe). Keep the rest up to before that? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Visit bakertilly... is maybe navigation/promotional; could remove. The Please discuss... maybe keep as it's about work location; but it's not a responsibility. I'd keep it as prose. Thus About the role paragraph: combine the sentences except the Visit line. Let's craft: Baker Tilly is a leading advisory, tax and assurance firm, providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the world’s leading financial centers – New York, London, San Francisco, Los Angeles, Chicago and Boston. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP (Baker Tilly) provide professional services through an alternative practice structure in accordance with the AICPA Code of Professional Conduct and applicable laws, regulations and professional standards. Baker Tilly US, LLP is a licensed independent CPA firm that provides attest services to its clients. Baker Tilly Advisory Group, LP and its subsidiary entities provide tax and business advisory services to their clients. Baker Tilly Advisory Group, LP and its subsidiary entities are not licensed CPA firms. Baker Tilly Advisory Group, LP and Baker Tilly US, LLP, trading as Baker Tilly, are independent members of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 141 territories, with 43,000 professionals and a combined worldwide revenue of $5.2 billion. Please discuss the work location status with your Baker Tilly talent acquisition professional to understand the requirements for an opportunity you are exploring. Now Responsibilities: The posting lists responsibilities with percentages and descriptions. Need to preserve all detail. Use
- for each responsibility item. Each item includes the percentage and description. We should keep the percentages as part of the li text. Responsibilities list: - Multi-cloud platform engineering and operations (design and operate foundations) (25%) Design, implement, and operate scalable infrastructure across AWS, Azure, and other providers, with hands-on depth in at least two.Engineer and improve foundational services and standard patterns (identity integration, networking, logging/monitoring, compute, storage, security controls).Own lifecycle management for key services (upgrades, deprecation planning, operational readiness). IaC ownership: reusable modules, standardized patterns, environment consistency (25%) Develop and maintain IaC (Terraform, Ansible, Bicep) with focus on reusable modules, standardized patterns, and consistency.Establish code quality expectations (reviews, documentation, versioning, validation) to improve repeatability and reduce risk. Automation-first engineering for efficiency and improve reliability (15%) Build automation workflows and scripts (Python, PowerShell, Bash) to eliminate manual operational tasks and improve reliability. Reliability ownership and operational standards (lead, don’t just participate) (15%) Own reliability outcomes for cloud services.Lead troubleshooting and root cause analysis; implement preventative improvements.Define and improve runbooks, monitoring standards, alerting practices, and support models. Security, compliance, resilience, and vulnerability management as engineered guardrails (12%) Ensure deployments meet security and compliance expectations through guardrails, patterns, and technical controls with Security/Risk.Support audit readiness (SOC, HIPAA, CMMC examples) with evidence support and control implementation.Design and validate backup, recovery, and resilience patterns; ensure objectives are tested and reliable.Lead and automate patching and vulnerability management improvements. Technical leadership: mentoring and cross-team influence (*8%) Translate requirements into designs, implementation plans, and roadmaps aligned to cloud-first.Mentor engineers through pairing, code reviews, and knowledge sharing.Provide technical guidance across teams, influencing patterns and decisions to reduce delivery friction We need to split into separate li items. The original had bullet points each with a heading and percentage. We'll create li for each. Now Qualifications: We need to combine education/experience, certifications, knowledge, skills, abilities, languages/tools. Let's extract: Qualifications (initial): Bachelor’s degree required 5+ years in cloud engineering, infrastructure engineering, platform engineering, or related roles. Hands-on engineering depth in at least two major cloud providers (AWS, Azure, GCP, OCI). Strong IaC (Terraform preferred and/or Ansible) including module development and pattern standardization. Strong scripting and automation (Python, PowerShell, Bash or equivalent). Experience implementing or significantly improving CI/CD practices for infrastructure delivery. Strong operational ownership: incident response, troubleshooting, root cause analysis, and preventative remediation. Certifications / licenses (2 or more preferred) AWS Solutions Architect – Professional Microsoft Azure Solutions Architect Expert Google Professional Cloud Architect Oracle Cloud Infrastructure Architect Professional Knowledge: Deep knowledge of multi-cloud design and operations, with hands-on depth in at least two: AWS, Azure, GCP, OCI. Knowledge of building and improving found