Vice President, Imaging Workflow Products

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who are we and why should you join us?" then description of company, then "Your Opportunity", then "How You'll Make An Impact" with subheadings, then "What You'll Bring" with subheadings, then "Learn More About ConcertAI". Also there is EEO statement which we must remove as boilerplate. Also remove navigation/legal/EEO etc. Also remove application instructions (none present). Also remove duplicated lines. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content to these headings appropriately. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings where applicable. However the posting does not have explicit sections like "About the role", "Responsibilities", etc. We need to infer and map content accordingly. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections have content. We have content about company mission (About the role? maybe "About the role" could be used for description of role and company). Then "Your Opportunity" could be "Responsibilities"? Actually "Your Opportunity" describes the role, product leader responsibilities. Could map to "Responsibilities". Then "How You'll Make An Impact" includes subheadings like Product Strategy..., Ownership of Product P&L metrics..., AI-First..., Commercial & Enterprise Growth..., Team Leadership..., Cross-Functional Executive Leadership... Those could be considered "Requirements" or "Qualifications"? Actually they are more like responsibilities/duties. But we already used Responsibilities for opportunity. Maybe we can use "Qualifications" for "What You'll Bring". That section includes required experience, skills. So we can map "What You'll Bring" to "Qualifications" (or "Requirements"). The instruction list includes both Requirements and Qualifications; we can choose one. Probably use "Qualifications" for the skills/experience. Then "Learn More About ConcertAI" could be "About the role"? Actually we already used About the role for company description. Could also use "About the role" for company overview. The "Learn More About ConcertAI" is more about company, could be part of About the role. But we should not duplicate. Maybe we keep About the role as company description (first paragraph). Then we can have Responsibilities (Your Opportunity + How You'll Make An Impact). Then Qualifications (What You'll Bring). Then maybe Skills? Could split out skills from qualifications but we can keep Qualifications only. Benefits, Pay, Schedule: not present, so we should not include those sections. We must not include boilerplate like EEO. Also remove duplicated lines. We need to preserve all substantive information. So we need to include all details from the posting except boilerplate. We need to format using

for each section heading, then content using

for prose and

• for lists. We need to decide how to structure lists: For responsibilities we have bullet-like sentences. Could convert each sentence into
• . For qualifications we have bullet points under each subheading. Could also use lists. We must not invent or summarize away detail. Must preserve all specifics: numbers, years, etc. Let's extract content. First part: "Who are we and why should you join us?ConcertAI is building the future of precision medicine. We use advanced artificial intelligence and real-world data to transform how healthcare and life sciences generate evidence, make decisions, and improve patient outcomes—starting in oncology and rapidly expanding across therapeutic areas. Our teams partner with the world’s leading pharmaceutical companies, providers, and research organizations to solve some of healthcare’s most complex challenges. At the core of our innovation is Cara, our next-generation AI platform that unlocks powerful insights from complex clinical, imaging, and molecular data. Combined with our Precision Suite—which unifies real-world data, advanced analytics, and scalable evidence generation—these solutions are transforming how clinical development, regulatory, and commercialization decisions are made. ConcertAI brings together a portfolio of purpose-built solutions, including TeraRecon, an industry leader in advanced imaging and AI-driven visualization, and CancerLinQ, the ASCO-originated oncology platform advancing care quality and large-scale discovery. Joining ConcertAI means working alongside bold thinkers, builders, and healthcare experts on innovative, high-impact products that directly improve patient lives. You’ll be part of a fast-growing, mission-driven organization at the forefront of AI-enabled healthcare, with meaningful opportunities for growth and leadership." That's the company description. Second: "Your OpportunityWe are seeking a visionary, AI-first, Product Leader to lead productization and GoToMarket (GTM) for our AI-driven Imaging Workflow Solutions. This role will own the product vision, strategy, commercialization, and product P&L metrics for an intelligent clinical pathways platform designed to improve patient outcomes while maximizing reimbursement performance. This is a builder and GTM role for a new productline within TeraRecon. You will define and develop an AI-first product that embeds clinical evidence, imaging workflow & process optimization, predictive imaging analytics, payer logic related to the entire care pathway, and documentation automation directly into clinical and operational workflows. You will operate with urgency and accountability — driving measurable clinical impact, accelerating prior authorization, reducing denials, and delivering sustainable revenue growth. This is a customer facing role based in the USA that will work with global software development and Quality/Regulatory teams — while partnering closely with Sales to win lighthouse customers and close the first wave of enterprise deals." Third: "How You'll Make An ImpactProduct Strategy, Product Management, & Market LeadershipDefine and execute the long-term strategy for AI-driven clinical pathway and reimbursement solutions. Position TeraRecon as the market leader, develop differentiated value propositions, own pricing strategy, and drive ecosystem expansion. Ownership of Product P&L metricsOwn revenue growth, margins, and overall financial performance. Lead forecasting, investment planning, cost discipline, and executive KPI reporting while ensuring measurable customer ROI. AI-First, AI-Fast Product ExecutionDeliver scalable, enterprise-grade AI solutions/technologies embedded within EHR workflows. Operationalize predictive models, integrate payer logic and coding guidance, and drive rapid innovation cycles. Commercial & Enterprise GrowthPartner with Sales to win lighthouse clients, support strategic deals, ensure successful implementations, and translate outcomes into repeatable go-to-market (GTM) momentum. Team LeadershipLead and align the India-based software development, global AI development, and global Compliance teams with product priorities, ensuring operational excellence and seamless global collaboration. Cross-Functional Executive LeadershipCollaborate across Engineering, Data Science, Clinical, Revenue Cycle, and Regulatory teams to drive adoption, maintain compliance, and build a high-performing, AI-native organization." Fourth: "What You'll BringProduct & Commercial Leadership10+ years of leadership experience in healthcare product, clinical transformation, AI-driven solutions, or medical imaging. Proven Product management/ownership with demonstrated revenue growth. Experience launching, scaling, and commercializing enterprise healthcare or imaging solutions. Having a track record supporting or closing complex enterprise healthcare sales Clinical, Imaging & Reimbursement Expertise10+ years in medical imaging workflows, clinical care, or imaging management within U.S. healthcare providers.5+ years in clinical transformation, utilization review, imaging economics, or pathway development. Working knowledge of reimbursement models (FFS, DRG, bundled payments, value-based care). Has a strong understanding of payer requirements, coding practices, and prior authorization processes. Experience collaborating with revenue cycle, payer, or pre-authorization teams. Ability to connect clinical workflows with financial and operational performance Technology & Data FluencyExperience leading AI-enabled, analytics-driven, or medical imaging software solutions. Familiarity with EHR integration (Epic, Cerner) and practice management systems. Has experience with workflow design and cross-functional implementation. Strong data analysis skills to track outcomes, trends, and reimbursement metrics Leadership ProfileStrategic, systems-oriented leader who understands both clinical and business dynamics. Builder mindset; comfortable operating in matrixed, cross-functional organizations. Detail-oriented and proactive in managing payer-policy complexities. Strong communicator with a passion for clinical and financial excellence. Action-oriented leader with a focus on measurable results" Fifth: "Learn More About ConcertAIOur team at ConcertAI is dedicated to transforming healthcare decision-making through the application of RWE and AI to improve patient outcomes. We work in a fast-paced, dynamic, high-performing culture where diversity, collaboration, and innovation are valued. Join us on our quest to create a world free of disease. Learn more about ConcertAI at www.concertai.com , or follow us on LinkedIn. Serving 1,300 clinical sites globally, TeraRecon - a ConcertAI company - is a Best in KLAS solution provider for AI-empowered radiology, oncology, cardiology, neurology, and vascular surgery. In the future, the combination with ConcertAI could bring a single, advanced AI-augmented diagnosis and interpretation capability from clinical trials to patient care." We need to remove EEO statement. Now map sections. Option: Use

  About the role

  for company description (first part). Then

  Responsibilities

  for "Your Opportunity" + "How You'll Make An Impact". Then

  Qualifications

  for "What You'll Bring". Then maybe

  About ConcertAI

  for "Learn More About ConcertAI". But the instruction list includes "About the role" as example heading; we could also use "About the role" for company description and "Learn More About ConcertAI" could be considered part of that, but we could also make a separate section like "About the company". However the instruction says use those headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot use other headings, but to follow the pattern we should likely stick to those. However we have content that doesn't fit neatly into Benefits, Pay, Schedule. We could omit those sections. For "Learn More About ConcertAI", maybe we can incorporate into About the role (since it's about the company). So we can merge that content into About the role section. Thus we will have:

  About the role

  containing the company description + Learn More About ConcertAI content (merged). Ensure we don't repeat.

  Responsibilities

  containing Your Opportunity + How You'll Make An Impact content.

  Qualifications

  containing What You'll Bring content. We should not include Requirements, Skills, Benefits, Pay, Schedule. Now we need to format content with

  for prose and

  • for lists. We need to decide where to use lists. For responsibilities we have multiple bullet-like items: product vision, strategy, commercialization, product P&L metrics; define and develop AI-first product; operate with urgency; customer facing role; work with global teams; partner with Sales; etc. Also the How You'll Make An Impact section has subheadings each with multiple sentences. Could treat each subheading as a
  • or we could keep prose. The instruction: "Use
    • for any list of duties/requirements/benefits". So if we have a list of duties, we should use
      • . The responsibilities section is essentially a list of duties. So we can break them into
      • items. Similarly qualifications: list of requirements (years experience, etc.) can be
        • . We must preserve all details, not lose any. Let's extract responsibilities details: From Your Opportunity: - Seeking a visionary, AI-first, Product Leader to lead productization and GoToMarket (GT