Director of AI Operations & Delivery

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. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - About SoftWriters (company description) maybe not needed? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. "About the role" likely corresponds to "The Opportunity" paragraph. "Responsibilities" corresponds to "What You'll Do". "Requirements" corresponds to "What We're Looking For Required". "Qualifications" maybe same as Requirements? Could separate but we can combine? The instruction: include a section only when posting has real specific content for it. We have both Required and Preferred under "What We're Looking For". Could treat "Requirements" as required, "Qualifications" as preferred? Or "Skills" as technical skills. Let's decide. We have: - About SoftWriters (company description) maybe not needed; but we could put under "About the role"? Actually "About the role" is about the role, not company. The posting includes "About SoftWriters" separate. Could we include that as a section? Not in allowed headings. Probably we should omit company description because not requested. But we must preserve ALL substantive information; cannot drop company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However we are limited to using only those headings. Could we include company description under "About the role"? Might be okay to include as part of that section. But "About the role" is supposed to be about the role, not company. However we could still include company info there; it's still substantive. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; 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 map content to those headings. If some content doesn't fit, we could still put under appropriate heading like "About the role" could include company overview. Or we could create a separate heading like "About SoftWriters" but that's not in list; maybe not allowed. Safer to put company description under "About the role". It's still substantive. Now extract content: About the role / The Opportunity: "The Opportunity We're seeking a Director of AI Operations & Delivery to join our growing Alpha Lab team and help shape the future of healthcare technology. In this role, you'll lead the execution and delivery of SoftWriters' agentic AI platform initiatives, driving operational excellence across product and engineering teams while helping define the next generation of AI-powered healthcare solutions. Location: Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday) Reports to: VP of AI" We should not include "Location:" as separate heading; we can embed in paragraph. Responsibilities (What You'll Do): List bullet points: - Delivery Leadership: Own delivery outcomes for agentic initiatives present and future. Drive sprint execution, unblock teams, manage dependencies with engineering and IT. - Blended Team Leadership: Build and lead a high-performance product + engineering team (currently ~4 people; scaling). Recruit, develop, and retain top talent across product and engineering disciplines. - Product & Engineering Alignment: Own the day-to-day integration of product thinking and engineering execution. Define features, roadmap prioritization, and technical tradeoffs with shared ownership. - Agentic Fleet Operations: Establish processes for creating, deploying, monitoring, and scaling agentic systems. Own the operational framework for agent lifecycle management and team capability building. - Technical Depth: Maintain hands-on familiarity with agentic architecture, cloud infrastructure (Azure), agent frameworks, and LLM integrations. Contribute to architectural decisions; unblock engineering on technical design questions. - Cross-Functional Alignment: Partner with VP of Engineering, IT/Cloud leadership (Azure governance), and broader product leadership on roadmap and technical constraints. - Operational Excellence: Establish metrics, dashboards, and processes for delivery visibility, quality, and risk management. Scale operations as team grows. We need to put each as

inside

