Cloud Solutions Architect (US)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph describing role: "Neural Concept embeds AI into design and simulation workflows... That is this role. You take an enterprise customer and make the platform real for them: architected, deployed, integrated, cleared by their security organisation, and stable enough that their engineers stop thinking about it. You own that outcome end to end for named accounts, as their primary technical counterpart." We can put that as

About the role

then

...

. - Responsibilities: The "What You Will Do" bullet list: deployment from first architecture conversation through go-live and into steady-state operation; integration with customer's identity, data and engineering systems, and infrastructure and model serving layer; relationship with IT, security and platform teams: assessments, architecture reviews, and the call when something breaks; diagnosis when it does break, including when cause sits outside our own software; runbooks, post-mortems and playbooks that make next deployment easier, and feedback loop into Product. We can format as

• ...

. - Where you will do it: description of environments: Managed Kubernetes across major clouds; on-premises and fully air-gapped clusters with no route to internet, GPU infrastructure, self-hosted model serving; customer HPC environments, schedulers, shared storage under real load; installing software with no internet access, on hardware you do not control, reads as interesting part. Could be part of Responsibilities or maybe a separate section like "Work Environment". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could incorporate environment details into Responsibilities or maybe Requirements? Probably Responsibilities includes where you will do it. Could add a paragraph after responsibilities. - Who You Are: list of qualifications: 6+ years deploying and operating enterprise software in production, two of them in environments you did not control; Kubernetes at configuration depth; Identity and SSO fundamentals; Linux, networking and TLS; Kubernetes storage; A production deployment you personally carried and then supported. Name it, date it, tell us what went wrong; Professional customer-facing English, willingness to travel and work customers' hours. Also valuable: regulated or air-gapped deployments private registries and image mirroring GPU scheduling and LLM serving enterprise IdP administration Terraform and GitOps Prometheus and Grafana HPC schedulers ISO 27001 evidence Python PLM, CAD or CAE exposure. We can split into Requirements (mandatory) and Qualifications (preferred) or Skills. The headings we have: Requirements, Qualifications, Skills. We need to decide what goes where. Usually Requirements = mandatory, Qualifications = preferred, Skills = specific technical skills. We'll allocate: Requirements: 6+ years deploying and operating enterprise software in production, two of them in environments you did not control; Kubernetes at configuration depth; Identity and SSO fundamentals; Linux, networking and TLS; Kubernetes storage; A production deployment you personally carried and then supported (name it, date it, tell us what went wrong); Professional customer-facing English, willingness to travel and work customers' hours. Qualifications: maybe "Also valuable: regulated or air-gapped deployments private registries and image mirroring GPU scheduling and LLM serving enterprise IdP administration Terraform and GitOps Prometheus and Grafana HPC schedulers ISO 27001 evidence Python PLM, CAD or CAE exposure." Skills: maybe list of specific tech: Kubernetes, OIDC/SAML, Linux networking, TLS, CSI, etc. But we already covered many. Could combine. We need to avoid filler like "commensurate with experience". Not present. Benefits: The "You Get" section: Work with world-class technology team; Benefit from competitive salary and rewarding opportunities as we continue to scale; Thrive in collaborative multicultural environment; Develop professionally alongside talented colleagues; Make a global impact; Balance life and work with remote work or hybrid model (20% remote); Enjoy paid vacations, healthcare (medical/vision/dental), 401K matching. Pay: Not explicitly stated; only "competitive salary". That is vague but maybe we can include Pay section if posting actually states them. It says "competitive salary". That's not a specific number, but it's still stating salary. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salary, so we can include Pay section with that phrase. However "competitive salary" is somewhat generic but it's stated. We'll include. Schedule: The posting mentions remote work or hybrid model (20% remote) and "we care about results, not rigid schedules". That's schedule info. So we can include Schedule section. Now we need to output HTML fragment only, no markdown fences. Let's craft. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

Competitive salary.

Schedule

Hybrid model (20% remote) with flexible hours focused on results.

