Senior Software and Solutions Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate: EEO/Vet/Disabled, navigation, cookie, legal, etc. Also remove application instructions (like "Join Us in Engineering Better Care..." maybe that's okay if it's not instruction? It's more marketing. Might keep as part of About the role? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the final paragraph "Join Us in Engineering Better Care..." as it's application encouragement? Might be considered application instructions? It's more marketing but could be considered fluff. Safer to remove it. Also remove EEO line. We need to preserve all substantive information: description of company, role, responsibilities, requirements, qualifications, benefits, etc. Let's parse content: Paragraphs: - At Capsa Healthcare, we're engineering better care... (company description) - We are seeking a Senior Software Solutions Architect to serve as the technical steward of Axona's end-to-end pharmacy fulfillment ecosystem... (role description) - This position reports to the Senior Director of Enterprise Architecture and is a REMOTE role requiring 30% - 40% travel. (schedule/travel) - Why Join Capsa? (benefits/culture) - As the Senior Software Solutions Architect, you will need experience with the following: (list of technical requirements) - What We're Looking For (education, experience) - What Capsa Offers (benefits list) - Join Us in Engineering Better Care. (call to action) - remove. - EEO/Vet/Disabled - remove. We need sections: About the role (maybe combine company description and role description?), Responsibilities (maybe from role description?), Requirements (technical list), Qualifications (education/experience), Benefits (What Capsa Offers), Pay (maybe not explicit; they say "Competitive salary commensurate with experience" - that's vague but it's mention of pay. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They do state "Competitive salary commensurate with experience" - that is a statement about pay, albeit vague. Should we include Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salary commensurate with experience. That's a statement about pay, albeit not specific. It's still stating something about pay. Should we include? The instruction also says: "Prefer a few substantive sections over many thin ones." And "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')". So if the only pay content is "Competitive salary commensurate with experience", that is filler/placeholder text (commensurate with experience). So we should NOT create a Pay section because it's just placeholder. So omit Pay. Schedule: they mention REMOTE role requiring 30% - 40% travel. That's schedule/travel info. That's specific enough (remote, travel %). So we can include a Schedule section (maybe heading Schedule). Or we could incorporate into About the role? But we have a Schedule heading allowed. Since they gave specifics, we can include Schedule section with that info. Benefits: they list many benefits in What Capsa Offers. That's substantive. So Benefits section. Responsibilities: from role description: "serve as the technical steward of Axona's end-to-end pharmacy fulfillment ecosystem, ensuring all platform components work together as a unified solution. With a balance of strategic architecture and hands-on development, this individual defines service boundaries, integration patterns, API contracts, deployment strategies, and modernization priorities while validating decisions through code, prototypes, and real-world implementation." That's responsibilities. Requirements: maybe the technical list under "As the Senior Software Solutions Architect, you will need experience with the following:" That's requirements (technical). Could also be Skills. But we have both Requirements and Skills headings allowed. We need to decide. The list includes deep .NET/C# microservices expertise, front-end architecture, event-driven distributed systems, IoT/connected device platform experience. That's more like Skills/Requirements. Could treat as Requirements. Then Qualifications: education and experience (bachelor's degree, 14+ years, 6+ years architect, ownership of production platform). That's Qualifications. Thus sections: About the role (company overview + role summary?), Responsibilities, Requirements, Qualifications, Benefits, Schedule. We must not repeat job title as heading. So no

Senior Software Solutions Architect

. Good. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the lists. Let's extract details: Company description paragraph: "At Capsa Healthcare, we're engineering better care. We build what healthcare runs on. Our pharmacy automation teams build the counting, packaging and robotic dispensing systems, and the software behind them, that pharmacies rely on to fill prescriptions at every scale, from a single retail counter to high volume central fill and mail order operations. It is engineering you can walk through. Join us and see how we're engineering a path to better care. Learn more about our solutions at www.capsahealthcare.com ." We can keep that as prose under About the role. Role description: "We are seeking a Senior Software Solutions Architect to serve as the technical steward of Axona's end-to-end pharmacy fulfillment ecosystem, ensuring all platform components work together as a unified solution. With a balance of strategic architecture and hands-on development, this individual defines service boundaries, integration patterns, API contracts, deployment strategies, and modernization priorities while validating decisions through code, prototypes, and real-world implementation. This position reports to the Senior Director of Enterprise Architecture and is a REMOTE role requiring 30% - 40% travel." We could split: About the role includes company description and maybe high-level role? But responsibilities section will have the detailed duties. Let's put About the role: company description paragraph only (maybe also brief role purpose?). But we need to preserve all substantive info; we can include the role description in Responsibilities (makes sense). So About the role: just company description. Responsibilities: the bullet points from "defines service boundaries, integration patterns, API contracts, deployment strategies, and modernization priorities while validating decisions through code, prototypes, and real-world implementation." Also maybe "serve as the technical steward of Axona's end-to-end pharmacy fulfillment ecosystem, ensuring all platform components work together as a unified solution." That's also a responsibility. So we can list responsibilities as bullet list. Requirements: the technical list under "As the Senior Software Solutions Architect, you will need experience with the following:" Then bullet list items: - Deep .NET/C# Microservices Expertise - Advanced .NET and C# Modern asynchronous programming - Microservices or modular architecture design - High-throughput, low-latency distributed systems - Production-scale architecture experience - Front-End Architecture (React/React Native) - React.js and React Native - TypeScript and modern JavaScript - Front-end architecture and standards ownership - Deep understanding of React lifecycle and rendering - Event-Driven Distributed Systems - Kafka or equivalent event streaming - MassTransit/workflow orchestration - gRPC and MQTT - Sagas/state machines - Understanding of ordering, delivery guarantees, and backpressure - IoT / Connected Device Platform Experience - Device identity and provisioning - Fleet management - Telemetry pipelines - Offline/intermittent connectivity - Device twins/shadow state - Over-the-air updates and configuration management We need to preserve all detail. Use

  • for any list. For nested items, we can have nested
    . That's fine. Qualifications: "What We're Looking For A bachelor's degree in engineering or related field; master's degree is a plus 14+ years of software engineering experience 6+ years in an architect or equivalent technical leadership role Ownership of a production platform spanning both backend services and frontend/UI layers" We can make bullet list. Benefits: "What Capsa Offers At Capsa Healthcare, we recognize that great people drive with great results. That's why we offer a competitive compensation and benefits package designed to support you professionally and personally, including: Competitive salary commensurate with experience Paid time off Paid holidays Medical, dental, and vision coverage Paid parental leave 401(k) with company match Company-paid Life, AD&D, and Long-Term Disability insurance Voluntary Short-Term Disability, Supplemental Life, AD&D, Accidental Injury, and Hospital Indemnity insurance" We need to keep all. The first sentence is prose. Then list of benefits. We'll put prose

    then

    • for each benefit. Schedule: "This position reports to the Senior Director of Enterprise Architecture and is a REMOTE role requiring 30% - 40% travel." That's schedule info. We'll put as

      maybe. We must not include duplicated lines. Ensure we don't repeat. Now produce HTML fragment. Structure:

      About the role

      At Capsa Healthcare, we're engineering better care. We build what healthcare runs on. Our pharmacy automation teams build the counting, packaging and robotic dispensing systems, and the software behind them, that pharmacies rely on to fill prescriptions at every scale, from a single retail counter to high volume central fill and mail order operations. It is engineering you can walk through. Join us and see how we're engineering a path to better care. Learn more about our solutions at www.capsahealthcare.com .

      Responsibilities

      • Serve as the technical steward of Axona's end-to-end pharmacy fulfillment ecosystem, ensuring all platform components work together as a unified solution.
      • Define service boundaries, integration patterns, API contracts, deployment strategies, and modernization priorities.
      • Validate decisions through code, prototypes, and real-world implementation.

      Requirements

      • Deep .NET/C# Microservices Expertise
        • Advanced .NET and C# Modern asynchronous programming
        • Microservices or modular architecture design
        • High-throughput, low-latency distributed systems
        • Production-scale architecture experience
      • Front-End Architecture (React/React Native)
        • React.js and React Native
        • TypeScript and modern JavaScript
        • Front-end architecture and standards ownership
        • Deep understanding of React lifecycle and rendering
      • Event-Driven Distributed Systems
        • Kafka or equivalent event streaming
        • MassTransit/workflow orchestration
        • gRPC and MQTT
        • Sagas/state machines
        • Understanding of ordering, delivery guarantees, and backpressure
      • IoT / Connected Device Platform Experience
        • Device identity and provisioning
        • Fleet management
        • Telemetry pipelines
        • Offline/intermittent connectivity
        • Device twins/shadow state
        • Over-the-air updates and configuration management
      But note the first bullet "Deep .NET/C# Microservices Expertise" is a