Staff Data Scientist, Optimization

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Requirements (Required Qualifications), maybe Qualifications (Preferred Qualifications), Benefits, Pay, Schedule? The posting includes Pay (US Salary Range) and Work Environment (location). Schedule not mentioned. Benefits & Perks present. Also "Work Environment" maybe not a standard heading; we can include as a paragraph under maybe "Location". But we only include sections when there is real specific content. We have About The Role (present). What You’ll Do (Responsibilities). Required Qualifications. Preferred Qualifications. Benefits & Perks. Compensation (Pay). Work Environment (location). Also maybe "Who We Are" but that's not a standard heading; we could treat as About the company but not required. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. We have: - About the role: we have "About The Role" paragraph. Use that as heading. - Responsibilities: "What You’ll Do" content. - Requirements: "Required Qualifications". Could also include "Required Qualifications" as Requirements. - Qualifications: "Preferred Qualifications" as Qualifications. - Benefits: "Benefits & Perks". - Pay: "Compensation US Salary Range". - Schedule: not present, so omit. - Skills: not separate; could be included in qualifications but we don't have a separate Skills section; we can omit. We also have Work Environment (location). Not a standard heading but could be placed as a paragraph under maybe About the role or separate? The instruction says only use those headings; we can include other info as paragraphs within sections. So we can include location info in a

under About the role or maybe a separate paragraph after About the role before Responsibilities. Probably best to add a

after About the role heading containing location and work environment details. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, equal opportunity, export control compliance, etc. Also remove navigation, cookie, legal, scam-warning, duplicated lines. Also remove "Who We Are" maybe? It's substantive but not a standard heading; we could incorporate as a paragraph under About the role? Actually "Who We Are" is about the company; could be placed as a paragraph before About the role heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should prefer those. Could we include a

for "Who We Are"? Not in list; better to avoid. We can incorporate that info into a

under About the role or maybe as a preceding paragraph without heading. Since we need to preserve all substantive information, we need to keep that "Who We Are" content. We can put it as a

before the first heading or as part of About the role section. Probably best to put it as a

before the About the role heading, as it's introductory. We must not include any markdown fences. Just raw HTML. Let's extract content. Who We Are paragraph: "At Firestorm, we are building the future of expeditionary defense manufacturing and autonomous systems. Modern conflict has exposed a fundamental problem: the systems needed most by operators are often too expensive, too slow to produce, and too difficult to sustain at scale. Firestorm exists to change that. We develop mission-adaptable aerial systems and deployable manufacturing infrastructure designed to put capability directly into the hands of the warfighter. From modular unmanned aircraft to xCell — our deployable microfactory — our goal is to make defense systems rapidly deployable, adaptable, and producible at the point of need. We are looking for builders, operators, and problem-solvers who want to work on meaningful technology with real-world impact." About The Role paragraph: "Firestorm builds uncrewed aircraft and the manufacturing network that produces them: full-capability plants, deployable xCell edge factories, and forward-deployed sites that stand up production near the point of need. Crucible is the software that runs that network. It plans and executes production across factories that don't look alike, using supply that isn't guaranteed to arrive. It has to answer practical questions: what should we build, where should we build it, what constrains the plan, and what changes when material, capacity, or demand moves. Many of those are optimization problems. The answer has to account for production capacity, inventory, sourcing, lead times, transportation, and incomplete information. It also has to solve quickly enough to be useful and explain why it produced the plan it did. We are hiring a Staff Data Scientist to own the optimization and decision science behind Crucible. As the first dedicated data scientist on the team, you'll set the technical direction for how Crucible models and solves planning problems, while staying hands-on building the models that ship in the product. You'll work directly with the Crucible software team and with manufacturing, supply chain, and product as we grow both the platform and the science behind it." What You’ll Do (Responsibilities) bullet list: - Own Crucible's optimization models — Formulate and solve problems across production planning, allocation, sourcing, inventory, scheduling, and manufacturing network optimization. - Choose the right approach — Use mathematical optimization, heuristics, simulation, statistics, or simpler methods based on the problem and the decisions the user needs to make. - Build models that work in production — Prototype against real data, establish baselines, test solution quality and performance, and work with software engineers to ship models inside Crucible. - Model real-world uncertainty — Account for incomplete data, changing demand, variable lead times, supplier performance, and other conditions that make a mathematically perfect plan operationally wrong. - Work directly with users — Spend time with manufacturing, supply chain, and program teams to understand how decisions are actually made and translate those constraints into the product. - Set the direction for decision science — Establish how Crucible formulates problems, evaluates model quality, explains recommendations, and determines when additional model complexity is actually worthwhile. - Build the foundation for the team — Establish the tools, methods, and technical standards that future data scientists will build on and raise the modeling fluency of the broader Crucible team. Required Qualifications (list): - 8+ years (or 6+ w/ PhD) building optimization, operations research, or data science solutions for complex operational problems - U.S. person required due to ITAR regulations - Demonstrated technical leadership on ambiguous problems, including setting modeling direction and influencing product or engineering decisions - Strong background in mathematical optimization, including linear or mixed-integer programming, network optimization, scheduling, or related methods - Hands-on experience with optimization tools such as Gurobi, CPLEX, OR-Tools, Pyomo, or equivalent - Strong Python and SQL, with experience writing code that is tested, maintained, and used in production - Strong statistical fundamentals and experience working with incomplete, noisy, or uncertain data - Demonstrated ability to take an ambiguous operational problem from formulation through validation and deployment - Strong written and verbal communication across technical and operational teams - Willingness to spend real time with the people using the models you build - U.S. person status (ITAR) (duplicate? Actually appears twice; we can keep one.) Preferred Qualifications (list): - MS or PhD in Operations Research, Industrial Engineering, Applied Mathematics, Statistics, Computer Science, or a related quantitative field - Experience with production planning, supply chain, logistics, inventory optimization, or manufacturing systems - Experience with simulation, stochastic optimization, robust optimization, or decomposition methods - Aerospace, defense, UAS, automotive, or other complex manufacturing experience Work Environment: "This role is based in San Diego, CA. We welcome candidates who are local or open to relocating; relocation assistance is available and may be included in the offer package where appropriate." Compensation: "US Salary Range: $175,000 – $220,000 USD The posted salary range reflects an estimate based on a variety of compensation factors, including but not limited to relevant experience, education, certifications, specialized skills, geographic location, and business needs. Actual compensation may vary, and this range is subject to change as our compensation structure or market conditions evolve." Benefits & Perks paragraph (multiple sentences). We'll keep as a

