Solutions Architect

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

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "If you have questions, please speak to your recruiter..." etc. Also remove "Our Benefits" maybe keep if benefits described. There's a Benefits paragraph. So include Benefits section. Pay: The posting includes compensation range statement: "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." No actual range given. So we should NOT create Pay section because no specific range. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated, so include Benefits. Pay not stated specific range, so omit. Schedule: Not mentioned, omit. We need sections: About the role (maybe intro), Responsibilities (What You Will Do), Requirements/Qualifications (Who You Are (Basic Qualifications)), Skills (What Will Put You Ahead), Benefits (Our Benefits). Possibly also "About the team" but we can incorporate into About the role. We must preserve all substantive information, not invent or summarize away detail. Must not omit details. Must keep all details from posting except boilerplate. We need to convert lists to

• . Identify bullet-like content. Let's extract content. First 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." We can put that under About the role (or maybe a brief intro). Not a heading for job title. Next: "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." Could be part of About the role. Then "What You Will Do" list: - 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 These are responsibilities. Then "Who You Are (Basic Qualifications)" 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 Then "What Will Put You Ahead" 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 Then "At Koch companies, we are entrepreneurs..." that's culture, maybe not needed as separate section; could be part of About the role or omitted? It's substantive but not a standard heading. Could be included in About the role as a paragraph. Then compensation philosophy paragraph: we should omit because it's generic and not specific range. It's boilerplate? It's about compensation philosophy; not a specific range. According to rule, we should not create Pay section unless posting actually states them. This is not a specific range, so we omit. Then "Hiring Philosophy ..." includes diversity, Military Ready, Second Chance employers. That's EEO/equal-opportunity boilerplate? It's about hiring philosophy; might be considered boilerplate but it's not standard EEO statement. However it's still generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is EEO/equal-opportunity boilerplate. So remove. Then "Who We Are As a Koch company, Koch Engineered Solutions (KES) is a dynamic network of businesses..." That's about company; could be considered boilerplate? It's descriptive but maybe not required. It's not a standard heading; could be part of About the role? Might be considered boilerplate but it's describing the company. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's company overview. Might be okay to keep? But we need to preserve ALL substantive information. This is substantive about the company. However we have limited sections; we could include an "About the company" section but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role or maybe not include a separate heading. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use those headings. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should fit content into those headings. Company description could go under About the role (makes sense). So we incorporate that paragraph into About the role. Then "Our Benefits" paragraph: we need Benefits section. Then "Equal Opportunities" etc boilerplate remove. 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 philosophy; remove. Also remove "Learn more about our hiring philosophy here." etc. Also remove "If you have questions on what benefits apply to you, please speak to your recruiter." That's part of Benefits but it's a directive to recruiter; maybe remove as application instruction? It's not exactly application instruction but it's a referral to recruiter. Might be considered boilerplate. Safer to remove that sentence. Also remove "Additionally, everyone has individual work and personal needs. We seek to enable the best work environment that helps you and the business work together to produce superior results." That's generic fluff; maybe keep? It's not boilerplate but could be considered filler. It's not specific detail. Might be considered filler. Safer to remove as it's not specific substantive detail? It's somewhat generic. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. This sentence is vague; could be considered filler. I'd remove. Also remove "Our goal is for each employee, and their families, to live fulfilling and healthy lives." That's part of Benefits description; keep? It's part of benefits intro. Keep. Now construct HTML. We'll have:

  About the role

  ... (combined intro, team description, company overview, location, visa sponsorship, etc.)

  Responsibilities

  • ... each responsibility

  Requirements

  ... maybe combine Basic Qualifications? But we have Requirements and Qualifications as separate headings allowed. Could put Basic Qualifications under Requirements, and Skills under Qualifications? Actually they listed Requirements, Qualifications, Skills as separate. We have Basic Qualifications (who you are) and What Will Put You Ahead (skills). So we can map: - Requirements: maybe the basic qualifications (5+ years experience, etc.) - Qualifications: maybe also basic qualifications? Hmm. Better: Use Requirements for basic qualifications, Qualifications for maybe also basic? But we have two lists: Basic Qualifications and What Will Put You Ahead (skills). Could treat Basic Qualifications as Requirements, and What Will Put You Ahead as Skills. Then we might not need Qualifications heading. Or we could put Basic Qualifications under Requirements and Qualifications, and Skills under Skills. But we need to avoid empty sections. Let's decide:

  Requirements

  • 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

  • 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
  We could also include a Qualifications section but maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit