Solutions Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The initial paragraph: "Your Job Koch Engineered Solutions (KES) is seeking a Solutions Architect to join its global Information Technology (IT) team. This role will lead the architecture, integration, and modernization of KES’s engineering technology ecosystem, including Autodesk, CAD, PLM, and related product development platforms. The Solutions Architect partners with IT and business teams to design solutions for transformation initiatives using architecture best practices. Success requires balancing complex requirements and project risks while combining technical expertise, business insight, collaboration, and stakeholder alignment. A proactive self-starter who connects technology to business goals will thrive in this role. The role is based in Wichita, KS; Tulsa, OK; or Houston, TX and is not eligible for visa sponsorship. Our Team IT capability is a vital component of the KES strategy to improve business performance through the application of technology and to profitably transform our business. Our team operates with a startup mentality—working as an integrated group with the Engineering, Operations, Commercial, and Finance teams to design, build, and scale innovative solutions that transform KES work processes." That's about the role. - Responsibilities: "What You Will Do" bullet list. List items: - Partner with Product teams to recommend technology solutions for business transformation, then lead the technical solutioning process to build the detailed blueprint for how technology will solve the problem. - Consider the enterprise landscape as part of solution design to produce architectural blueprints consistent with IT technical vision and strategy - Leverage expertise in multiple technical domains as part of solutioning process (Software Engineering, Application Review/Selection, Security, Networking, Cloud Infrastructure, etc.) - Lead the development and alignment of architecture strategies across the engineering & design organization. - Experimentation - Identify and experiment with solutions to solve problems new to the organization - Execute on initiatives as appropriate, not just a “Box Drawing” role - Partner with finance to build economic “Bet” models for strategic solutions to determine a value range - Requirements / Qualifications: "Who You Are (Basic Qualifications)" list. List: - Experience with modern cloud-based platforms and tools (PLM, Engineering (CAD tools : Autodesk, Solidworks, etc), and Product Planning platforms, AWS, Microsoft, Salesforce, SaaS vendors) - Strong knowledge of CAD, PLM and engineering data management ecosystems - Experience architecting and supporting engineering and product development environments - Proven experience communicating technology in both execution detail and broad concepts to various audiences - Demonstrated capability partnering with customers to understand business and operating models to develop proposals for technical solutions - 5+ years’ experience in Information Technology - Skills: "What Will Put You Ahead" list. List: - Experience in supporting discrete engineering & manufacturing - Experience with conversational and action-oriented AI agent platforms that solve business problems. - Understanding the fundamental architecture of GenAI - Technical experience with serverless cloud technology tools and services (for example: S3, Blobs, SaaS, Lambda, SQS, SNS, Event Bridge, DynamoDB, API Gateway, etc.) - Experience with event driven architectures and microservices - Experience with analytical concepts (Data lakes, Graph Database Technology, Data Warehousing) - Experience with container technologies (Docker, Kubernetes, ECS, Fargate, AKS) - Experience with DevOps methodologies, processes and tools (CI/CD, GitHub, Lean, Azure DevOps) - Familiarity with enterprise architecture platforms such as LeanIX, HOPEX, or BizzDesign - Benefits: "Our Benefits" paragraph. Paragraph: "Our goal is for each employee, and their families, to live fulfilling and healthy lives. We provide essential resources and support to build and maintain physical, financial, and emotional strength - focusing on overall wellbeing so you can focus on what matters most. Our benefits plan includes - medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, and may also include infertility assistance, paid parental leave and adoption assistance. Specific eligibility criteria is set by the applicable Summary Plan Description, policy or guideline and benefits may vary by geographic region. If you have questions on what benefits apply to you, please speak to your recruiter." We should keep that. - Pay: The posting includes a paragraph about compensation: "At Koch companies, we are entrepreneurs. This means we openly challenge the status quo, find new ways to create value and get rewarded for our individual contributions. Any compensation range provided for a role is an estimate determined by available market data. The actual amount may be higher or lower than the range provided considering each candidate's knowledge, skills, abilities, and geographic location. If you have questions, please speak to your recruiter about the flexibility and detail of our compensation philosophy." That's about compensation but not a specific range. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation philosophy but not a specific range. It says "Any compensation range provided for a role is an estimate..." This is still about compensation but not a specific range. Should we include a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, but it's generic. It might be considered stating compensation philosophy. However they said "Prefer a few substantive sections over many thin ones." And they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation paragraph is not filler but it's generic. I'd say we can include a Pay section with that paragraph. But it's not a specific range; still it's substantive about compensation philosophy. I'd include it. - Schedule: Not mentioned. No schedule info. So we omit Schedule. - Also there is "Hiring Philosophy" and "Who We Are" sections. Those could be considered "About the company" but not required headings. We could incorporate into About the role or maybe a separate section like "About Koch Engineered Solutions". But the instruction only lists specific headings; we can add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for those sections if present. It doesn't forbid other headings, but better to stick to those. The "Hiring Philosophy" and "Who We Are" could be considered part of About the role or maybe we could add a section "About the Company". But not in list. Safer to incorporate into About the role paragraph. We also need to remove boilerplate: Equal Opportunities, EEO, legal, etc. Also remove "If you have questions, please speak to your recruiter about the flexibility and detail of our compensation philosophy." That's part of compensation paragraph; we can keep it as it's substantive. Also remove "Learn more about our hiring philosophy here." etc. Also remove "Our goal is for each employee..." we kept that as Benefits. Also remove "If you have questions on what benefits apply to you, please speak to your recruiter." That's part of Benefits; we can keep. Also remove "Equal Opportunities Equal Opportunity Employer, including disability and protected veteran status. Except where prohibited by state law, some offers of employment are conditioned upon successfully passing a drug test. This employer uses E-Verify. Please click here for additional information. (For Illinois E-Verify information click here, aquí, or tu)." Remove. Also remove "Hiring Philosophy All Koch companies value diversity of thought, perspectives, aptitudes, experiences, and backgrounds. We are Military Ready and Second Chance employers. Learn more about our hiring philosophy here." Remove. Also remove "Who We Are As a Koch company, Koch Engineered Solutions (KES) is a dynamic network of businesses that work together to create an ecosystem of domain expertise to increase operational efficiency, improve safety, reduce waste, and reduce emissions. At Koch, employees are empowered to do what they do best to make life better. Learn how our business philosophy helps employees unleash their potential while creating value for themselves and the company." Could be considered About the company; but we can incorporate into About the role maybe. However it's not about the role specifically. Might be considered boilerplate? It's descriptive of the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive about the company. Should we keep it? It's not covered by headings but we could add a section "About Koch Engineered Solutions". But the instruction only gave examples; not exclusive. I'd include a section with heading

