Senior Cloud Platform Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must output only HTML fragment, no /, no markdown fences.
Let's extract content:
Job Description: Senior Cloud Platform Engineer Location: Austin, Texas (Partial Remote)
Role Overview: Cloud Engineering owns the shared cloud platform: the GCP organization and Azure tenant, the landing zones, IAM and network baselines, the Terraform framework and module library, and the standards that govern them. This role exists to close the gap between the platform's existence and a product running reliably on it in production. You will embed with product and vendor delivery teams as their Cloud Engineering counterpart, from design through go-live and into steady-state operations. This position combines platform engineering with Site Reliability Engineering (SRE) practices to ensure products can deploy repeatably, recover from failure, and operate within defined security and compliance boundaries.
Key Responsibilities:
- Serve as the embedded Cloud Engineering contact for assigned product teams and vendor delivery teams.
- Translate product and vendor requirements into cloud designs that fit published standards on GCP.
- Build the product's infrastructure as code in the product-owned Terraform repository, including project structure, IAM, database access, VPC, and pipelines.
- Stay with the team through first deployments to validate prerequisites, prove environment promotion, and fix defects.
- Provide operational support after go-live for issues related to access, connectivity, capacity, cost, and security findings.
- Review infrastructure code, pull requests, and architecture decision records against Cloud Engineering standards.
- Act as the cloud counterpart to external delivery partners, ensuring their designs align with security, network, and identity boundaries.
- Apply and tune security controls at the product boundary, such as VPC Service Controls, organization policies, and Identity-Aware Proxy.
- Convert repeated product shapes into reusable assets, contributing to the Terraform module library.
- Ensure all effort is traceable through Jira work items tied to the source product.
Required Qualifications:
- 10+ years in a hands-on role such as cloud engineering, platform engineering, or solutions engineering supporting application teams.
- Experience with Google Cloud Platform, including projects, IAM, Shared VPC, Private Service Connect, Cloud DNS, Cloud Run, Cloud SQL, and Pub/Sub.
- Working knowledge of Microsoft Azure, including subscriptions, Entra ID, virtual networking, and Azure Firewall.
- Proficiency with Terraform, including authoring modules and managing remote state in CI workflows.
- Experience building CI/CD pipelines in Azure DevOps or Cloud Build with keyless authentication through Workload Identity Federation.
- Understanding of cloud networking and identity principles such as DNS, TLS, OAuth2/OIDC, and least-privilege design.
- Demonstrated ability to diagnose production issues using logs, audit trails, and IAM policy state.
- Experience working directly with product owners and application developers to gather requirements and create documentation.
- Strong written communication skills for creating design rationale, review findings, and handoff documents.
- Bachelor's degree in Computer Science, Information Technology, or a related field, or equivalent practical experience.
Preferred Qualifications:
- Google Professional Cloud Architect or Microsoft Certified: Azure Solutions Architect Expert certification.
- Experience with VPC Service Controls, organization policy, and domain-restricted sharing on GCP.
- Experience consuming an API management platform like Apigee X from the workload side.
- Experience with GKE or other Kubernetes platforms.
- Experience with Pub/Sub, Kafka, or other event-driven integration on GCP.
- Experience as the cloud-side counterpart to a vendor-delivered platform.
- Familiarity with FinOps practices, including cost estimation and spend review.
- Experience operating within a Product, Agile, or DevSecOps framework.
- Exposure to supply chain, distribution, or logistics domains.
Company description: Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico. Everforth Apex uses a virtual recruiter as part of the application process. Click here for more details. (We should drop application instructions and virtual recruiter link? The instruction says remove application instructions. The line about virtual recruiter and click here is application instruction; we should drop it. Also the subsequent lines about agreeing to receive calls etc are also application instructions; drop. Also the privacy policy link etc drop. Also the benefits overview we need to keep as Benefits section.
Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide.
We should keep that as Benefits section.
We must drop EEO boilerplate etc.
Now structure:
About the role
role overview paragraph(s). Could be two paragraphs but we can combine into one
containing the role overview text.
Responsibilities
- ... each bullet
Qualifications
We could split into Required and Preferred but maybe combine into one section with two sublists? The instruction: prefer few substantive sections over many thin ones. Could have one Qualifications section with two subheadings? But subheadings would be maybe not allowed? Only for section headings. Could we use inside? Probably okay. But to keep simple, we could have two sections: Required Qualifications and Preferred Qualifications. That's two sections, still okay. But they said prefer few substantive sections over many thin ones. Having two qualification sections is fine.
Alternatively combine into one Qualifications section with two lists preceded by indicating required and preferred. That is one section.
Let's do one Qualifications section with two
headings inside? Not heading. Use
Required Qualifications:
then . Then Preferred Qualifications:
then . That keeps one section.
Similarly Benefits section.
Location: we can include a short paragraph after About the role maybe: Location: Austin, Texas (Partial Remote)
. Not a heading.
Now produce HTML.
Check for any leftover boilerplate: we removed EEO, legal, application instructions, virtual recruiter, privacy policy, etc. Also removed the duplicated EEO lines.
Make sure we preserve all substantive info: role overview, responsibilities, required qualifications, preferred qualifications, benefits overview, location, company description (Everforth Apex description). The company description paragraph is part of "About the company" maybe we can include in About the role or separate section "About the company". The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company but we could include it as part of About the role or maybe as a separate section "About the company". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's examples, not exhaustive. We could add About the company if we want, but better to stick to given examples. The company description is substantive; we could incorporate it into About the role paragraph or a separate paragraph without heading. Probably best to add a paragraph after role overview: "Everforth Apex is a world-class IT services company..." etc.
Thus About the role section will contain role overview + company description.
Now produce HTML.
Let's craft:
About the role
Cloud Engineering owns the shared cloud platform: the GCP organization and Azure tenant, the landing zones, IAM and network baselines, the Terraform framework and module library, and the standards that govern them. This role exists to close the gap between the platform's existence and a product running reliably on it in production. You will embed with product and vendor delivery teams as their Cloud Engineering counterpart, from design through go-live and into steady-state operations. This position combines platform engineering with Site Reliability Engineering (SRE) practices to ensure products can deploy repeatably, recover from failure, and operate within defined security and compliance boundaries. Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico.
Location: Austin, Texas (Partial Remote)
Responsibilities
- Serve as the embedded Cloud Engineering contact for assigned product teams and vendor delivery teams.
- Translate product and vendor requirements into cloud designs that fit published standards on GCP.
- Build the product's infrastructure as code in the product-owned Terraform repository, including project structure, IAM, database access, VPC, and pipelines.
- Stay with the team through first deployments to validate prerequisites, prove environment promotion, and fix defects.
- Provide operational support after go-live for issues related to access, connectivity, capacity, cost, and security findings.
- Review infrastructure code, pull requests, and architecture decision records against Cloud Engineering standards.
- Act as the cloud counterpart to external delivery partners, ensuring their designs align with security, network, and identity boundaries.
- Apply and tune security controls at the product boundary, such as VPC Service Controls, organization policies, and Identity-Aware Proxy.
- Convert repeated product shapes into
for prose. We must output only HTML fragment, no /, no markdown fences. Let's extract content: Job Description: Senior Cloud Platform Engineer Location: Austin, Texas (Partial Remote) Role Overview: Cloud Engineering owns the shared cloud platform: the GCP organization and Azure tenant, the landing zones, IAM and network baselines, the Terraform framework and module library, and the standards that govern them. This role exists to close the gap between the platform's existence and a product running reliably on it in production. You will embed with product and vendor delivery teams as their Cloud Engineering counterpart, from design through go-live and into steady-state operations. This position combines platform engineering with Site Reliability Engineering (SRE) practices to ensure products can deploy repeatably, recover from failure, and operate within defined security and compliance boundaries. Key Responsibilities: - Serve as the embedded Cloud Engineering contact for assigned product teams and vendor delivery teams. - Translate product and vendor requirements into cloud designs that fit published standards on GCP. - Build the product's infrastructure as code in the product-owned Terraform repository, including project structure, IAM, database access, VPC, and pipelines. - Stay with the team through first deployments to validate prerequisites, prove environment promotion, and fix defects. - Provide operational support after go-live for issues related to access, connectivity, capacity, cost, and security findings. - Review infrastructure code, pull requests, and architecture decision records against Cloud Engineering standards. - Act as the cloud counterpart to external delivery partners, ensuring their designs align with security, network, and identity boundaries. - Apply and tune security controls at the product boundary, such as VPC Service Controls, organization policies, and Identity-Aware Proxy. - Convert repeated product shapes into reusable assets, contributing to the Terraform module library. - Ensure all effort is traceable through Jira work items tied to the source product. Required Qualifications: - 10+ years in a hands-on role such as cloud engineering, platform engineering, or solutions engineering supporting application teams. - Experience with Google Cloud Platform, including projects, IAM, Shared VPC, Private Service Connect, Cloud DNS, Cloud Run, Cloud SQL, and Pub/Sub. - Working knowledge of Microsoft Azure, including subscriptions, Entra ID, virtual networking, and Azure Firewall. - Proficiency with Terraform, including authoring modules and managing remote state in CI workflows. - Experience building CI/CD pipelines in Azure DevOps or Cloud Build with keyless authentication through Workload Identity Federation. - Understanding of cloud networking and identity principles such as DNS, TLS, OAuth2/OIDC, and least-privilege design. - Demonstrated ability to diagnose production issues using logs, audit trails, and IAM policy state. - Experience working directly with product owners and application developers to gather requirements and create documentation. - Strong written communication skills for creating design rationale, review findings, and handoff documents. - Bachelor's degree in Computer Science, Information Technology, or a related field, or equivalent practical experience. Preferred Qualifications: - Google Professional Cloud Architect or Microsoft Certified: Azure Solutions Architect Expert certification. - Experience with VPC Service Controls, organization policy, and domain-restricted sharing on GCP. - Experience consuming an API management platform like Apigee X from the workload side. - Experience with GKE or other Kubernetes platforms. - Experience with Pub/Sub, Kafka, or other event-driven integration on GCP. - Experience as the cloud-side counterpart to a vendor-delivered platform. - Familiarity with FinOps practices, including cost estimation and spend review. - Experience operating within a Product, Agile, or DevSecOps framework. - Exposure to supply chain, distribution, or logistics domains. Company description: Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico. Everforth Apex uses a virtual recruiter as part of the application process. Click here for more details. (We should drop application instructions and virtual recruiter link? The instruction says remove application instructions. The line about virtual recruiter and click here is application instruction; we should drop it. Also the subsequent lines about agreeing to receive calls etc are also application instructions; drop. Also the privacy policy link etc drop. Also the benefits overview we need to keep as Benefits section. Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide. We should keep that as Benefits section. We must drop EEO boilerplate etc. Now structure:
About the role
role overview paragraph(s). Could be two paragraphs but we can combine into one
containing the role overview text.
Responsibilities
- ... each bullet
Qualifications
We could split into Required and Preferred but maybe combine into one section with two sublists? The instruction: prefer few substantive sections over many thin ones. Could have one Qualifications section with two subheadings? But subheadings would be maybe not allowed? Only for section headings. Could we use inside? Probably okay. But to keep simple, we could have two sections: Required Qualifications and Preferred Qualifications. That's two sections, still okay. But they said prefer few substantive sections over many thin ones. Having two qualification sections is fine.
Alternatively combine into one Qualifications section with two lists preceded by indicating required and preferred. That is one section.
Let's do one Qualifications section with two
headings inside? Not heading. Use
Required Qualifications:
then . Then Preferred Qualifications:
then . That keeps one section.
Similarly Benefits section.
Location: we can include a short paragraph after About the role maybe: Location: Austin, Texas (Partial Remote)
. Not a heading.
Now produce HTML.
Check for any leftover boilerplate: we removed EEO, legal, application instructions, virtual recruiter, privacy policy, etc. Also removed the duplicated EEO lines.
Make sure we preserve all substantive info: role overview, responsibilities, required qualifications, preferred qualifications, benefits overview, location, company description (Everforth Apex description). The company description paragraph is part of "About the company" maybe we can include in About the role or separate section "About the company". The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company but we could include it as part of About the role or maybe as a separate section "About the company". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's examples, not exhaustive. We could add About the company if we want, but better to stick to given examples. The company description is substantive; we could incorporate it into About the role paragraph or a separate paragraph without heading. Probably best to add a paragraph after role overview: "Everforth Apex is a world-class IT services company..." etc.
Thus About the role section will contain role overview + company description.
Now produce HTML.
Let's craft:
About the role
Cloud Engineering owns the shared cloud platform: the GCP organization and Azure tenant, the landing zones, IAM and network baselines, the Terraform framework and module library, and the standards that govern them. This role exists to close the gap between the platform's existence and a product running reliably on it in production. You will embed with product and vendor delivery teams as their Cloud Engineering counterpart, from design through go-live and into steady-state operations. This position combines platform engineering with Site Reliability Engineering (SRE) practices to ensure products can deploy repeatably, recover from failure, and operate within defined security and compliance boundaries. Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico.
Location: Austin, Texas (Partial Remote)
Responsibilities
- Serve as the embedded Cloud Engineering contact for assigned product teams and vendor delivery teams.
- Translate product and vendor requirements into cloud designs that fit published standards on GCP.
- Build the product's infrastructure as code in the product-owned Terraform repository, including project structure, IAM, database access, VPC, and pipelines.
- Stay with the team through first deployments to validate prerequisites, prove environment promotion, and fix defects.
- Provide operational support after go-live for issues related to access, connectivity, capacity, cost, and security findings.
- Review infrastructure code, pull requests, and architecture decision records against Cloud Engineering standards.
- Act as the cloud counterpart to external delivery partners, ensuring their designs align with security, network, and identity boundaries.
- Apply and tune security controls at the product boundary, such as VPC Service Controls, organization policies, and Identity-Aware Proxy.
- Convert repeated product shapes into
- lists preceded by
- Serve as the embedded Cloud Engineering contact for assigned product teams and vendor delivery teams.
- Translate product and vendor requirements into cloud designs that fit published standards on GCP.
- Build the product's infrastructure as code in the product-owned Terraform repository, including project structure, IAM, database access, VPC, and pipelines.
- Stay with the team through first deployments to validate prerequisites, prove environment promotion, and fix defects.
- Provide operational support after go-live for issues related to access, connectivity, capacity, cost, and security findings.
- Review infrastructure code, pull requests, and architecture decision records against Cloud Engineering standards.
- Act as the cloud counterpart to external delivery partners, ensuring their designs align with security, network, and identity boundaries.
- Apply and tune security controls at the product boundary, such as VPC Service Controls, organization policies, and Identity-Aware Proxy.
- Convert repeated product shapes into
indicating required and preferred. That is one section. Let's do one Qualifications section with two
headings inside? Not heading. Use
Required Qualifications:
then- . Then
Preferred Qualifications:
then- . That keeps one section.
Similarly Benefits section.
Location: we can include a short paragraph after About the role maybe:
Location: Austin, Texas (Partial Remote)
. Not a heading. Now produce HTML. Check for any leftover boilerplate: we removed EEO, legal, application instructions, virtual recruiter, privacy policy, etc. Also removed the duplicated EEO lines. Make sure we preserve all substantive info: role overview, responsibilities, required qualifications, preferred qualifications, benefits overview, location, company description (Everforth Apex description). The company description paragraph is part of "About the company" maybe we can include in About the role or separate section "About the company". The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company but we could include it as part of About the role or maybe as a separate section "About the company". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's examples, not exhaustive. We could add About the company if we want, but better to stick to given examples. The company description is substantive; we could incorporate it into About the role paragraph or a separate paragraph without heading. Probably best to add a paragraph after role overview: "Everforth Apex is a world-class IT services company..." etc.
Thus About the role section will contain role overview + company description.
Now produce HTML.
Let's craft:
About the role
Cloud Engineering owns the shared cloud platform: the GCP organization and Azure tenant, the landing zones, IAM and network baselines, the Terraform framework and module library, and the standards that govern them. This role exists to close the gap between the platform's existence and a product running reliably on it in production. You will embed with product and vendor delivery teams as their Cloud Engineering counterpart, from design through go-live and into steady-state operations. This position combines platform engineering with Site Reliability Engineering (SRE) practices to ensure products can deploy repeatably, recover from failure, and operate within defined security and compliance boundaries. Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico.
Location: Austin, Texas (Partial Remote)