Senior Solution Architect

We need to produce HTML fragment with sections: Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: Overview paragraph: "The US Oncology Network is looking for a Senior Solution Architect to join our team at Texas Oncology. This is a remote role and requires the candidate to reside within Texas. As a part of The US Oncology Network, Texas Oncology delivers high-quality, evidence-based care to patients close to home. Texas Oncology is the largest community oncology provider in the country and has approximately 600+ providers in 280+ sites across Texas, our founders pioneered community-based cancer care because they believed in making the best available cancer care accessible to all communities, allowing people to fight cancer at home with the critical support of family and friends nearby. Our mission is still the same today—at Texas Oncology, we use leading-edge technology and research to deliver high-quality, evidence-based cancer care to help our patients achieve “More breakthroughs. More victories.” ® in their fight against cancer. Today, Texas Oncology treats half of all Texans diagnosed with cancer on an annual basis. The US Oncology Network is one of the nation’s largest networks of community-based oncology physicians dedicated to advancing cancer care in America. The US Oncology Network is supported by McKesson Corporation focused on empowering a vibrant and sustainable community patient care delivery system to advance the science, technology, and quality of care." Then "What does the Senior Solution Architect do? Including but not limited to The Solution Architect is a senior individual contributor role responsible for translating business, clinical, and technical requirements into cohesive, secure, and scalable solution designs across Texas Oncology. This role owns solution-level architecture for assigned initiatives, ensuring designs align with enterprise architecture standards, support long-term platform strategy, and are feasible to build and operate at scale. Operating between Enterprise Architecture and delivery teams, the Solution Architect provides hands-on technical leadership during design and implementation, guiding system integration, data flows, application design, and non-functional requirements while enabling delivery teams to execute effectively." Then "Responsibilities The essential duties and responsibilities: including but not limited to: Solution Architecture & Design Ownership Own end-to-end solution architecture for assigned initiatives, including application, integration, and data design.Translate business and clinical requirements into logical and physical architecture designs.Define non-functional requirements including security, scalability, performance, resilience, and supportability. Enterprise Architecture Alignment Ensure solution designs align with enterprise standards, architecture principles, and strategic roadmaps.Partner with Enterprise Architects on platform selection, reuse, and technology tradeoffs.Document architecture decisions, assumptions, and rationale. Delivery & Implementation Enablement Provide technical guidance to delivery teams during build, integration, testing, and deployment.Review detailed designs and implementation artifacts for architectural compliance.Support production readiness, go-live planning, and handoff to operations. Stakeholder & Vendor Collaboration Partner with analysts, product owners, and IT Project Managers to ensure clarity of intent and feasibility.Engage with vendors and implementation partners to ensure solutions meet design expectations.Communicate architectural concepts and tradeoffs to technical and non-technical stakeholders. Governance & Continuous Improvement Participate in architecture reviews and governance forums.Identify opportunities to improve patterns, standards, and reusable assets.Contribute to maturation of solution architecture practices across IT." Then "Qualifications The ideal candidate for the position will have the following background and experience: Required Qualifications Bachelor’s degree in Computer Science, Information Technology, Engineering, or related field.8-10 years of experience in solution architecture or senior-level systems design roles.Strong experience designing enterprise applications, integrations, and data flows.Demonstrated ability to balance business needs with technical and architectural constraints. Preferred Qualifications Healthcare IT or regulated-industry experience.Experience with cloud, integration platforms, and enterprise data environments.Skilled in modern architecture patterns and SDLC methodologies." Then "Physical Demands The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations will be offered to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee is regularly required to sit and use hands to finger, handle, or feel. The employee is occasionally required to stand, walk, and reach with hands and arms. The employee must occasionally lift and/or move up to 30 pounds. Specific vision abilities required by this job include ability to adjust focus. Requires vision and hearing corrected to normal range." Then "Work Environment The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job. Reasonable accommodations will be offered to enable individuals with disabilities to perform the essential functions. Work is performed in an office environment. Involves frequent interaction with corporate and field staff, as well as external customers and contacts. Work may require some travel by air or automobile. Fantastic time-management skills with the ability to multi-task." We need to decide sections: Overview (maybe "About the role" or "Overview"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for overview. Then "Responsibilities". Then "Qualifications". Possibly "Physical Demands" and "Work Environment" could be combined under "Requirements"? But they are not exactly requirements; they are more about job conditions. The instruction says we can include sections only when posting has real, specific content. We have content for Physical Demands and Work Environment. Could we create a section "Working Conditions"? Not in the list but we can still use

  with any heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate. Physical Demands and Work Environment could go under "Requirements" or maybe "Skills"? But they are not skills. Could be under "Requirements" as part of job requirements. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include a "Requirements" section that includes both qualifications and physical demands and work environment? But qualifications are separate. The posting has "Qualifications" section with required and preferred. So we should have a "Qualifications" heading. Then we could have a "Requirements" heading for physical demands and work environment? Might be okay. But we also have an overview description that could be "About the role". Let's do:

  About the role

  with overview paragraphs.

  Responsibilities

  with
  • items for each bullet. We need to extract bullet points from responsibilities. The responsibilities text is a bit run-on but we can parse into items: - Own end-to-end solution architecture for assigned initiatives, including application, integration, and data design. - Translate business and clinical requirements into logical and physical architecture designs. - Define non-functional requirements including security, scalability, performance, resilience, performance, and supportability. - Ensure solution designs align with enterprise standards, architecture principles, and strategic roadmaps. - Partner with Enterprise Architects on platform selection, reuse, and technology tradeoffs. - Document architecture decisions, assumptions, and rationale. - Provide technical guidance to delivery teams during build, integration, testing, and deployment. - Review detailed designs and implementation artifacts for architectural compliance. - Support production readiness, go-live planning, and handoff to operations. - Partner with analysts, product owners, and IT Project Managers to ensure clarity of intent and feasibility. - Engage with vendors and implementation partners to ensure solutions meet design expectations. - Communicate architectural concepts and tradeoffs to technical and non-technical stakeholders. - Participate in architecture reviews and governance forums. - Identify opportunities to improve patterns, standards, and reusable assets. - Contribute to maturation of solution architecture practices across IT. We need to ensure we preserve all substantive information; not invent or summarize away detail. So we should keep each distinct responsibility as separate
  • . The original had some combined sentences; we can split at periods. Now Qualifications: Required Qualifications and Preferred Qualifications. We can produce
    • for each. Required: - Bachelor’s degree in Computer Science, Information Technology, Engineering, or related field. - 8-10 years of experience in solution architecture or senior-level systems design roles. - Strong experience designing enterprise applications, integrations, and data flows. - Demonstrated ability to balance business needs with technical and architectural constraints. Preferred: - Healthcare IT or regulated-industry experience. - Experience with cloud, integration platforms, and enterprise data environments. - Skilled in modern architecture patterns and SDLC methodologies. Now Physical Demands and Work Environment: Could be under a section "Requirements" or maybe "Working Conditions". Since not in the example list but we can still use

      for any heading. 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 to be safe we could put them under "Requirements". However "Requirements" might be confused with qualifications. But we already have Qualifications. Perhaps we can have a section "Working Conditions" with Physical Demands and Work Environment. The instruction didn't list Working Conditions but it's okay as a heading as long as we have real content. It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exhaustive. So we can use other headings. Thus we can have:

      Physical Demands

      with

      describing.

      Work Environment

      with

      . But we need to avoid creating sections with filler text. We have real content. Now we need to ensure we don't repeat job title as heading. We are not. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none evident. Now produce HTML fragment. We'll wrap sections in maybe not needed. Just output headings and content. We'll use

      for prose paragraphs. For overview we have multiple paragraphs; we can combine into one

      or multiple. Probably multiple

      okay. Let's craft. Overview: The US Oncology Network is looking for a Senior Solution Architect to join our team at Texas Oncology. This is a remote role and requires the candidate to reside within Texas. As a part of The US Oncology Network, Texas Oncology delivers high-quality, evidence-based care to patients close to home. Texas Oncology is the largest community oncology provider in the country and has approximately 600+ providers in 2