About Koch Engineered Solutions

and put that paragraph. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the pattern. I'd include it as "About the Company". But maybe better to incorporate into About the role? The About the role already has a paragraph about team IT capability etc. The "Who We Are" is more about the company. Could be considered part of About the role? Not exactly. I'd add a separate section "About Koch Engineered Solutions". It's substantive. But we need to avoid filler. It's real content. Thus final HTML will have sections:

About the role

with paragraph(s).

Responsibilities

with

• ...

  Requirements

  (or Qualifications?). The heading "Who You Are (Basic Qualifications)" could be either Requirements or Qualifications. We have both Requirements and Qualifications as possible headings. The content is basic qualifications. Could be under Requirements. We'll use

  Requirements

  .

  Skills

  for "What Will Put You Ahead".

  Benefits

  for benefits paragraph.

  Pay

  for compensation philosophy paragraph. We'll omit Schedule. We'll also maybe include a short paragraph for location and visa sponsorship inside About the role. Now ensure we don't repeat job title as heading. Not. Now produce HTML fragment. Let's craft. About the role paragraph: combine the initial paragraphs plus maybe the "Our Team IT capability..." and "Our team operates with a startup mentality..." plus maybe the "Who We Are" paragraph? I'd keep Who We Are separate. Thus About the role: "Koch Engineered Solutions (KES) is seeking a Solutions Architect to join its global Information Technology (IT) team. This role will lead the architecture, integration, and modernization of KES’s engineering technology ecosystem, including Autodesk, CAD, PLM, and related product development platforms. The Solutions Architect partners with IT and business teams to design solutions for transformation initiatives using architecture best practices. Success requires balancing complex requirements and project risks while combining technical expertise, business insight, collaboration, and stakeholder alignment. A proactive self-starter who connects technology to business goals will thrive in this role. The role is based in Wichita, KS; Tulsa, OK; or Houston, TX and is not eligible for visa sponsorship." Then maybe a second paragraph: "Our Team IT capability is a vital component of the KES strategy to improve business performance through the application of technology and to profitably transform our business. Our team operates with a startup mentality—working as an integrated group with the Engineering, Operations, Commercial, and Finance teams to design, build, and scale innovative solutions that transform KES work processes." That seems good. Now Responsibilities list as above. Now Requirements list as above. Now Skills