Platform Architect

We need to output HTML fragment with sections: h3 headings for sections present: About the role (maybe Overview?), Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must include only sections with real specific content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We have a long posting with overlapping sections: Overview, About The Role, Responsibilities, Technology Tools, Role Essentials, What We'd Like to See, Pay Transparency, About Hyland, etc. Also later there is a duplicate "Responsibilities" section with different bullet points, and "Basic Qualifications". Also "What You Can Expect Next" (application instructions) should be removed. Also "U.S. Benefits" list. Also repeated "#HylandLife" etc. We need to extract substantive content: role description, responsibilities, qualifications/requirements, skills/tools, benefits, pay, schedule (if any). Schedule: not mentioned except maybe "Flexible Schedule" in benefits. So schedule could be part of benefits? But schedule section only if posting actually states schedule specifics. It mentions "Flexible Schedule" under benefits, so we could include schedule as part of benefits? The instruction: create Pay/Schedule/Benefits sections only if posting actually states them. It does state benefits list, and mentions flexible schedule. So we can have a Benefits section with list, and maybe a Schedule section noting flexible schedule? But schedule is part of benefits list; we could still have a Schedule section with "Flexible Schedule". However they said prefer few substantive sections over many thin ones. Might combine schedule into benefits? But they said use headings for Benefits, Pay, Schedule separately if present. Since schedule is mentioned, we could create a Schedule section with "Flexible Schedule". But that's thin. Might be okay. Pay: we have two salary ranges: first $148,000 – $170,000 per year, eligible for benefits and variable compensation. Later: base salary range of $161,000-189,000 and eligible for bonus and benefits. There's inconsistency; we must preserve all substantive info, not invent or summarize away detail. So we need to include both ranges? Probably we should include both as they appear. Could combine? But we must not invent or summarize away detail. We could list both ranges as separate statements. That's preserving detail. Benefits: list includes 401(k) Retirement Savings, Flexible Schedule, Paid Time Off, Medical, Dental, Vision, Volunteer Paid Time Off, Wellness Reimbursement, Paid Parental Leave, Sabbatical Program, Hyland House Program. Also maybe career development resources, wellbeing programs, innovation practices mentioned elsewhere. We'll include the explicit list. Responsibilities: we have two sets: first under "Your Role Responsibilities? Here's What You'll Do." with bullet points. Then later a "Responsibilities" section with different bullet points. We need to preserve all substantive info, so combine both sets? We should not duplicate identical lines; but they are different. We'll include all unique bullet points. Requirements/Qualifications: we have "Role Essentials" (Bachelor's degree or equivalent experience, 5+ years experience as Platform or Cloud Architect, mastery in two or more general purpose programming languages, master-level expertise in..., Solution Architect Professional or Equivalent in AWS or Azure, etc.) Also "Basic Qualifications": Master’s degree or equivalent experience, extensive experience with at least one prominent public cloud provider, extensive experience with IaC, experience operating software workloads in production, experience providing platform services for other internal teams, sharp fast learner, experience with continuous software delivery, understanding of build environments and delivery pipelines, strong oral/written communications, strong organizational/time management, strong collaboration skills, strong ability to coach/mentor. Also "What We'd Like to See": Multi-cloud experience (AWS + Azure), Knowledge of cloud security, compliance, and governance frameworks, Experience with cost optimization and FinOps practices, Published thought leadership or speaking experience on cloud architecture. Also "Technology Tools" list: Public Cloud Platforms, IaC Tools, CI/CD Pipeline Tools, Containerization & Orchestration, Security & Compliance Monitoring Tools. We need to decide sections: Could have "Requirements" (or "Qualifications") covering education, experience, certifications. Could have "Skills" covering technical tools and desired skills. Could have "Preferred Qualifications" for what we'd like to see. But instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements, Qualifications, Skills separate. But we need to avoid thin sections. Might combine Requirements and Qualifications into one? But they are distinct headings allowed. We could have Requirements (education, years experience) and Qualifications (certifications, specific expertise). Skills (tools, languages). However we have a lot of content; we can split. Let's extract: About the role: The overview paragraph: "The Platform Architect leads the creation and execution of strategic cloud architecture and platform initiatives, driving innovation and ensuring the seamless integration of complex cloud solutions across the organization. This role involves setting architectural standards, golden path patterns, conducting POCs, evaluating tools, mentoring teams, and influencing the overall cloud strategy to support long-term business objectives." Also maybe the "Overview Platform Architect Location: United States Work Arrangement: Remote". We should include location and work arrangement as part of About the role? Could be a short paragraph. We'll include location and remote. Responsibilities: combine bullet points from both sections. First set bullet points (from "Your Role Responsibilities? Here's What You'll Do."): - Lead the development of platform/cloud strategy within platform engineering, ensuring alignment with organizational objectives. - Design and oversee the implementation of complex, multi-cloud architectures, with hands-on involvement in proof-of-concepts and critical technical decisions. - Design and refine the workload deployment pattern. - Drive orchestration and provisioning architecture. - Establish and enforce platform specific standards and best practices, driving consistency and quality across cloud solutions and deployments. - Collaborate with executive leadership and stakeholders to define cloud strategy, roadmaps, and business cases, ensuring alignment with organizational priorities. - Perform advanced risk assessments and develop comprehensive mitigation strategies, addressing security, compliance, and operational risks in cloud environments. - Lead the evaluation and integration of new cloud technologies and tools, assessing their potential impact and benefits for the organization. - Drive continuous improvement in cloud architecture practices, utilizing feedback, performance data, and industry trends to refine and enhance architectural approaches. - Lead Platform's role in cloud transformation (orchestration, provisioning, workload patterns), ensuring they are delivered on time, within budget, and in accordance with architectural standards. - Share architectural insights with peers and industry professionals. - Operate as a trusted advisor on issues and trends; provide general consulting services leveraging expertise and significant best practice knowledge. - Drive adoption of architectural best practices within platform teams through knowledge sharing and coaching on current best practices and market trends. - Mentor, coach, train, and provide feedback to other team members; provide feedback to leadership on abilities of team. Second set bullet points (under "Responsibilities"): - Define technical direction, system architecture, and software architecture for supported programs, including the ownership of non-functional requirements, in alignment with functional requirements, program standards, and enterprise architecture. - Lead technical designs and provide oversight for design implements and codebase. - Ensure application of industry standards and best practices in technical designs and code and system development. - Collaborate with product management to refine teams’ and/or program backlogs by reviewing business cases, providing estimates, defining architectural enablers, and identifying and addressing implementation risks. - Collaborate with technical and architectural leadership across teams within a program to ensure that technical designs are in line with the enterprise architecture, and in compliance with product and industry practices and regulations. - Own the architectural roadmap and actively contribute to the product roadmap in collaboration with program leadership. - Mentor, coach, train, and provide feedback to other program members. - Provide feedback to leadership on technical abilities of team. - Operate as a trusted advisor to influence and lead the application of standard processes and practices within a program, including backlog refinement, planning, work estimation, solution demos, and software reviews. - Develop prototypes to evaluate and demonstrate architectural concepts and new technologies for software design. - Operate as an innovative thought leader. - Contribute to the overall growth and quality of the program and its teams through knowledge sharing and coaching on current best practices and market trends for software design. - Comply with all corporate and departmental privacy and data security policies and practices, including but not limited to, Hyland’s Information Systems Security Policy. We need to merge, avoid duplicates. Some overlap: mentoring, trusted advisor, etc. We'll keep unique. Now Requirements/Qualifications/Skills. Let's extract education/experience requirements: From Role Essentials: - Bachelor's degree or equivalent experience - 5+ years of experience as a Platform or Cloud Architect - Mastery in two or more general purpose programming languages - Master-level expertise in: cloud hosting design patterns, IaC, CI/CD pipelines, multi-cloud architectures - Solution Architect Professional or Equivalent in AWS or Azure - Excellent software modeling skills covering information, domain, process, state, security, logical, and physical architectural views. - Proven ability to design and oversee complex, enterprise-scale cloud solutions. - Strong executive presence and ability to influence C-level stakeholders. - Excellent critical thinking, problem-solving, and decision-making skills. - Strong collaboration and communication skills across technical and business stakeholders. - Ability to mentor and provide feedback to junior architects and senior engineers - Master level experience in understanding and application of cloud hosting design, design patterns, architecture patterns, and quality attributes. - Proven ability developing and using original thinking to translate business goals and functional requirements into the implementation of new ideas and design solutions - Up to 10% travel time required From Basic Qualifications: - Master’s degree or equivalent experience - Extensive experience with at least one prominent public cloud provider (e.g., AWS, Azure, or GCP) - Extensive experience with prominent infrastructure-as-code technology (e.g., Terraform, CloudFormation, etc.) - Experience operating software workloads in production - Experience providing platform services for other internal teams - Sharp, fast learner with technology curiosity and aptitude - Experience with continuous software delivery - Understanding of build environments and delivery pipelines - Strong oral and written communications skills that demonstrate a professional demeanor and the ability to interact with a variety of cross-functional roles with occasional executive presence - Strong organizational and time management skills - Strong collaboration skills, applied successfully within team as well as with all levels of employees in other areas - Strong ability to coach, mentor, and provide feedback to team members in a timely manner From What We'd Like to See: - Multi-cloud experience (AWS + Azure) - Knowledge of cloud security, compliance, and governance frameworks - Experience with cost optimization and FinOps practices - Published thought leadership or speaking experience on cloud architecture Now Skills/Tools list from Technology Tools: - Public Cloud Platforms (e.g., AWS, Microsoft Azure, Google Cloud) - Infrastructure as Code (IaC) Tools (e.g., Terraform, Pulumi) - CI/CD Pipeline Tools (e.g., GitHub Actions, Jenkins, Azure DevOps) - Containerization & Orchestration (e.g., Docker, Kubernetes) - Security & Compliance Monitoring Tools (e.g., Prisma Cloud, AWS Security Hub) Also mastery in two or more general purpose programming languages (could be skill). Also software modeling skills. We need to decide sections: Perhaps: - About the role (location, remote, summary) - Responsibilities (combined list) - Requirements (education, years experience, travel) - Qualifications (certifications, expertise, software modeling, executive presence, etc.) - Skills (technical tools, languages, cloud security, FinOps, thought leadership) - Benefits (list) - Pay (salary ranges) - Schedule (flexible schedule) We must avoid thin sections; but we have enough content. Now produce HTML fragment with

headings and

• for lists,

  for prose. We must not include any markdown code fences. Let