Digital Twin Principal Scientist (f/m/d)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. No Pay/Schedule unless present. The posting does not mention specific pay or schedule details. So omit Pay and Schedule sections. We need to extract content: - About the role: The "OverviewApplication About Focused Energy" part? Actually after "OverviewApplication About Focused Energy" there is description of company. That could be "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - Overview/About Focused Energy: description of company, mission, etc. Could be "About the role"? Actually "About the role" is more about the position description. The posting includes "Your Role" and "What You'll Do". So we can treat "About the role" as the overview of the role (maybe combine "Your Role" and "What You'll Do"?). But we have separate sections: Responsibilities (What You'll Do). Requirements (Must-haves). Qualifications (maybe Nice-to-haves? Actually they separate Must-haves and Nice-to-haves). Skills (programming skills etc). Benefits (What We Offer). We'll map accordingly. Let's parse: Company overview: "Focused Energy is building the future of clean energy through laser-driven inertial fusion..." That's more about company; could be placed under "About the role"? Not exactly but we can put under "About the role" as a brief description of the company and role context. Then "Your Role" paragraph: describes purpose. Could be part of About the role. Then "What You'll Do": list of responsibilities (bullet-like sentences). We'll put under Responsibilities. Then "Who You Are": Must-haves and Nice-to-haves. We'll separate: Requirements = Must-haves (mandatory). Qualifications = Nice-to-haves? Or maybe Qualifications = Nice-to-haves. Skills = programming skills etc (maybe part of Must-haves). But we need to avoid duplication. Let's extract: Must-haves: - Master’s degree in Physics (with a specialization in Plasma, Laser, Nuclear, or related field); a Ph.D. is strongly preferred. - Deep expertise in IFE/ICF physics - e.g. target implosion design, laser-plasma interaction, hydrodynamic instability, burn physics, or chamber/neutronics - Track record developing, validating, and publishing physics simulation codes (hydrodynamic, radiation-hydrodynamics, PIC, ray tracing, Monte Carlo neutronics, etc.) - Strong programming skills (Python, Fortran, C++, or equivalent) and experience with HPC/large-scale simulation workflows. - Experience with integrated, systems-level modeling - coupling physics domains, managing code interfaces, uncertainty propagation, sensitivity analysis. Nice-to-haves: - Strong scientific leadership - sets high standards and builds team confidence. - Clear communicator - can translate complex physics for execs, engineers, and external partners. - Systems-level thinker - sees how subsystem trade-offs affect the whole design. - Collaborative across physics, engineering, and software disciplines. - Comfortable making decisions under uncertainty and being transparent about confidence levels. - Familiarity with Digital Twin methods, reduced-order modeling, or physics-informed ML. - Published or patented work in IFE/ICF or related plasma/laser physics. - Experience with requirements flow-down, performance budgeting, or margin analysis. - Entrepreneurial, self-directed, energized by building things from scratch. - Comfortable engaging with execs, program managers, academics, and investors. - Genuinely mission-driven and energized by startup pace and ambiguity. We could treat "Skills" as programming skills etc. But we already have programming skills in Must-haves. Could still have a Skills section listing programming languages and HPC experience. However we must not repeat content. Better to keep Must-haves as Requirements, Nice-to-haves as Qualifications, and maybe Skills as programming skills (but that duplicates). Perhaps we can omit Skills section if content overlaps; but we need to include only when posting has real specific content. The posting does have programming skills etc. Could put under Skills: "Strong programming skills (Python, Fortran, C++, or equivalent) and experience with HPC/large-scale simulation workflows." That's specific. But then we would duplicate that line also in Requirements. To avoid duplication, we could move programming skills to Skills and keep other must-haves in Requirements. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can reorganize to avoid duplication? Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. It doesn't explicitly forbid repeating content, but better to avoid duplication. We could split Must-haves into two: Requirements (education, expertise, track record, systems-level modeling) and Skills (programming, HPC). Nice-to-haves as Qualifications. Let's decide: - About the role: company overview + "Your Role" paragraph. - Responsibilities: "What You'll Do" bullet points. - Requirements: Master’s degree..., Deep expertise..., Track record..., Experience with integrated, systems-level modeling... - Skills: Strong programming skills (Python, Fortran, C++, or equivalent) and experience with HPC/large-scale simulation workflows. - Qualifications: Nice-to-haves list. - Benefits: "What We Offer" list. No Pay or Schedule. Now we need to format as HTML: use

