Sr. Engineering Scientist

. We need to decide what goes into each section. Let's extract content: About the role (overview): The paragraphs about SPA, JOID, mission, need for Sr. Engineering Scientist, location DARPA Arlington VA. We'll combine into a

maybe multiple paragraphs. Responsibilities: bullet list of duties: - Apply a strong technical background and a proactive attitude in support of DARPA and will be motivated to learn or already understand DARPA processes, procedures, and culture. - Utilize technical skills to understand the complex problems associated with DARPA programs, while simultaneously providing the necessary management support to execute the day-to-day requirements. - Support periodic (monthly or bi-weekly) performer assessments to analyze programmatic, technical, and schedule risks and communicate findings to the Program Manager. - Assess performer task progress and projected performer outcomes with a program team. - Monitor both the technical and programmatic progress of various performers and keep the Program Manager abreast of progress through daily communications, monthly reports, and other reports as needed. - Assist in preparation and execution of various reviews of programs, gathering technical information and data on progress and accomplishments from the various performers. - This is a full-time on-site position in Arlington, VA. Up to 15% travel may be required. Note: The last bullet about full-time onsite and travel could be schedule, but it's also a responsibility. We'll keep it in responsibilities or schedule? Since schedule section exists, we could move that to schedule. But the instruction says to include schedule section only if posting actually states them. It does state full-time on-site and up to 15% travel. So we can put that in Schedule section. However the responsibilities bullet includes that sentence; we could keep it there but then schedule would be duplicate. Better to separate: responsibilities list excludes the schedule sentence; schedule section includes full-time onsite and travel. Thus responsibilities bullets (excluding the schedule sentence). We'll keep the rest. Requirements: Required qualifications list: - Master's degree in science, technology, engineering or math (STEM); may substitute a non-technical degree with demonstrated technical acumen. - 10+ years of technical experience supporting research and development (R&D) programs. - Demonstrated skill in conceiving, planning, and conducting research in complex problem areas requiring novel approaches. - Proven ability to make independent decisions on R&D engineering problems and to plan and coordinate work. - Active DoW TS/SCI clearance. - Self-starter with excellent oral and written communication skills, with mature judgment and attention to detail. - Proficiency with software suites such as Microsoft 365, Word, PowerPoint, and Excel. - Ability to work fully onsite at DARPA's HQ in Arlington, VA. Note: Ability to work fully onsite duplicates schedule; but it's a requirement. We'll keep it in Requirements. Qualifications (Desired): - At least 3 years of experience working in or with DARPA or a similar organization. - Prior experience as senior PM support at DARPA. - Published articles in the field of expertise. Skills: Could be overlapping with required proficiency etc. But we already have proficiency in software suites under Requirements. Could also include communication skills etc. Since we have a Skills section allowed, we could extract skills: strong technical background, proactive attitude, understanding DARPA processes, technical skills, management support, analytical skills, communication, judgment, attention to detail, software proficiency. But to avoid duplication, maybe we skip Skills section because its content is already covered. However instruction says prefer a few substantive sections over many thin ones. We could omit Skills if its content is redundant. But we need to decide if we have substantive content for Skills beyond what's already in Requirements. The posting does not have a separate "Skills" heading; it's embedded. We could still create a Skills section with the software proficiency and communication skills etc. But that would duplicate content from Requirements. The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid redundancy. However we could keep Skills separate with items like "Strong technical background, proactive attitude, understanding of DARPA processes, technical and programmatic analysis, communication, judgment, attention to detail, proficiency with Microsoft 365 suite." That is still substantive but duplicates some. Might be okay but risk of being considered thin? It's not thin. Given we already have Requirements covering many of those, maybe we skip Skills. Benefits: paragraph about benefit programs. Pay: salary range. Schedule: full-time on-site, up to 15% travel. Now we need to output HTML fragment only, no /, no markdown. We'll produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

...

Pay

Salary range: USD $150,000.00/Yr. - USD $200,000.00/Yr.

Schedule

Full-time on‑site position in Arlington, VA; up to 15% travel may be required.

for prose; we can break into multiple

if needed but not required. Now Responsibilities bullets (excluding schedule sentence). Let's list: - Apply a strong technical background and a proactive attitude in support of the Defense Advanced Research Projects Agency (DARPA) and will be motivated to learn or already understand DARPA processes, procedures, and culture. - Utilize technical skills to understand the complex problems associated with DARPA programs, while simultaneously providing the necessary management support to execute the day-to-day requirements. - Support periodic (monthly or bi-weekly) performer assessments to analyze programmatic, technical, and schedule risks and communicate findings to the Program Manager. - Assess performer task progress and projected performer outcomes with a program team. - Monitor both the technical and programmatic progress of various performers and keep the Program Manager abreast of progress through daily communications, monthly reports, and other reports as needed. - Assist in preparation and execution of various reviews of programs, gathering technical information and data on progress and accomplishments from the various performers. Check if any other responsibilities: The sentence "This is a full-time on-site position in Arlington, VA. Up to 15% travel may be required." we moved to Schedule. Now Requirements bullets: - Master's degree in science, technology, engineering or math