• list? The benefits are listed as sentences; we can convert each benefit into a list item. The instruction: Use
  • for any list of duties/requirements/benefits. So we should make a list for benefits. Benefits list items: - comprehensive medical, dental, and visions plans - 401(k) Retirement Savings Plan to invest in your long-term retirement goals - Equity grants for new hires - Unlimited PTO - Extremely generous company holiday calendar, including a holiday hiatus in July & December. - Generous Parental Leave - Lifestyle Spending Account - FSA DCFSA HSA - Hospital Indemnity insurance - Critical Illness insurance - Accident insurance - Basic Life/AD&D, short-term and long-term disability insurance, 100% covered by Firestorm. Plus, the option to purchase additional life insurance for you and your family. - Mental Health Resources: We provide free mental health resources 24/7 including therapy and more. - Additional work-life services, such as free legal and financial support, are available to you as well. We could also include the introductory sentence: "Our culture fosters collaboration, respect, and trust, empowering passionate people to do their best work. We offer a competitive salary, comprehensive benefits, and opportunities for career growth. In addition to an opportunity to take part in an innovative, collaborative and fast-growing business with a highly motivated and skilled team, we also take pride in taking care of our employees. Here are just a few ways that we show our appreciation:" This is prose; we can put as a

    before the list. Now we need to output only HTML fragment, no /. Use

    for each section heading. Order: maybe About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Work Environment (location) maybe as a paragraph under About the role or separate heading? Since Work Environment not in list, we could just include as a

    after About the role heading before Responsibilities. We must not include sections with filler like "commensurate with experience". Not present. Let's craft. We'll start with a

    for Who We Are. Then

    About the role

    then

    About The Role content.

    Then maybe

    Work Environment: This role is based in San Diego, CA....

    (or we could incorporate into About the role). I'll add a separate

    for location. Then

    Responsibilities

    then
    • ... each responsibility. Then

      Requirements

      then
      • ... required qualifications. Then

        Qualifications

        then
        • ... preferred qualifications. Then

          Benefits

          then

          Intro sentence about culture.

          then
          • ... benefits. Then

            Pay

            then

            US Salary Range: ...

            We should not include Schedule. Make sure to preserve all substantive information; we have included everything except boilerplate. Check for duplicated lines: we have U.S. person required due to ITAR regulations and later U.S. person status (ITAR) duplicate; we can keep one. Now produce HTML. Be careful to escape any special characters like &, <, >. In text we have "&" in "FSA DCFSA HSA". That's fine as is. Also we have "xCell — our deployable microfactory —". The em dash may be okay; we can keep as is. Might need to encode? Usually HTML can handle raw em