AI full stack Engineer

We need to output HTML fragment with sections for headings: 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 like EEO, scam warnings, application instructions, navigation, cookie, legal. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph about McKesson: "McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care. What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you." Then: "We are seeking a highly skilled and motivated AI Full Stack Software Engineer to join our innovative team at CMM. In this role, you will be instrumental in designing, developing, and deploying end-to-end AI-powered solutions that enhance our healthcare products and services. You will work across the full stack, from front-end user interfaces to back-end AI model integration and data pipelines." That's about the role. Then "Responsibilities" heading with bullet list: - Develop and deliver AI-driven enterprise quality software applications. - Build scalable applications integrating Large Language Models and other AI tools (e.g. voice recognition, document parsing, image parsing, text to speech, RAG) into new and legacy codebases - Design and optimize data pipelines and datasets for AI system development and testing. - Communicate modern AI concepts (LLMs, vector databases etc.) to non-technical audiences - Iteratively craft effective prompts to maximize LLM performance and implement prompt caching strategies - Maintain prompt libraries & benchmark performance - Fine-tune & serve GPT-family, Llama - Develop AI agents Semantic Kernel Prototype co-pilot experiences & autonomous workflows - Fully document all work at both the code level and application level. - The ability to learn and adapt in a changing environment. - Collaborate with other staff and outside stakeholders on large projects. - Must be passionate about creating solutions and solving complex problems. - Priority will be given to candidates who reside in the Atlanta, GA, and Columbus, OH metropolitan areas. - We are unable to provide sponsorship for this role presently or in the future. Then "Minimum Qualifications" heading with bullet list: - Minimum 4+ years of experience in Software development. - B.S. degree in Computer Science or related engineering discipline, or equivalent experience Then "Critical Skills" heading with bullet list: - Minimum 4+ years of experience in developing AI-enhanced applications using LLMs, voice, image, or speech models. - Proficiency in Python and AI related python libraries such as openai, tensorflow, pytorch - AI System Evaluation & Optimization: Proficient in sensitivity metrics (precision, recall, F1-score, AUC-ROC) and MLOps for scalable, cost-efficient AI deployment. - RAG Development: Skilled in building RAG systems from scratch or with LangChain/LlamaIndex, using vector databases for context-aware LLM applications. - Experience using AI coding tools (e.g. Github Copilot, Cursor, Codeium/Windsurf) - LLM Cost Optimization: Expert in managing LLM costs (token pricing, input/output rates) via prompt caching, batching, and quantization. - LLM Knowledge: Deep understanding of LLM advancements (GPT-3.5 vs GPT-4 vs o1/”thinking” models) for informed model selection and tuning. Then "Preferred Skills" heading with bullet list: - Exceptional analytical skills to extract actionable insights from data - Healthcare Domain Expertise, Translate clinical/business needs into AI solutions - Proficiency in creating Node.js web apps (e.g. Express.js) - Experience with cloud (AWS/GCP/Azure) - Effective communication skills to collaborate with technical, DevOps and product management teams. - Experience with Git, Docker, and Kubernetes Then "We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards. This is determined by several factors, including performance, experience and skills, equity, regular job market evaluations, and geographical markets. The pay range shown below is aligned with McKesson's pay philosophy, and pay will always be compliant with any applicable regulations. In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered. For more information regarding benefits at McKesson, please click here. Our Base Pay Range for this position $110,300 - $183,800" Thus we have Pay info: Base Pay Range $110,300 - $183,800. Also mention other compensation like annual bonus or long-term incentive opportunities may be offered. Benefits: mention "For more information regarding benefits at McKesson, please click here." That's not specific benefit details, just a link. According to rules: we should not create Benefits section unless posting actually states them. It says "For more information regarding benefits at McKesson, please click here." That's not specific benefit content; it's a referral. Likely we should not create a Benefits section because no specific benefits listed. However we could include a short paragraph about benefits? The rule: "IMPORTANT: 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")". The benefits statement is vague; not specific. So we should omit Benefits section. Pay: we have specific base pay range. Also mention other compensation like annual bonus or long-term incentive opportunities may be offered. That's specific enough? It mentions other compensation types. So we can include Pay section with that info. Schedule: no mention of schedule (e.g., full-time, remote, hybrid). Not present. So omit Schedule. Now sections: About the role (intro paragraph), Responsibilities, Requirements (maybe combine Minimum Qualifications and Critical Skills? The spec says we can have Requirements section. We need to decide: The headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have Minimum Qualifications (education, years experience). That's like Requirements. We have Critical Skills (specific technical skills). That's like Skills. We have Preferred Skills (additional). Could combine into Skills section? But we have both required and preferred skills. Could put required skills under Skills, and maybe note preferred? But we must not invent sections. We could have Requirements (minimum qualifications) and Skills (critical skills + preferred skills). Or we could have Qualifications (education) and Skills (critical). However we have both Minimum Qualifications and Critical Skills separate. The allowed headings include Qualifications and Skills. So we can put Minimum Qualifications under Qualifications, and Critical Skills under Skills. Preferred Skills could also go under Skills as additional bullet points maybe with note "Preferred". That's okay. Thus: - About the role: intro paragraphs (maybe two paragraphs). We'll wrap in

