Senior Scientist, LPI Modeling & Beam Smoothing
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
Thus:
About the role
... prose ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
We need to preserve all substantive information. Let's extract.
About the role prose: combine overview and role description.
From posting:
"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.
Your Role Focused Energy is looking for a Senior Scientist to bring deep theoretical and simulation expertise in laser-plasma interaction (LPI) modeling, beam smoothing, and laser-target coupling to our Science team. This is a role that spans both the laser system and target physics sides of the house, translating laser system capabilities into target physics requirements, and target physics needs into laser beam requirements, an end-to-end view that is critical to refining our roadmap forward. You will act as a scientific anchor for the beam smoothing project and a trusted theoretical resource across several teams: supporting implementation work, providing simulation and theory support for LPI research, and contributing to the design and interpretation of experiments. Your work will directly shape beam requirements (picket, drive, beam port design) and the physics roadmap that underpins our path to fusion energy at commercial scale."
We need to keep that as prose in . Possibly split into two paragraphs but one is fine.
Responsibilities list: from "What You'll Do":
- Provide theoretical and simulation support on the beam smoothing project.
- Coordinate laser beam requirements, including picket and drive beam design and beam port design.
- Support the roadmap, partnering with the diagnostics team and leading physics efforts.
- Provide theoretical support for implementation in the DUED code.
- Provide theoretical support for LPI science across LPI experiments and simulations.
- Partner closely with the beam smoothing team, the laser and science teams working on beam requirements, the target design team, and the target physics team on LPI risk mitigation and imprint/hydrodynamic instabilities.
Make each as
- .
Requirements (Must-haves):
- PhD in plasma physics or an equivalent field.
- 10+ years of post-doc or staff scientist experience.
- Strong theoretical and simulation knowledge of beam smoothing techniques.
- Strong theoretical knowledge of LPI (CBET, SBS, SRS, and/or TPD) and experience with PIC/fluid simulations.
- Knowledge of High-Performance Computing (HPC).
- Excellent programming skills for HPC (OpenMP/MPI) in C++ and/or Python or an equivalent language.
- Strong mathematical background, including linear algebra, dynamical systems, partial differential equations, stochastic differential equations, and numerical modeling.
- Strong background in laser fusion science.
- Excellent communication skills and a strong collaborator across technical teams.
- High capability in prioritization, problem-solving, and adaptability.
Qualifications (Nice-to-haves):
- Experience designing or interpreting LPI or rad-hydro experiments.
- Knowledge of imprint requirements.
- Knowledge of rad-hydro physics and simulations.
- Knowledge of laser science and optics.
- Experience leading a team.
We should not include boilerplate EEO etc.
Now output HTML fragment only.
Check for any repeated content: ensure we didn't miss any substantive info like location, employment type, department. The posting includes Location Austin, TX Employment Type Full time Location Type Remote Department IFE Science. Should we include that? It's substantive info. Where to put? Could be part of About the role? Or maybe a separate section like "Job details"? But we only have allowed headings list; we could include location etc in About the role prose. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location, employment type, location type, department are minor metadata; we can fold into a short
maybe before About the role? But we must not create extra headings. Could add a
with that info before the first heading. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having a
before headings. It says "fold minor metadata into a short
or drop it." So we can include a short paragraph with location, employment type, location type, department.
Thus output:
Location: Austin, TX • Employment Type: Full time • Location Type: Remote • Department: IFE Science
Then head
for prose. Thus:
About the role
... prose ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
. Possibly split into two paragraphs but one is fine. Responsibilities list: from "What You'll Do": - Provide theoretical and simulation support on the beam smoothing project. - Coordinate laser beam requirements, including picket and drive beam design and beam port design. - Support the roadmap, partnering with the diagnostics team and leading physics efforts. - Provide theoretical support for implementation in the DUED code. - Provide theoretical support for LPI science across LPI experiments and simulations. - Partner closely with the beam smoothing team, the laser and science teams working on beam requirements, the target design team, and the target physics team on LPI risk mitigation and imprint/hydrodynamic instabilities. Make each as
or drop it. Location, employment type, location type, department are minor metadata; we can fold into a short
maybe before About the role? But we must not create extra headings. Could add a
with that info before the first heading. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having a
before headings. It says "fold minor metadata into a short
or drop it." So we can include a short paragraph with location, employment type, location type, department. Thus output:
Location: Austin, TX • Employment Type: Full time • Location Type: Remote • Department: IFE Science
Then head