Solutions Architect

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. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, etc. Also remove duplicated lines. Must not create sections with placeholder text like "commensurate with experience". So we need to parse the posting. Let's extract content: First paragraph: "About The Role" heading. Content: "This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended. This role will be hybrid with requirements to be in office 3 days per week. The Solution Architect – Application Administration serves as a senior technical leader responsible for the design, engineering, and lifecycle management of enterprise application solutions. This role blends deep application administration expertise with a solution architecture mindset, focusing on building scalable, secure, and sustainable platforms that align with business strategy. The Solution Architect partners closely with architects, infrastructure teams, and business stakeholders to translate business requirements into engineered solutions, ensuring optimal integration across systems and platforms. This position emphasizes solution design, automation, standardization, and continuous improvement, while maintaining hands-on technical involvement. As a technical leader and mentor, this role fosters collaboration across teams, promotes engineering best practices, and drives innovation across the application administration domain." Then "MAJOR RESPONSIBILITIES AND AUTHORITY" heading with bullet points (list). Then "Professional Competencies:" bullet list. Then "About You" heading with bullet list of qualifications. Then "Preferred Certifications and Skills:" bullet list. Then "Role-Specific Competencies:" bullet list. Then "Professional Context:" bullet list. Then "About Us" about FDM. Then "Committed to Equal Opportunities" (EEO) - we must remove. Then "Additional Considerations" about states - maybe we keep? It's substantive info about location eligibility. Should we include? It's not a standard section but could be part of About the role or Requirements. The instruction: preserve ALL substantive information; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Additional Considerations" is not EEO, it's about states eligibility. It's substantive. Should we keep? Probably yes, we can incorporate into a short paragraph under About the role or maybe a separate section like "Location Eligibility". But we only allowed sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put location eligibility under About the role or Requirements. Probably under Requirements. We must not create sections with placeholder text. Benefits, Pay, Schedule: posting does not mention benefits, pay, schedule specifics beyond hybrid 3 days per week (that's schedule). Actually schedule: "This role will be hybrid with requirements to be in office 3 days per week." That's schedule info. So we can include a Schedule section with that detail. Benefits: not mentioned. Pay: not mentioned. So we omit Benefits and Pay. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We need to decide what goes where. About the role: general description (first paragraph). Could also include hybrid schedule? But schedule separate. Responsibilities: from "MAJOR RESPONSIBILITIES AND AUTHORITY" list. Requirements: maybe the "About You" bullet list (education/experience) plus maybe the "Additional Considerations" states. Qualifications: maybe the "Technical Expertise" etc? Actually "About You" includes education/experience and technical expertise. Could split: Requirements = education/experience; Qualifications = technical expertise; Skills = preferred certifications and role-specific competencies; Professional Context maybe part of Skills or Qualifications. But we need to follow typical sections: Responsibilities, Requirements, Qualifications, Skills. We'll map content accordingly. Let's extract bullet lists. Under MAJOR RESPONSIBILITIES AND AUTHORITY: each line starts with a bold heading? Actually they are like: Solution Design and Engineering Leadership: - Design, engineer, and implement robust application solutions that align with enterprise architecture and business objectives. - Partner with Enterprise Architects to validate solution designs for scalability, performance, and integration. - Translate complex technical and business requirements into actionable solution designs. - Lead prototyping and proof-of-concept efforts to validate solution feasibility. Application Lifecycle Ownership: - Own the end-to-end lifecycle of application platforms including deployment, configuration, maintenance, and optimization. - Ensure solutions are maintainable, scalable, and aligned with application administration best practices. - Drive standardization and automation across application lifecycle processes. Technical Standards and Governance: - Enforce and evolve engineering standards, guardrails, and best practices across all application solutions. - Champion secure administration and deployment practices across environments. - Ensure compliance with enterprise SDLC and governance frameworks. Collaboration and Stakeholder Engagement: - Partner with Infrastructure, Development, and Business teams to deliver aligned and effective solutions. - Facilitate clear communication between technical teams and business stakeholders. - Drive solution discussions, requirements clarification, and technical decision-making. Technical Leadership and Mentorship: - Serve as a senior escalation point for complex technical issues and solution challenges. - Mentor Application Administrators and engineers on solution design, automation, and best practices. - Promote a culture of innovation, collaboration, and continuous improvement. Solution Delivery and Optimization: - Lead troubleshooting and root cause analysis for complex system and application issues. - Perform system analysis, performance tuning, and optimization across platforms. - Ensure high-quality, scalable releases through solution validation and oversight. Business Alignment and Value Delivery: - Drive solutions that deliver measurable business outcomes and operational efficiency. - Build strong relationships with stakeholders to ensure alignment between technical solutions and business needs. - Support end-user enablement through guidance, documentation, and training. Professional Competencies: - Act as a role model for Application Administrators in adhering to and enhancing established quality and SDLC/PMLC best practices. - Comply with Certified Fleet Operator requirements as per the Company Driving and Safety Policy. Now About You bullet list: At least one of the following: - Bachelor’s degree from accredited college or university in a network, computer, or management related field and substantial experience in an information technology-related field. - Associate degree from an accredited school in a technology-related field and extensive experience in an information technology-related field. Technical Expertise: Solution Architecture Expertise: - Minimum 4 years of Strong foundation in application architecture, integration, and system design principles. - Ability to build and deliver scalable, enterprise-grade solutions. Cloud and Platform Engineering: - Experience in designing and supporting cloud-native solutions (preferably Microsoft Azure). - Familiarity with PaaS environments and modern application hosting models. Security and Compliance: - Expertise in secure configuration, deployment, and vulnerability mitigation practices. Problem-Solving and Innovation: - Strong analytical and critical thinking skills applied to complex solution challenges. - Ability to identify and implement innovative improvements across systems and processes. Performance Engineering: - Experience optimizing application performance and system efficiency across distributed environments. Leadership & Collaboration: - Proven ability to mentor teams and lead through influence. - Strong communication and stakeholder engagement skills. Preferred Certifications and Skills: - Certifications in Scrum, Agile, SAFe, or comparable frameworks. - Cloud-native experience, ideally in PaaS environments such as Microsoft Azure. Role-Specific Competencies: - Exceptional analytical thinking and problem-solving abilities can address and resolve highly intricate challenges. - A passion for continuous learning, skill expansion, and adaptability to emerging technologies and practices. - Outstanding oral and written communication skills, ensuring clarity in technical discussions and collaboration across diverse teams. - Strong organizational acumen, particularly in prioritizing tasks and managing competing demands effectively. Professional Context: - Operates as a senior technical leader without direct reports, influencing solution direction and engineering standards. - Bridges business and technical domains to ensure successful solution delivery and alignment. Now About Us paragraph: we can keep as part of About the role? Actually About Us is separate but we could incorporate into About the role? The instruction: preserve ALL substantive information. We could keep About Us as a paragraph under About the role or maybe a separate section but not in allowed list. Since only allowed sections are those, we could put About Us content under About the role as additional description. That seems okay. Now Additional Considerations: list of states. We'll incorporate into Requirements maybe as a note. Now schedule: hybrid 3 days per week. Now we need to output HTML with

