Cloud Architect (Multi-Cloud)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, application instructions, navigation, etc. We need to extract substantive info: The posting includes: - Company description: Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Salary Range: $130,000–$170,000 Annually - Experience Required: 12+ years - Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. - Job Summary: description of role. - Required Qualifications: list. - Preferred Qualifications: list. - How to Apply: we must remove application instructions. - EEO statement: remove. Thus we need sections: About the role (maybe company description + role summary?), Responsibilities (maybe from Job Summary?), Requirements (maybe experience required?), Qualifications (maybe required qualifications?), Skills (maybe from required/preferred?), Benefits (none explicit), Pay (salary range), Schedule (maybe position type full-time? Could be schedule). We need to include only sections with real content. We need to decide which sections to include. - About the role: could include company description and job summary. That is substantive. - Responsibilities: could be derived from Job Summary: design strategies, reference architectures, platform capabilities that span multiple cloud providers, focusing on portability, abstraction layers, federated identity, cross-cloud networking, platform offerings that hide cloud-specific complexity from product teams. Also maybe leading multi-cloud architecture initiatives. We can list as bullet points. - Requirements: could include Experience Required: 12+ years, sponsorship eligibility, location remote, position type full-time, maybe degree requirement? Actually degree is in qualifications. But we can put experience and sponsorship under Requirements. - Qualifications: Required Qualifications list. - Skills: maybe combine required and preferred qualifications? Or we could put technical skills under Skills: hands-on architecture across at least two major cloud providers, cloud networking, identity, security, IaC, policy-as-code, federated identity SSO, Kubernetes, container platforms, managed cloud services, communication, stakeholder management, multiple cloud certifications, leading multi-cloud architecture initiatives. Preferred: abstraction platforms, cloud-agnostic observability, large-scale migrations, regulated industries, public talks/writing. - Pay: Salary Range. - Schedule: Position Type: Full-time, Direct W2 (maybe also remote). Could be schedule: Full-time. We must not include placeholder text like "commensurate with experience". Not present. We must not include navigation/legal/EEO etc. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must preserve ALL substantive information; do not invent or summarize away detail. Thus we need to include all details from the posting except boilerplate. Let's extract all substantive info: Company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Location: "100% Remote (U.S.)" Position Type: "Full-time, Direct W2" Salary Range: "$130,000–$170,000 Annually" Experience Required: "12+ years" Sponsorship: "U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." Job Summary: "We are seeking a Cloud Architect (Multi-Cloud) to design strategies, reference architectures, and platform capabilities that span multiple cloud providers — AWS, Azure, GCP, and selectively OCI — for enterprises operating on more than one cloud by deliberate choice. The role focuses on portability, abstraction layers, federated identity, cross-cloud networking, and platform offerings that hide cloud-specific complexity from product teams. The ideal candidate has architected meaningful multi-cloud capabilities, understands the trade-offs between portability and cloud-native depth, and brings strong opinions grounded in production experience." Required Qualifications list: - Bachelor’s or Master’s degree in Computer Science or a related field - Eight or more years of experience in cloud architecture roles - Hands-on architecture experience across at least two major cloud providers - Deep understanding of cloud networking, identity, and security across multiple providers - Strong experience with infrastructure-as-code and policy-as-code across clouds - Experience designing federated identity and SSO across cloud platforms - Solid understanding of Kubernetes, container platforms, and managed cloud services - Excellent communication and stakeholder management skills - Multiple cloud certifications across providers - Track record of leading multi-cloud architecture initiatives Preferred Qualifications list: - Experience with abstraction platforms (Crossplane, Pulumi, Terraform CDK) - Familiarity with cloud-agnostic observability platforms - Experience driving large-scale cloud-to-cloud migrations - Exposure to regulated industries with multi-cloud mandates - Public talks or writing on multi-cloud architecture We also have "How to Apply" which we must remove. EEO statement remove. Thus we need to map to sections. Potential sections: - About the role: could include company description and job summary (maybe combined). Or we could split: About the role (company description), Responsibilities (job summary). Let's decide. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings if content exists. We need to include a section ONLY when the posting has real, specific content for it. Thus we need to decide which sections have content. About the role: we have company description and maybe overview. That's specific. Responsibilities: we have job summary details about what the role does. That's specific. Requirements: we have experience required, sponsorship, location, position type? Could be considered requirements. But also we have degree requirement under qualifications. Might be better to put degree under Qualifications. Requirements could be experience years, sponsorship, location, position type. Qualifications: we have Required Qualifications list. Skills: we could combine technical skills from required and preferred? Or we could treat Required Qualifications as Qualifications, and Preferred Qualifications as Skills? But the instruction says we can use Skills section for list of skills. Might be appropriate to put both required and preferred under Skills? However we already have Qualifications for required. Let's follow typical pattern: Qualifications = required qualifications; Skills = preferred qualifications or skill highlights. But we also have many skill-like items in required qualifications (e.g., hands-on architecture experience, deep understanding, strong experience, etc.). Those could be considered skills. But we already have Qualifications for required. To avoid duplication, we could put required qualifications under Qualifications, and preferred qualifications under Skills. However the instruction says "Use

  • for any list of duties/requirements/benefits". So we can have lists under any section. Thus we can have: - About the role: prose (company description + maybe high-level summary) - Responsibilities: list of duties (from job summary) - Requirements: list (experience years, sponsorship, location, position type) - Qualifications: list (required qualifications) - Skills: list (preferred qualifications) - Pay: salary range - Schedule: position type full-time (maybe also remote). But we already used location under Requirements; schedule could be full-time. We must not repeat info. Ensure we preserve all substantive info. Let's list each piece and assign. Company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Job Summary (responsibilities): "We are seeking a Cloud Architect (Multi-Cloud) to design strategies, reference architectures, and platform capabilities that span multiple cloud providers — AWS, Azure, GCP, and selectively OCI — for enterprises operating on more than one cloud by deliberate choice. The role focuses on portability, abstraction layers, federated identity, cross-cloud networking, and platform offerings that hide cloud-specific complexity from product teams. The ideal candidate has architected meaningful multi-cloud capabilities, understands the trade-offs between portability and cloud-native depth, and brings strong opinions grounded in production experience." We could break responsibilities into bullet points: - Design strategies, reference architectures, and platform capabilities spanning multiple cloud providers (AWS, Azure, GCP, selectively OCI) - Focus on portability, abstraction layers, federated identity, cross-cloud networking - Create platform offerings that hide cloud-specific complexity from product teams - Architect meaningful multi-cloud capabilities - Understand trade-offs between portability and cloud-native depth - Bring strong opinions grounded in production experience That captures all. Requirements: we have: - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Experience Required: 12+ years - Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. We could also include that the role is direct W2 (already in position type). So list: - 100% Remote (U.S.) - Full-time, Direct W2 - 12+ years of experience - Open to U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates (no new H-1B sponsorship) Qualifications (required): - Bachelor’s or Master’s degree in Computer Science or a related field - Eight or more years of experience in cloud architecture roles - Hands-on architecture experience across at least two major cloud providers - Deep understanding of cloud networking, identity, and security across multiple providers - Strong experience with infrastructure-as-code and policy-as-code across clouds - Experience designing federated identity and SSO across cloud platforms - Solid understanding of Kubernetes, container platforms, and managed cloud services - Excellent communication and stakeholder management skills - Multiple cloud certifications across providers - Track record of leading multi-cloud architecture initiatives Skills (preferred): - Experience with abstraction platforms (Crossplane, Pulumi, Terraform CDK) - Familiarity with cloud-agnostic observability platforms - Experience driving large-scale cloud-to-cloud migrations - Exposure to regulated industries with multi-cloud mandates - Public talks or writing on multi-cloud architecture Pay: Salary Range: $130,000–$170,000 Annually Schedule: Position Type: Full-time (maybe also direct W2 but that's employment type). Could just say Full-time. We must not repeat info: we already used Full-time in Requirements; we could still include Schedule: Full-time. It's okay to repeat? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Repeating is not prohibited but might be redundant. Better to avoid duplication: we can put Full-time under Requirements and not repeat under Schedule, or we can put Schedule: Full-time and not include in Requirements. But we need to keep location and sponsorship somewhere. Let's decide to put location, sponsorship, and experience under Requirements, and put Position Type (Full-time, Direct W2) under Schedule. That way