for each section heading. Use

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

  for prose. We need to decide which content is prose vs list. About the role: likely prose (maybe two paragraphs). We'll put in

  . Responsibilities: list of duties (each sentence starting with a verb). We'll make

  • . Requirements: list (each bullet). Use
    • . Skills: maybe a single item list or prose. Could be

      but rule: use

      • for any list of duties/requirements/benefits. Skills is a list? It's just one item but could be list. Safer to use
        • . Qualifications: list. Benefits: list. Now we need to extract exact sentences. Let's copy relevant text. Company overview paragraph: "Focused Energy is building the future of clean energy through laser-driven inertial fusion. Backed by our $240M Series A - the largest fully secured Series A in the global fusion industry - we are scaling rapidly across multiple geographies. Based in Germany and the US, we have brought together the top scientific and engineering minds using proven technologies to unlock fusion power at commercial scale. Focused Energy is working to realize game-changing scientific innovation that promises to deliver a clean, sustainable and abundant source of power globally." That's one paragraph. Then "Your Role" paragraph: "Focused Energy is advancing laser-driven inertial fusion energy (IFE) toward commercial power generation, and the credibility and velocity of that mission depend on our ability to model how the full IFE system behaves, where the physics risks lie, and what each subsystem must achieve for the plant to be economically viable. This role exists to and lead and participate in that capability. We are seeking a Principal Scientist to serve as the most senior technical authority on the Digital Twin team to bring together an integrated IFE system modeling environment which will be at the center of Focused Energy’s IFE plant design efforts. You will lead a team of scientists who develop and own the simulation codes for each major subsystem - laser, target, fusion chamber, target injection and tracking, and target manufacturing - and drive the synthesis of those subsystem models into a comprehensive, self-consistent plant-level simulation framework. That framework enables rigorous trade-off analysis across competing point design candidates and allocates quantitative performance budgets back to each subsystem, forming the physics foundation from which engineering requirements are derived." Note there is a small grammatical error: "exists to and lead". We'll keep as is. We'll combine these two paragraphs into About the role. Now Responsibilities: "What You'll Do" bullet points (each line starts with a verb). Let's extract: - Integrate the physics modeling efforts across all IFE subsystems — laser, target, chamber, target injection/tracking, and manufacturing. - Validate that subsystem code accurately captures the physics, with model uncertainty rigorously quantified and reported. - Set the scientific direction, modeling standards, and validation philosophy for the Digital Twin team. - Lead development of a comprehensive, integrated IFE plant model. - Work directly with the Science team on trade-off analyses across design candidates, identifying which design choices and parameters most affect plant viability. - Work with experimental physics teams to validate simulation codes against real shot data (our own, plus NIF, OMEGA, ELI, etc.). - Partner with the Digital Twin team and external collaborators (national labs, the broader IFE community) to keep our modeling at the frontier. - Present the modeling team's work to executive leadership, program management, and investors. We'll make each as
        • . Now Requirements (Must-haves except programming skills). Let's list: - Master’s degree in Physics (with a specialization in Plasma, Laser, Nuclear, or related field); a Ph.D. is strongly preferred. - Deep expertise in IFE/ICF physics - e.g. target implosion design, laser-plasma interaction, hydrodynamic instability, burn physics, or chamber/neutronics - Track record developing, validating, and publishing physics simulation codes (hydrodynamic, radiation-hydrodynamics, PIC, ray tracing, Monte Carlo neutronics, etc.) - Experience with integrated, systems-level modeling - coupling physics domains, managing code interfaces, uncertainty propagation, sensitivity analysis. Now Skills: - Strong programming skills (Python, Fortran, C++, or equivalent) and experience with HPC/large-scale simulation workflows. Now Qualifications (Nice-to-haves): - Strong scientific leadership - sets high standards and builds team confidence. - Clear communicator - can translate complex physics for execs, engineers, and external partners. - Systems-level thinker - sees how subsystem trade-offs affect the whole design. - Collaborative across physics, engineering, and software disciplines. - Comfortable making decisions under uncertainty and being transparent about confidence levels. - Familiarity with Digital Twin methods, reduced-order modeling, or physics-informed ML. - Published or patented work in IFE/ICF or related plasma/laser physics. - Experience with requirements flow-down, performance budgeting, or margin analysis. - Entrepreneurial, self-directed, energized by building things from scratch. - Comfortable engaging with execs, program managers, academics, and investors. - Genuinely mission-driven and energized by startup pace and ambiguity. Now Benefits (What We Offer). Let's extract each bullet: - Innovative Technology & Mission: Be part of a cutting-edge company working on groundbreaking research in clean energy and scientific discovery. - Career Development: We invest in our people. This is an opportunity to join an early, growing company at the forefront of new technology, where you’ll have the opportunity to develop and grow your career. - Collaborative Culture: Work with great people in a dynamic, international environment with top-tier scientists, engineers and professionals passionate about solving global challenges. - Ownership: Take ownership from day 1 and drive impact by making decisions, solving challenges and shaping the future of our company. - Your Success is our Success: We offer a competitive salary and company ownership in the form of stock options, giving you a direct stake in our success and ownership in what we build together. - Medical, Dental, Vision: Multiple great plans to pick from that are active come the 1st Day of employment for you and any enrolled dependents. - Vacation Days: We support your work-life-balance by granting you Unlimited PTO. - Snacks and Drinks: Our office fridges are never empty. Enjoy our healthy snacks and drinks. - Retirement Plan: If you decide to enroll in our 401