for each section heading. Use

• for lists. Use

  for prose. We must not repeat job title. Not include Job ID. We must not include boilerplate like EEO, equal opportunity, etc. Already removed. We must not create sections with placeholder text. We'll only create sections where we have content. Thus sections:

  About the role

  -> paragraph(s) containing the initial description plus About Us maybe.

  Responsibilities

  -> list of responsibilities (the major responsibilities list). Could combine all bullet points under one
  or separate subheadings? The instruction: use
  • for any list of duties/requirements/benefits. So we can just make a single list of all responsibility items. Could also group but not required.

    Requirements

    -> education/experience bullet list (At least one of the following) plus maybe Additional Considerations (states) as a paragraph.

    Qualifications

    -> technical expertise bullet list (Solution Architecture Expertise, Cloud and Platform Engineering, Security and Compliance, Problem-Solving and Innovation, Performance Engineering, Leadership & Collaboration). Could be a list.

    Skills

    -> Preferred Certifications and Skills, Role-Specific Competencies, Professional Context maybe as list.

    Schedule

    -> paragraph about hybrid 3 days per week. We must ensure we don't create empty sections. Now we need to preserve all substantive information. Let's capture all details. First, About the role paragraph: combine the initial description and About Us. Initial description: "This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended. This role will be hybrid with requirements to be in office 3 days per week. The Solution Architect – Application Administration serves as a senior technical leader responsible for the design, engineering, and lifecycle management of enterprise application solutions. This role blends deep application administration expertise with a solution architecture mindset, focusing on building scalable, secure, and sustainable platforms that align with business strategy. The Solution Architect partners closely with architects, infrastructure teams, and business stakeholders to translate business requirements into engineered solutions, ensuring optimal integration across systems and platforms. This position emphasizes solution design, automation, standardization, and continuous improvement, while maintaining hands-on technical involvement. As a technical leader and mentor, this role fosters collaboration across teams, promotes engineering best practices, and drives innovation across the application administration domain." About Us: "About FDMFDM powers the people behind tech and innovation. We spot trends, find top talent, and help businesses stay ahead.With 35+ years of