Senior Manager, Strategy and Operations
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no heading for Senior Manager etc.
We must not put Job ID/requisition numbers as headings (none present).
We must output only HTML fragment.
Let's craft.
First, About the role: combine the introductory paragraphs into maybe two
elements.
Content:
"Passionate about precision medicine and advancing the healthcare industry? Recent advancements in underlying technology have finally made it possible for AI to impact clinical care in a meaningful way. Tempus' proprietary platform connects an entire ecosystem of real-world evidence to deliver real-time, actionable insights to physicians, providing critical information about the right treatments for the right patients, at the right time. Our ECG-AI team is accelerating cardiac care by deploying AI-powered solutions designed to support clinicians in identifying patients at risk for cardiovascular conditions before critical events occur by using a pervasive, inexpensive diagnostic tool, the ECG. We are seeking a highly motivated, execution-oriented Senior Manager, Strategy & Operations to join our growing ECG-AI team. This individual will be pivotal in translating our advanced AI algorithms into everyday clinical practice. In this role, you will drive the operational blueprint for how ECG-AI is integrated into clinical workflows at our healthcare partner sites. You will lead clinical rollout strategy, manage long-term site relationships, track technology adoption, and spearhead high-priority strategic initiatives. This role demands a strategic thinker who thrives in ambiguity, possesses strong cross-functional management skills, and can move seamlessly between high-level strategy and hands-on execution."
We can split into maybe two paragraphs for readability but not required.
Now Responsibilities: Under What You'll Do, we have three sections: Clinical Operations & Partner Readiness, Account & Relationship Management, Strategic Initiatives. Each has bullet points.
We need to output as
- for any list of duties/requirements/benefits. So we can make a list for each subsection? Could combine all duties into one list but better to preserve structure. Could have
for each subsection? But the rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those top-level sections. Inside we can use
or
- . So we should not add extra headings inside Responsibilities. So we will just list all duties as a single
- maybe with sub-bullets? But we cannot nest
inside - ? We could but not specified. Safer to just list all duty items as separate
- preserving the text.
Thus we need to extract each bullet point:
From Clinical Operations & Partner Readiness:
- Design and Refine Clinical Workflows: Define, test, and implement standard operating playbooks detailing how ECG-AI insights are delivered, viewed, and actioned by clinical teams within their native workflows.
- Orchestrate Rollouts: Serve as the central operational quarterback for new site launches, aligning project timelines cross-functionally with Tempus connectivity, product, and partner-site technical teams without being responsible for the underlying IT build.
- Onboard Clinical Staff: Act as the operational face of Tempus during launches, educating and training hospital stakeholders (physicians, nursing staff, clinical coordinators, and administrators) on operational workflows and clinical utility.
From Account & Relationship Management:
- Drive Adoption: Serve as the primary relationship owner post-launch, monitoring how clinicians engage with ECG-AI and identifying operational levers to improve software utilization and clinical integration.
- Manage Account Health: Continually evaluate site performance and collaboration health, bridging the gap between clinical users and Tempus Product/Engineering teams to communicate user feedback and feature requests.
- Track Care Pathways: Collaborate with partner site leadership to track patient follow-up rates, ensuring that flagged patients are successfully directed to the correct diagnostic and treatment pathways.
From Strategic Initiatives:
- Scale the Program: Identify, evaluate, and execute strategic projects that improve deployment speed, scale account management processes, and lower the barriers to clinical adoption across a growing list of major health systems.
- Build Operational Infrastructure: Turn ambiguous, early-stage challenges into repeatable, documented processes that the broader team can use to scale the ECG-AI footprint.
- Support Commercial & Market Growth: Support market expansion initiatives, including clinical validation partnerships, ROI case studies, and cross-functional preparation for new algorithmic expansions.
We'll put each as
- .
Now Requirements: from "Qualifications Required:" list:
- Experience: 6+ years of professional experience in strategy and operations, management consulting, healthcare operations, customer success, or project management within healthcare, healthtech, or life sciences.
- Navigating Ambiguity: Proven ability to thrive in a fast-paced, rapidly evolving environment. A track record of building structure, processes, and clarity out of ambiguous situations.
- Cross-Functional Collaboration: Exceptional relationship-building skills with a proven ability to partner effectively with both technical teams (EHR, data engineering, connectivity) and non-technical stakeholders (physicians, hospital executives).
- Project Management & Execution: Strong organizational skills with the ability to manage multiple complex, multi-stakeholder account rollouts simultaneously.
- Communication: Excellent presentation and interpersonal skills, with the ability to establish credibility and influence clinical and administrative leadership.
We'll output as
- .
Now Qualifications: Preferred Background, Education, Domain Knowledge.
Content:
- Preferred Background: Prior experience working in a high-growth startup or a management consulting firm is highly encouraged.
- Education: MBA, MHA, or equivalent advanced degree is a plus, but not required.
- Domain Knowledge: Familiarity with hospital health systems, clinical workflows, or cardiology services.
We'll output as
- .
Now Benefits: "Tempus offers a full range of benefits, which may include incentive compensation, restricted stock units, medical and other benefits depending on the position."
We'll output as
maybe but rule says use
- for any list of benefits. This is not a list but a sentence. Could treat as
. However they said use
- for any list of duties/requirements/benefits. Since it's not a list, we can use
. But we could also split into list items: incentive compensation, restricted stock units, medical and other benefits. But the sentence says "may include incentive compensation, restricted stock units, medical and other benefits depending on the position." Could make list: incentive compensation, restricted stock units, medical and other benefits. However that might be summarizing. Safer to keep as
.
Now Pay: "$130,000-$165,000 The expected salary range may vary for other locations. Actual salary may vary based on qualifications and experience."
We'll output as
.
Now ensure we removed EEO etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Benefits
...
Pay
...
No Schedule.
Make sure to not include extra whitespace? It's fine.
Now craft the HTML.
Let's write the About the role paragraph(s). Could be two paragraphs but we
for prose. We must not repeat job title as heading. So no heading for Senior Manager etc. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment. Let's craft. First, About the role: combine the introductory paragraphs into maybe two
elements. Content: "Passionate about precision medicine and advancing the healthcare industry? Recent advancements in underlying technology have finally made it possible for AI to impact clinical care in a meaningful way. Tempus' proprietary platform connects an entire ecosystem of real-world evidence to deliver real-time, actionable insights to physicians, providing critical information about the right treatments for the right patients, at the right time. Our ECG-AI team is accelerating cardiac care by deploying AI-powered solutions designed to support clinicians in identifying patients at risk for cardiovascular conditions before critical events occur by using a pervasive, inexpensive diagnostic tool, the ECG. We are seeking a highly motivated, execution-oriented Senior Manager, Strategy & Operations to join our growing ECG-AI team. This individual will be pivotal in translating our advanced AI algorithms into everyday clinical practice. In this role, you will drive the operational blueprint for how ECG-AI is integrated into clinical workflows at our healthcare partner sites. You will lead clinical rollout strategy, manage long-term site relationships, track technology adoption, and spearhead high-priority strategic initiatives. This role demands a strategic thinker who thrives in ambiguity, possesses strong cross-functional management skills, and can move seamlessly between high-level strategy and hands-on execution." We can split into maybe two paragraphs for readability but not required. Now Responsibilities: Under What You'll Do, we have three sections: Clinical Operations & Partner Readiness, Account & Relationship Management, Strategic Initiatives. Each has bullet points. We need to output as
- for any list of duties/requirements/benefits. So we can make a list for each subsection? Could combine all duties into one list but better to preserve structure. Could have
for each subsection? But the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those top-level sections. Inside we can use
or
- . So we should not add extra headings inside Responsibilities. So we will just list all duties as a single
- maybe with sub-bullets? But we cannot nest
- inside
- ? We could but not specified. Safer to just list all duty items as separate
- preserving the text. Thus we need to extract each bullet point: From Clinical Operations & Partner Readiness: - Design and Refine Clinical Workflows: Define, test, and implement standard operating playbooks detailing how ECG-AI insights are delivered, viewed, and actioned by clinical teams within their native workflows. - Orchestrate Rollouts: Serve as the central operational quarterback for new site launches, aligning project timelines cross-functionally with Tempus connectivity, product, and partner-site technical teams without being responsible for the underlying IT build. - Onboard Clinical Staff: Act as the operational face of Tempus during launches, educating and training hospital stakeholders (physicians, nursing staff, clinical coordinators, and administrators) on operational workflows and clinical utility. From Account & Relationship Management: - Drive Adoption: Serve as the primary relationship owner post-launch, monitoring how clinicians engage with ECG-AI and identifying operational levers to improve software utilization and clinical integration. - Manage Account Health: Continually evaluate site performance and collaboration health, bridging the gap between clinical users and Tempus Product/Engineering teams to communicate user feedback and feature requests. - Track Care Pathways: Collaborate with partner site leadership to track patient follow-up rates, ensuring that flagged patients are successfully directed to the correct diagnostic and treatment pathways. From Strategic Initiatives: - Scale the Program: Identify, evaluate, and execute strategic projects that improve deployment speed, scale account management processes, and lower the barriers to clinical adoption across a growing list of major health systems. - Build Operational Infrastructure: Turn ambiguous, early-stage challenges into repeatable, documented processes that the broader team can use to scale the ECG-AI footprint. - Support Commercial & Market Growth: Support market expansion initiatives, including clinical validation partnerships, ROI case studies, and cross-functional preparation for new algorithmic expansions. We'll put each as
- .
Now Requirements: from "Qualifications Required:" list:
- Experience: 6+ years of professional experience in strategy and operations, management consulting, healthcare operations, customer success, or project management within healthcare, healthtech, or life sciences.
- Navigating Ambiguity: Proven ability to thrive in a fast-paced, rapidly evolving environment. A track record of building structure, processes, and clarity out of ambiguous situations.
- Cross-Functional Collaboration: Exceptional relationship-building skills with a proven ability to partner effectively with both technical teams (EHR, data engineering, connectivity) and non-technical stakeholders (physicians, hospital executives).
- Project Management & Execution: Strong organizational skills with the ability to manage multiple complex, multi-stakeholder account rollouts simultaneously.
- Communication: Excellent presentation and interpersonal skills, with the ability to establish credibility and influence clinical and administrative leadership.
We'll output as
- .
Now Qualifications: Preferred Background, Education, Domain Knowledge.
Content:
- Preferred Background: Prior experience working in a high-growth startup or a management consulting firm is highly encouraged.
- Education: MBA, MHA, or equivalent advanced degree is a plus, but not required.
- Domain Knowledge: Familiarity with hospital health systems, clinical workflows, or cardiology services.
We'll output as
- .
Now Benefits: "Tempus offers a full range of benefits, which may include incentive compensation, restricted stock units, medical and other benefits depending on the position."
We'll output as
maybe but rule says use
- for any list of benefits. This is not a list but a sentence. Could treat as
. However they said use
- for any list of duties/requirements/benefits. Since it's not a list, we can use
. But we could also split into list items: incentive compensation, restricted stock units, medical and other benefits. But the sentence says "may include incentive compensation, restricted stock units, medical and other benefits depending on the position." Could make list: incentive compensation, restricted stock units, medical and other benefits. However that might be summarizing. Safer to keep as
. Now Pay: "$130,000-$165,000 The expected salary range may vary for other locations. Actual salary may vary based on qualifications and experience." We'll output as
. Now ensure we removed EEO etc. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
-
...
Qualifications
-
...
Benefits
...
Pay
...
No Schedule. Make sure to not include extra whitespace? It's fine. Now craft the HTML. Let's write the About the role paragraph(s). Could be two paragraphs but we
- for any list of duties/requirements/benefits. Since it's not a list, we can use
- for any list of benefits. This is not a list but a sentence. Could treat as
- .
Now Benefits: "Tempus offers a full range of benefits, which may include incentive compensation, restricted stock units, medical and other benefits depending on the position."
We'll output as
- .
Now Qualifications: Preferred Background, Education, Domain Knowledge.
Content:
- Preferred Background: Prior experience working in a high-growth startup or a management consulting firm is highly encouraged.
- Education: MBA, MHA, or equivalent advanced degree is a plus, but not required.
- Domain Knowledge: Familiarity with hospital health systems, clinical workflows, or cardiology services.
We'll output as
- maybe with sub-bullets? But we cannot nest
- . So we should not add extra headings inside Responsibilities. So we will just list all duties as a single