. - Responsibilities:

• ... each bullet. - Qualifications:
  • Minimum 4+ years of experience in Software development.
  • B.S. degree in Computer Science or related engineering discipline, or equivalent experience
  - Skills: combine Critical Skills and Preferred Skills. Could separate into required and preferred but we can just list all. Might be long but okay. We need to ensure we don't include filler like "commensurate with experience". Not present. Pay:

  Base Pay Range: $110,300 - $183,800. In addition to base pay, other compensation such as an annual bonus or long‑term incentive opportunities may be offered.

  We should not include the line about clicking here for benefits. We must not include any boilerplate like EEO, scam warnings, etc. Now produce HTML fragment. Make sure to use

  for each section heading. Order: About the role, Responsibilities, Qualifications, Skills, Pay. Check that we didn't miss any substantive content: The line "Priority will be given to candidates who reside in the Atlanta, GA, and Columbus, OH metropolitan areas." and "We are unable to provide sponsorship for this role presently or in the future." Those are under Responsibilities originally but could be considered Requirements or maybe Qualifications? They are eligibility constraints. Could be placed under Requirements or Qualifications. Since we have Qualifications for education/experience, we could add those as additional list items under Qualifications (or maybe under Requirements). But we don't have a Requirements section; we have Qualifications. Could add them there. However they are not exactly qualifications but location preference and sponsorship. Might be better to put them under Responsibilities? They are not responsibilities. Could create a separate section like "Eligibility" but not allowed. Could fold into Qualifications as extra bullets. The rule: preserve ALL substantive information. So we need to include them somewhere. Since we have no explicit section for them, we could add them under Qualifications as additional bullets (makes sense). Or we could add a short paragraph after Qualifications. But we must use

  • for any list of duties/requirements/benefits. These are requirements/eligibility, so list. Thus Qualifications list items: - Minimum 4+ years of experience in Software development. - B.S. degree in Computer Science or related engineering discipline, or equivalent experience - Priority will be given to candidates who reside in the Atlanta, GA, and Columbus, OH metropolitan areas. - We are unable to provide sponsorship for this role presently or in the future. Now Skills: list all critical and preferred skills. Let's enumerate: Critical Skills: - Minimum 4+ years of experience in developing AI-enhanced applications using LLMs, voice, image, or speech models. - Proficiency in Python and AI related python libraries such as openai, tensorflow, pytorch - AI System Evaluation & Optimization: Proficient in sensitivity metrics (precision, recall, F1-score, AUC-ROC) and MLOps for scalable, cost-efficient AI deployment. - RAG Development: Skilled in building RAG systems from scratch or with LangChain/LlamaIndex, using vector databases for context-aware LLM applications. - Experience using AI coding tools (e.g. Github Copilot, Cursor, Codeium/Windsurf) - LLM Cost Optimization: Expert in managing LLM costs (token pricing, input/output rates) via prompt caching, batching, and quantization. - LLM Knowledge: Deep understanding of LLM advancements (GPT-3.5 vs GPT-4 vs o1/”thinking” models) for informed model selection and tuning. Preferred Skills: - Exceptional analytical skills to extract actionable insights from data - Healthcare Domain Expertise, Translate clinical/business needs into AI solutions - Proficiency in creating Node.js web apps (e.g. Express.js) - Experience with cloud (AWS/GCP/Azure) - Effective communication skills to collaborate with technical, DevOps and product management teams. - Experience with Git, Docker, and Kubernetes We could combine them. Now Responsibilities list we have many bullets. Let's list them exactly as given. Responsibilities bullets: - Develop and deliver AI-driven enterprise quality software applications. - Build scalable applications integrating Large Language Models and other AI tools (e.g. voice recognition, document parsing, image parsing, text to speech, RAG) into new and legacy codebases - Design and optimize data pipelines and datasets for AI system development and testing. - Communicate modern AI concepts (LLMs, vector databases etc.) to non-technical audiences - Iteratively craft effective prompts to maximize LLM performance and implement prompt caching strategies - Maintain prompt libraries & benchmark performance - Fine-t