Lead, Cost Modeling Scientist - Medicines for All

We need to produce HTML fragment with sections: About the role? The posting includes Job Summary, responsibilities, qualifications, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info. We need to parse the posting: It has Job Summary (intro), then responsibilities broken into Techno‑Economic Modeling, Data Management & Analysis, Collaboration & Project Support, Continuous Improvement. Then Qualifications (Required Qualifications, Preferred Qualifications). Then Additional Details includes Salary Range, Benefits, Reporting Structure, Work Environment, FLSA Exemption Status, Hours per Week, Restricted Position, ORP Eligible, Flexible Work Arrangement, University Job Title, Sponsorship, Contact. We need to map to sections: About the role (maybe from Job Summary). Responsibilities (list of duties). Requirements (maybe qualifications). Skills (maybe specific skills). Benefits (explicit). Pay (salary range). Schedule (hours per week). Also maybe we could include Work Environment? Not a standard heading but we could put under About the role or maybe not needed. The instructions: Use headings for those specific headings only. So we should create sections for those headings that have content. We need to avoid repeating job title as heading. So no heading for "Lead, Cost Modeling Scientist". Also avoid Job ID etc. We need to output only HTML fragment, no /, no markdown fences. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit boilerplate besides maybe contact email? Contact is substantive? It's contact email; maybe we keep as part of About the role? Might be considered application instruction? It says "Contact: m4all@vcu.edu". That's like application instruction; we should remove application instructions. So we should drop contact line. Also we need to drop duplicated lines. There's no duplication. We need to ensure we don't include sections with filler like "commensurate with experience". Not present. We need to include Pay section only if posting states salary range. It does: "Salary Range: The annual salary for this position is up to $125,000, with the final compensation determined based on the selected candidate’s unique qualifications, experience, and skills." So we include Pay. Benefits: posting includes Benefits paragraph. So include Benefits. Schedule: posting includes "FLSA Exemption Status: Exempt Hours per Week: Minimum of 40 hours/week; Monday - Friday (day shift)". So schedule info: minimum 40 hours/week, Monday-Friday day shift. Also maybe "Flexible Work Arrangement: Yes - This role is hybrid..." That's more about work arrangement but schedule heading expects hours per week. We'll include schedule with that info. We also might include "About the role" from Job Summary paragraph. Responsibilities: we have four sub-sections each with bullet-like sentences. We'll turn each bullet into

