Director, Application Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Rose BioSolutions" then "The Role", then "What You Will Do", "What You Bring", "Compensation Data", "How You Will Work", "Why Join Us?" and "Perks & Benefits". We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About Rose BioSolutions: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Rose BioSolutions" which is company overview. Could be placed under "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We need to decide which sections we have content for. We have: - About the role: we have "The Role" description. So we can put that under

About the role

. - Responsibilities: we have "What You Will Do" list. So

Responsibilities

. - Requirements / Qualifications: we have "What You Bring" which includes qualifications, experience, etc. Could be split into Requirements and Qualifications but we can combine? The instruction: prefer few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications combined? But they gave separate headings. We could use

Qualifications

for the "What You Bring". Or we could have both Requirements and Qualifications if we split content. But we have limited content; better to have one section, maybe "Qualifications". However we need to follow instruction: use those headings only if we have real specific content. We can choose to use "Qualifications". We'll put the "What You Bring" content there. - Skills: we could extract skills from "What You Bring" but it's overlapping. Might be thin. Better to not create Skills section if not distinct. - Benefits: we have "Perks & Benefits" and also "Compensation Data" includes pay. Benefits section: we have health, dental, vision, 401k, PTO, professional development. So we can make

Benefits

. - Pay: we have compensation data: $200k-225k per year. So

Pay

. - Schedule: not mentioned. So omit. We also have "How You Will Work" and "Why Join Us?" and "Impact" etc. Those could be folded into other sections or maybe we can include as part of About the role or separate? The instruction: only include sections when posting has real specific content for it. We could create a section "How You Will Work" but not in the list of allowed headings. The allowed headings are limited to those examples. So we should not create custom headings; we must use those headings. So we need to map content to those headings only. So "How You Will Work" could be part of About the role or Responsibilities? Probably part of About the role. "Why Join Us?" could be part of Benefits? Or maybe we can omit as it's promotional but still substantive. Could be placed under Benefits? Not exactly. Could be under About the role? Might be okay. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can embed them under the allowed headings. We must not omit any substantive info. So we need to ensure that all details from the posting appear somewhere in the HTML under allowed headings. Thus we need to place: - Company overview (About Rose BioSolutions) maybe under About the role? Could be a paragraph before responsibilities. That's okay. - The Role description (hands-on technical leader etc.) under About the role. - Responsibilities: the bullet list of duties (What You Will Do). We'll put as