. Requirements (What We're Looking For Required): - 5+ years in software engineering, product management, or engineering leadership - 3+ years managing high-performance blended or cross-functional teams (product + engineering preferred) - 2+ years hands-on experience with AI/ML systems, agentic systems, or orchestration platforms - Deep technical depth in at least one of: cloud architecture (Azure/AWS), distributed systems, agent frameworks, LLM integrations, or platform engineering - Proven ability to bridge product and engineering, comfortable translating between product vision and technical execution - Demonstrated success in startup or R&D environments Qualifications (Preferred): - Experience with agentic systems, multi-agent orchestration, or AI-driven automation - Healthcare, pharmacy, or regulated industry background - Experience scaling cross-functional teams in innovation labs or R&D centers - Strong product mindset: roadmap prioritization, customer/user empathy, go-to-market thinking - AWS or Azure cloud infrastructure expertise - Background in SDLC best practices Skills: Could be technical skills list maybe overlapping with requirements. Could combine but we have separate sections. We could put technical skills under Skills: e.g., agentic architecture, Azure, agent frameworks, LLM integrations, etc. But we already have those in requirements. Might be redundant. However we need to include a section only when posting has real specific content for it. The posting does not have a separate "Skills" heading; but we could infer skills from the responsibilities and requirements. However to avoid fabrication, maybe we should not create a Skills section if not explicitly present. The posting does not have a "Skills" heading; but we could still create a Skills section summarizing technical skills mentioned. That might be considered summarizing away detail? It's not inventing, it's extracting. But the instruction: "Prefer a few substantive sections over many thin ones." Could combine Skills into Requirements or Qualifications. Safer to omit Skills section if not explicit. Benefits: The posting includes "Why You'll Love Working Here" with subpoints: Meaningful Work, Modern Work Environment, Recognized Top Workplace, Work-Life Balance (Hybrid work policy with flexible hours, Remote-Work Bank for additional flexibility, Paid parking provided, PTO day on your birthday, Floating holidays), Comprehensive Benefits (Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, and vision coverage, Life and disability insurance), Growth-Focused Culture, Our Values in Action. We need to extract benefits: Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, and vision coverage, Life and disability insurance, Paid parking, PTO day on birthday, Floating holidays, Remote-Work Bank, Hybrid work policy with flexible hours, Modern office, Recognized top workplace, etc. Some are more culture/environment. But we can list benefits as bullet points. Pay: The posting mentions "Competitive salary" but no specific number. The instruction: 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. Since they state "Competitive salary" which is vague but still states something about pay. Is that considered placeholder? It's not a specific number but it's a statement. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive salary" is somewhat vague but not exactly those. It's still a statement about pay. I'd include Pay section with that statement. Schedule: They mention Hybrid work policy with flexible hours, Core office days: Tuesday, Wednesday, Thursday. Also Remote-Work Bank for additional flexibility. So we have schedule info. So we can include Schedule section. Now we need to output HTML fragment only, no markdown fences. We'll structure:

About the role

... (including company description and opportunity)

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Pay

Competitive salary

Schedule

Hybrid work policy with flexible hours; core office days Tuesday, Wednesday, Thursday; Remote‑Work Bank for additional flexibility.

We must ensure we don't repeat job title. Not include any boilerplate like EEO etc. Now craft the About the role paragraph: combine company description and opportunity. Company description: "SoftWriters develops innovative IT solutions that empower long-term care (LTC) pharmacies to deliver life-saving medications more efficiently and accurately. As a voted top workplace in Pittsburgh, we combine meaningful work with a collaborative culture where your contributions directly impact patient care." Opportunity: "We're seeking a Director of AI Operations & Delivery to join our growing Alpha Lab team and help shape the future of healthcare technology. In this role, you'll lead the execution and delivery of SoftWriters' agentic AI platform initiatives, driving operational excellence across product and engineering teams while helping define the next generation of AI-powered healthcare solutions. Location: Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday) Reports to: VP of AI" We can combine into a paragraph. Now Responsibilities bullets as above. Requirements bullets. Qualifications bullets. Benefits bullets: list items: - Meaningful work: leadership directly influences AI-powered solutions that improve patient safety and enable pharmacies to deliver better care. - Modern work environment: brand new, high-tech office with stunning Pittsburgh city views, located directly on the North Shore waterfront. - Recognized top workplace: consistently voted one of the best places to work in Pittsburgh. - Work‑life balance: hybrid work policy with flexible hours, Remote‑Work Bank for additional flexibility, paid parking provided, PTO day on your birthday, floating holidays. - Comprehensive benefits: competitive salary, 100% paid parental leave, 401(k) with company match, comprehensive medical, dental, and vision coverage, life and disability insurance. - Growth‑focused culture: continuous learning and development opportunities, cross‑functional collaboration, clear career advancement paths. - Our values in action: innovators, thought leaders, teachers; accountability and ownership; customer‑centric; unyielding integrity; one team, family spirit. We could combine some. Pay: "Competitive salary" (already mentioned in benefits but we can still have Pay section with that line.) Schedule: "Hybrid work policy with flexible hours; core office days Tuesday, Wednesday, Thursday; Remote‑Work Bank for additional flexibility." Now produce HTML. Check for any duplicated lines: we have competitive salary both in Benefits and Pay; maybe okay but could be duplicate. Might be considered duplication; we could remove from Benefits to avoid duplication. But Benefits section includes comprehensive benefits list; we could keep competitive salary there and Pay section maybe redundant. Better to keep Pay section only with competitive salary and remove from Benefits to avoid duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove competitive salary from Benefits, we are still preserving it in Pay section, so it's preserved. So we can omit from