• . Could group under
  . Requirements: maybe combine Required Qualifications and Preferred Qualifications? The heading "Requirements" could contain both required and preferred? But we have separate headings for Qualifications and Skills. The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put qualifications vs skills vs requirements. Usually "Requirements" could be required qualifications; "Qualifications" could be preferred? Or "Skills" for specific skills. We need to map content. We have Required Qualifications (education, experience, knowledge, abilities). Preferred Qualifications (experience in pharma manufacturing, etc.). Also there is a list of skills: strong foundational knowledge of Organic chemistry, ability to evaluate synthetic routes, demonstrated experience leading techno-economic evaluations, ability to do process mapping, unit operation and cycle time, advanced proficiency in Excel, exceptional written communication skills, high proficiency with spreadsheets, ChemDraw, MS Office, Google Drive, ability to guide others, previous experience with techno economic analysis is a plus, strong written and verbal communication skills, excellent analytical, problem-solving, reasoning abilities, ability to work under pressure, demonstrated ability to work in and foster environment of respect, highly motivated, self-directed, innovative, able to work independently, ability to manage and analyze large datasets, strong collaboration skills, demonstrated ability to learn new concepts quickly. We could split: Required Qualifications heading for education/experience; Skills heading for abilities/tools; Qualifications heading for preferred qualifications? But we already have Qualifications heading; maybe we put both required and preferred under Qualifications? But then we would duplicate. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Qualifications section, and Skills section for specific technical skills (Excel, ChemDraw, etc.). But we also have many soft skills. Let's think: The posting has "Qualifications:" heading with Required and Preferred subheadings. So we could map that directly to a

  Qualifications

  containing both required and preferred as lists. Then we could have a

  Skills

  for the specific abilities like "Strong foundational knowledge of Organic chemistry", "Ability to evaluate synthetic routes", etc. However many of those are also under Required Qualifications. Might cause duplication. But we must preserve all substantive information; we can include them in both sections? That would duplicate content, which is not allowed (do not repeat). So we need to decide a non-duplicative split. Option: Use Qualifications for education/experience requirements (required and preferred). Use Skills for the abilities/tools (technical and soft skills). That seems reasonable: Qualifications section lists education, experience, degrees; Skills section lists knowledge, abilities, proficiencies. Let's extract: Qualifications (Required): - Ph.D. or Master’s degree in Chemistry, Chemical Engineering, Computational Chemistry, Data Science, Biology, or a closely related field - Candidates with a Bachelor’s degree and 4-5+ years of progressively responsible experience in process economics, chemical process development, or related areas will also be considered. - Candidates with a combination of education and substantial amount of progressive, relevant experience will also be considered. - Strong foundational knowledge of Organic chemistry and the ability to evaluate synthetic routes from both a technical and economic perspective. - Demonstrated experience leading or overseeing techno‑economic evaluations, including the ability to assess multiple chemical processes and guide teams toward cost‑effective, scalable options. - Ability to do process mapping, unit operation and cycle time of chemical processes. - Advanced proficiency in Excel and related analytical tools, with the ability to design, audit, and improve complex cost models involving material, labor, equipment, and process‑level assumptions. - Exceptional written communication skills, with experience preparing decision‑ready reports and recommendations for technical teams and leadership. - High proficiency with spreadsheets (Excel, Google Sheets, Smartsheet), ChemDraw, MS Office, and Google Drive, with the ability to guide others in best practices. - Previous experience with techno economic analysis or chemical route analysis is a plus but not required. - Strong written and verbal communication skills, with the ability to convey information clearly to diverse audiences. - Excellent analytical, problem‑solving, and reasoning abilities, with the capacity to work under pressure and meet tight deadlines. - Demonstrated ability to work in and foster an environment of respect, professionalism and civility with a population of faculty, staff, and students from all backgrounds and experiences, or a commitment to do so as a staff member at VCU. - Highly motivated, self‑directed, innovative, and able to work independently. - Ability to manage and analyze large datasets with accuracy and attention to detail. - Strong collaboration skills and the ability to work effectively with researchers and cross‑functional teams, while demonstrating behaviors aligned with M4ALL’s core values and organizational culture. - Demonstrated ability to learn new concepts quickly and adapt to evolving project needs. Preferred Qualifications: - Experience in pharmaceutical manufacturing and process development of active pharmaceutical ingredients (APIs). - Experience in chemical process development, route scouting, and scale-up is preferred. - Experience with data analysis tools (e.g., Python, R, Scikit-learn, PyTorch, etc.) is a plus. Now Skills: maybe we could extract the specific technical skills: Advanced proficiency in Excel, ability to design/audit/improve cost models, high proficiency with spreadsheets, ChemDraw, MS Office, Google Drive, ability to guide others, experience with data analysis tools (Python, R, etc.) is a plus (but that's also in Preferred). Also ability to do process mapping, unit operation and cycle time. Ability to evaluate synthetic routes. Strong foundational knowledge of Organic chemistry. Exceptional written communication skills. Strong written and verbal communication skills. Excellent analytical, problem-solving, reasoning abilities. Ability to work under pressure. Ability to manage and analyze large datasets. Strong collaboration skills. Demonstrated ability to learn new concepts quickly. But many of these overlap with Qualifications. To avoid duplication, we could put all the bullet points under Qualifications (including required and preferred) and not have a separate Skills section. However the instruction allows us to include Skills section if we have content. But we must not duplicate. We could decide to not include Skills section and just have Qualifications covering all. That would be fewer sections, which is preferred. But we also need Responsibilities section. About the role section from Job Summary. Benefits, Pay, Schedule. Thus we could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That seems reasonable and avoids duplication. Now we need to format. About the role: Use the Job Summary paragraph(s). The Job Summary includes two paragraphs: first about M4ALL mission, second about role. We'll combine into prose

  maybe multiple

  tags. We need to preserve all substantive information. So we include both paragraphs. Responsibilities: we have four categories each with multiple sentences. We'll turn each sentence into

  • under a
    . Could also keep each category as a
    • with sub-bullets? But instruction: Use
      • for any list of duties/requirements/benefits. So we can flatten each duty as a
      • . We'll preserve the content. We need to ensure we don't lose any detail. Let's list each duty sentence: From Techno‑Economic Modeling: - Prepare material balances, chemical raw material cost estimates, and green chemistry metrics for baseline and proposed API manufacturing routes. - Drive continuous improvement of cost‑modeling tools and frameworks to enhance efficiency, transparency, and usability across the Institute. - Evaluate alternative synthetic routes and provide strategic recommendations to project teams and leadership on cost saving opportunities and risk tradeoffs. - Ensure all technoeconomic analyses meet or exceed expectations for technical quality, reliability, and timeliness, and proactively identify risks to deliverables. Data Management & Analysis: - Manage the development, accuracy, and governance of raw material databases, ensuring data integrity, traceability, and alignment with modeling needs. - Establish standards and best practices for data management within the Process Economics function. - Lead complex or high‑impact analyses and guide the team in generating actionable insights for strategic and operational decision‑making. - Partner with internal stakeholders to anticipate data needs and ensure analytical readiness for emerging priorities. Collaboration & Project Support: - Serve as an advisor to project teams, providing strategic input on process changes, development decisions, and cost implications across the lifecycle of each drug target. - Facilitate alignment between technical teams and leadership by translating economic findings into clear, decision‑ready recommendations for both technical and non‑technical audiences. - Represent the Process Economics function in cross‑functional discussions, ensuring economic considerations are integrated early and consistently. - Provide guidance, mentorship, and informal leadership to junior analysts and researchers supporting techno‑economic work. Continuous Improvement: - Lead the development and refinement of internal tools, templates, and methodologies that strengthen the institute’s techno‑economic capabilities. - Identify