• ... each bullet. - Qualifications: the bullet list of requirements (What You Bring). We'll put as
  • . - Pay: compensation data. - Benefits: the perks & benefits list. - Possibly also include "How You Will Work" and "Why Join Us?" details; we need to embed them somewhere. Could add a paragraph under About the role or Responsibilities? The instruction: do not omit substantive info. So we need to include those paragraphs somewhere. We could add a

    under About the role after the role description that includes "How You Will Work" and "Why Join Us?" content. Or we could create a separate section but not allowed heading. So we must incorporate them into existing sections. Thus final HTML:

    About the role

    Rose BioSolutions is a cell and gene therapy contract development and manufacturing organization (CDMO), recently carved out from Charles River Laboratories. The company operates sites in Rockville, MD; Memphis, TN; Northridge, CA; and Keele, UK, and is building its technology foundation as a standalone organization, including a new SAP S/4HANA Public Cloud core, GxP-validated quality and lab systems, and the commercial, legal, and workforce platforms that support a growing CDMO. The Director, Application Architect is a hands-on technical leader responsible for the design, integration, and lifecycle of Rose BioSolutions' core business applications. This person owns the architecture that connects SAP S/4HANA Public Cloud, Salesforce CRM, Ironclad, UKG, and the company's QMS and LIMS platforms, ensuring that data, processes, and controls flow cleanly across systems in a validated, GxP-appropriate environment. The Application Architect works closely with the CIO and business stakeholders to anticipate the company's evolving needs, identify where AI capabilities can responsibly improve these systems, and manage the vendor relationships, licensing, and contracts that underpin the application portfolio. This is an individual-contributor architecture role, not a people-management role, and requires someone who is equally comfortable in a whiteboard session with executives and inside a system configuration screen. Rose BioSolutions is currently separating from its former parent company, and this role will be heavily involved in that separation, including standing up new instances, migrating and disentangling data, closing out the parent company's Transition Service Agreement (TSA), and replacing shared-services systems with Rose BioSolutions' own application stack. This is a rare opportunity to help design and build a company's application architecture from the ground up, free of legacy debt, and to set new standards for how the systems are integrated, governed, and modernized from day one.

    Then responsibilities:

    Responsibilities

    • Own the end-to-end application architecture across SAP S/4HANA Public Cloud, Salesforce CRM, Ironclad, UKG, QMS, and LIMS, and maintain a current, accurate view of how these systems and their data connect to one another.
    • Work hands-on within these platforms, deep enough to evaluate configuration and integration decisions directly rather than relying solely on vendors or system integrators.
    • Partner with the CIO and business leaders across quality, manufacturing, commercial, legal, HR, and finance to understand operational needs and translate them into application and integration designs.
    • Anticipate the architectural implications of new business requirements, regulatory changes, growth, and site additions before they become urgent problems.
    • Understand the native AI capabilities built into SAP (such as Joule and SAP Business AI) and Salesforce (such as Einstein and Agentforce), and evaluate and recommend where these and other AI capabilities can be responsibly applied within the existing application stack, from workflow automation to document intelligence to decision support, with appropriate attention to GxP validation and data governance.
    • Define and maintain integration patterns, data flows, and system-of-record decisions across the application landscape, using integration middleware and iPaaS tooling (such as Boomi, MuleSoft, or SAP PI/PO) in coordination with the SAP implementation partner and other systems integrators.
    • Ensure application changes and integrations follow Computer System Validation (CSV) practices and comply with 21 CFR Part 11 requirements for electronic records and signatures.
    • Own the ongoing revalidation strategy required by a public cloud SAP environment, where SAP pushes quarterly releases on a fixed schedule. Unlike private cloud or on-premise deployments, validation here is a recurring compliance obligation, not a one-time event, and must be planned, resourced, and executed release after release without disrupting GxP operations.
    • Lead the technical closure of the company's Transition Service Agreement (TSA) with the former parent company, coordinating cutover timing and system readiness across all affected applications.
    • Own vendor and licensing management for the application portfolio, including contract renewals, license optimization, and commercial negotiations, in partnership with procurement and legal.
    • Establish architecture standards, documentation, and governance practices appropriate for a regulated CDMO environment.
    • Serve as a technical advisor during the ongoing carve-out and system implementation effort, working alongside the SAP SI, QMS/LIMS implementation teams, and managed service providers.
    • Play a lead role in separating Rose BioSolutions' applications and data from the former parent company's environment, including system cutover planning, data migration, and decommissioning of shared-services dependencies.
    • Take advantage of the greenfield opportunity to architect the new company's application landscape on modern, well-integrated, and AI-ready foundations, rather than replicating legacy patterns.
    • Communicate architectural tradeoffs and recommendations clearly to both technical and non-technical audiences, including executive leadership.
    Then qualifications:

    Qualifications

    • Bachelor's degree required; relevant certifications in SAP, Salesforce, or other core platforms in this role are a strong plus.
    • 8 to 10 years of experience in enterprise application architecture, with direct, hands-on implementation experience across SAP, Salesforce CRM, Ironclad, and UKG.
    • Experience with QMS and LIMS systems appropriate for a CDMO or other regulated life sciences manufacturing environment, including Computer System Validation (CSV) practices and 21 CFR Part 11 requirements.
    • Experience validating and maintaining regulated applications in a public cloud or SaaS environment, including managing recurring, vendor-driven release cycles rather than a single point-in-time validation.
    • Demonstrated ability to design and reason about system integration architecture, including data flows, system-of-record decisions, and integration middleware or iPaaS platforms (such as Boomi, MuleSoft, or SAP PI/PO).
    • Experience operating under a Transition Service Agreement (TSA) or otherwise supporting a carve-out or divestiture is a plus.
    • A working understanding of business operations in a manufacturing, quality, or life sciences services organization, and the judgment to anticipate how business needs translate into system requirements.
    • Practical knowledge of AI capabilities within enterprise applications, including what platforms like SAP (Joule, SAP Business AI) and Salesforce (Einstein, Agentforce) natively enable, and a thoughtful, risk-aware approach to introducing them in a regulated environment.
    • Experience owning vendor relationships, software licensing, and contract negotiations.
    • Excellent written and verbal communication skills, with the ability to move fluently between executive conversations and detailed technical work.
    • A hands-on, low-ego, self-starter approach; comfortable operating with significant autonomy in a lean, fast-moving environment.
    Then pay:

    Pay

    The pay rate for this role is $200,000-225,000 per year. Please