We need to ensure we don't repeat job title. No extra. Now fill content precisely, preserving all substantive info. Let's extract exact sentences. About the role: Combine first two paragraphs: "Neural Concept embeds AI into design and simulation workflows so engineering teams make continuous, data-driven decisions instead of waiting on sequential design–simulation–validation cycles. None of that matters until the platform is running inside the customer's environment, on their infrastructure, under their rules. That is this role. You take an enterprise customer and make the platform real for them: architected, deployed, integrated, cleared by their security organisation, and stable enough that their engineers stop thinking about it. You own that outcome end to end for named accounts, as their primary technical counterpart." We'll put that as a single paragraph. Responsibilities: list items: - The deployment, from the first architecture conversation through go-live and into steady-state operation. - Its integration with the customer's identity, data and engineering systems, and the infrastructure and model serving layer beneath it. - The relationship with their IT, security and platform teams: assessments, architecture reviews, and the call when something breaks. - The diagnosis when it does break, including when the cause sits outside our own software. - The runbooks, post-mortems and playbooks that make the next deployment easier, and the feedback loop into Product. We'll keep as is. Where you will do it: maybe incorporate into Responsibilities as an extra bullet? Could add bullet: "Work environments include managed Kubernetes across major clouds, on-premises and fully air-gapped clusters with no route to the internet, GPU infrastructure, self-hosted model serving, customer HPC environments, schedulers, and shared storage under real load, and installing software with no internet access on hardware you do not control." We'll add as a bullet. Now Requirements: list: - 6+ years deploying and operating enterprise software in production, with at least two years in environments you did not control. - Kubernetes at configuration depth: understanding how chart values become rendered manifests and why a workload will not start. - Identity and SSO fundamentals: OIDC and SAML, clients and credential rotation, redirect URIs, group-to-role mapping. - Linux, networking and TLS: DNS, routing, ingress and egress, certificate chains and interception proxies. - Kubernetes storage: persistent volumes and CSI, access modes, diagnosing shared storage that degrades under load. - A production deployment you personally carried and then supported; be able to name it, date it, and explain what went wrong. - Professional customer-facing English, and willingness to travel and work your customers' hours. Qualifications (preferred): - Experience with regulated or air-gapped deployments, private registries and image mirroring. - GPU scheduling and LLM serving. - Enterprise IdP administration. - Terraform and GitOps. - Prometheus and Grafana. - HPC schedulers. - ISO 27001 evidence. - Python. - PLM, CAD or CAE exposure. Skills: maybe list specific technical skills not covered? Could be redundant. But we need a Skills section; we can list: Kubernetes, OIDC/SAML, Linux networking, TLS, CSI, Terraform, GitOps, Prometheus, Grafana, HPC schedulers, Python. However many already in Requirements/Qualifications. Might be okay but avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in the posting? The posting lists many items under "Also valuable". Those are qualifications. We could treat those as Skills. But we already have Qualifications for those. Maybe we can omit Skills section if no distinct content. But we need to include a section only when posting has real specific content for it. If we don't have distinct content for Skills, we should not emit it. So better to omit Skills section. Thus we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now Benefits: list items: - Work with a world-class technology team – our engineers are top-notch, and we always aim for excellence. - Benefit from a competitive salary and rewarding opportunities as we continue to scale. - Thrive in a collaborative, multicultural environment where your work is visible and recognized. - Develop professionally alongside talented colleagues who share knowledge freely and support one another. - Make a global impact by helping customers shift to AI-assisted design, making innovation faster, smarter, and more sustainable. - Balance life and work with remote work or hybrid model (20% remote) — we care about results, not rigid schedules. - Enjoy paid vacations, healthcare (medical/vision/dental), 401K matching. Note: The hybrid model mention also appears in Schedule; we might avoid duplication. But we can keep Benefits focusing on other benefits, and Schedule separate. Pay: "competitive salary" already mentioned in Benefits; but we still need Pay section if posting states it. We can put Pay: "Competitive salary (see Benefits)." But to avoid duplication, maybe we just put Pay: "Competitive salary." Benefits can exclude salary mention. Let's adjust Benefits to not include salary phrase. The Benefits paragraph originally: "Benefit from a competitive salary and rewarding opportunities as we continue to scale." We'll split: Pay gets competitive salary; Benefits gets rewarding opportunities etc. Thus Benefits list: - Work with a world-class technology team – our engineers are top-notch, and we always aim for excellence. - Rewarding opportunities as we continue to scale. - Thrive in a collaborative, multicultural environment where your work is visible and recognized. - Develop professionally alongside talented colleagues who share knowledge freely and support one another. - Make a global impact by helping customers shift to AI-assisted design, making innovation faster, smarter, and more sustainable. - Enjoy paid vacations, healthcare (medical/vision/dental), 401K matching. Schedule: Hybrid model (20% remote) with flexible hours focused on results; travel to customer locations in the US required. Also mention start date ASAP, eligibility ITAR clearance required. Should we include that? It's substantive info. Where to put? Could be under Requirements or Qualifications? It's eligibility: ITAR clearance required. Could be a separate section like "Eligibility" but not allowed headings. Could incorporate