Operations Research Analyst
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Title: Operations Research Analyst Belong. Connect. Grow. with KBR! (but we don't repeat title as heading). The page already shows title.
We need sections: maybe "About the role" (position summary), "Responsibilities", "Qualifications" (maybe combine required and preferred?), "Skills" (technical expertise?), "Benefits". Pay and Schedule: we have Working Hours: Standard (40 hrs/wk) and Location: Onsite at Wright-Patterson AFB, OH Travel Requirements: Minimal. That's schedule info? Could be schedule: Standard 40 hrs/wk. Pay not mentioned. So we should not create Pay section because no pay info. Schedule: we have Working Hours: Standard (40 hrs/wk). That's schedule info. So we can include a Schedule section with that detail.
Also location maybe not needed but could be part of About the role? Not required.
We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions, "Ready to Make a Difference?" maybe considered call to action; but we should remove application instructions. The line "Ready to Make a Difference? If you’re excited about making a significant impact..." is basically a call to apply; we should remove as application instruction. Also "KBR Benefits" heading we can treat as Benefits section.
We need to preserve all substantive information.
Let's extract:
About the role / Position Summary: The paragraph after "Position Summary": "The Junior to Mid‑Level Operations Research Analyst applies operations research methods and mathematical modeling to support decision‑making and policy development. The analyst collects and analyzes data, develops decision‑support tools, and uses modern analytical techniques to generate insights. The focus of analysis centers on logistics feasibility, specifically as it relates to munitions and fuels posture, as well as resupply options and examination of alternatives. Further, the analyst will help shape overall software, modeling, and analysis architecture solutions to ensure a robust end-to-end analysis capability. They collaborate with team members on studies that improve processes, strengthen system performance, and enhance operational effectiveness."
That's substantive.
Responsibilities: The bullet list under "Key Responsibilities" with subheadings Analysis, Communication, Innovation, Technical Expertise. We need to combine into a list? The instruction: Use - for any list of duties/requirements/benefits. So we should create a
with each duty as - . Could also keep subheadings? Probably not needed; just list duties.
Let's extract each duty:
- Apply foundational knowledge of operations research, mathematics, and analytical techniques to support project objectives.
- Work with project leads to clarify analytical goals and develop task plans aligned with management priorities.
- Collaborate with team members to conduct quantitative and qualitative analyses that inform decision‑making.
- Contribute to studies that evaluate, improve, and validate decision‑analytic models, simulations, and methodologies.
- Document analysis using analytical models, simulations, visualizations, or decision‑support tools.
- Prepare clear, concise briefings, technical papers, and summary reports to communicate findings and recommendations.
- Present analytical results, insights, and techniques to customers, project teams, and peers.
- Identify opportunities to enhance analytical methods and share creative, well‑supported solutions to complex problems.
- Participate in brainstorming sessions and contribute new ideas that strengthen project outcomes.
- Create system designs and architectures that position the team to integrate analytic efforts across functional communities and classes of supply.
- Stay current on emerging analytical tools, modeling techniques, and domain‑relevant technologies.
- Actively pursue professional development to deepen expertise in operations research, related disciplines, and domain knowledge.
- Diagnose complex software issues, develop efficient and scalable code, and implement solutions to maintain model performance and reliability.
That's a lot; we can keep them.
Qualifications: Required qualifications list:
- BA/BS degree in operations research, mathematics, industrial engineering, or a related field
- At least 2 years of experience applying scientific methods and techniques to analyze systems (e.g., professional work, DoW programs, and national security analytics)
- Fundamental knowledge of applying scientific methods and analytical techniques to systems and software
- Experience with at least one analytical or statistical language/tool (e.g., Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, and JMP)
- Basic experience (coursework, internship, or project‑based) developing or utilizing analytical models using Python, R, or C++
- Ability to analyze and interpret problems and recommend effective solutions
- Ability to quickly learn customer missions, systems, and problem domains
- Active Secret clearance
- Ability to obtain a DoD Top Secret clearance
Preferred qualifications:
- MS degree in operations research, mathematics, industrial engineering, or a related field
- 4–6 years of experience applying scientific methods and techniques to analyze systems (e.g., professional work, DoD programs, and national security analytics)
- Familiarity with DoD systems, weapon subsystem design, or military operations
- Proficiency with multiple analytical tools (e.g., Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, and JMP)
- Experience designing and developing analytical models using Python, R, and/or C++
- Demonstrated initiative in learning and applying new analytic techniques
- Active DoD Secret and/or Top Secret clearance
- Experience working in military logistics related fields
- Experience in system design and architecture with a focus on developing solutions to integrate modeling and analysis capabilities
We could combine required and preferred into a Qualifications section, maybe separate Required and Preferred subheadings? But instruction: use
for section headings; we could have Qualifications heading and then within that we could have for required and maybe another for preferred? But we need to avoid creating thin sections; we can combine all qualifications into one list, maybe marking required vs preferred? But we must preserve all substantive info; we could separate with headings inside? Not allowed to create extra headings beyond the allowed set? The instruction only says use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We could have Qualifications and then within that we could have two with a preceding indicating Required and Preferred. That's okay.
Skills: Could be derived from Technical Expertise and maybe from qualifications about tools. But we already have technical expertise in responsibilities. Could create a Skills section listing tools: Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, JMP, C++ maybe. But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Technical Expertise into Skills section. However we already have Responsibilities covering many duties; we could have Skills separate.
But we need to decide which sections to include: About the role (position summary), Responsibilities, Qualifications, Skills, Benefits, Schedule. Pay not present, so omit.
Let's extract Skills: from qualifications and responsibilities: Experience with at least one analytical or statistical language/tool (list). Proficiency with multiple analytical tools. Experience designing and developing analytical models using Python, R, and/or C++. Basic experience developing or utilizing analytical models using Python, R, or C++. Also maybe "Ability to analyze and interpret problems". But that's more ability.
We could create a Skills section listing: Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, JMP, C++ (maybe also analytical modeling). But we need to ensure we don't invent. The posting explicitly mentions those tools in qualifications and preferred. So we can list them.
Benefits: from "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development."
We should include that as Benefits.
Schedule: "Working Hours: Standard (40 hrs/wk)" and "Location: Onsite at Wright-Patterson AFB, OH Travel Requirements: Minimal". Schedule could be Working Hours: Standard (40 hrs/wk). Location maybe not schedule but we could include location in About the role? Might be okay to include location in About the role? But we already have About the role summary; we could add location as a separate sentence? The instruction: preserve ALL substantive information; we should not drop location. Could add a short paragraph under About the role or maybe a separate section? There's no section for Location; we could incorporate into About the role as a sentence: "This position is onsite at Wright-Patterson AFB, OH with minimal travel." That preserves info.
Travel Requirements: Minimal - we can include in same sentence.
Thus About the role will include position summary plus location/travel.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce:
About the role
... (position summary plus location/travel)
Responsibilities
- ...
...
Qualifications
Required:
...
Preferred:
...
But we used which is not prohibited; but we should stick to for prose. Using inside is okay. Or we could just have two
headings: "Required Qualifications:" and "Preferred Qualifications:" as prose then lists.
Better:
Required qualifications:
...
Preferred qualifications:
...
That's fine.
Skills
...
Benefits
...
Schedule
Standard working hours: 40 hours per week.
We should not include Pay.
Now let's craft the content precisely.
About the role paragraph:
"The Junior to Mid‑Level Operations Research Analyst applies operations research methods and mathematical modeling to support decision‑making and policy development. The analyst collects and analyzes data, develops decision‑support tools, and uses modern analytical techniques to generate insights. The focus of analysis centers on logistics feasibility, specifically as it relates to munitions and fuels posture, as well as resupply options and examination of alternatives. Further, the analyst will help shape overall software, modeling, and analysis architecture solutions to ensure a robust end-to-end analysis capability. They collaborate with team members on studies that improve processes, strengthen system performance, and enhance operational effectiveness. This position is onsite at Wright‑Patterson AFB, OH with minimal travel."
Check that we didn't miss any detail: The original also said "Location: Onsite at Wright-Patterson AFB, OHTravel Requirements: MinimalWorking Hours: Standard (40 hrs/wk)". We included location and travel; we will handle working hours in Schedule.
Now Responsibilities list: we need to ensure we captured all bullet points from the four subheadings.
Let's list them exactly as in posting:
Analysis
- Apply foundational knowledge of operations research, mathematics, and analytical techniques to support project objectives.
- Work with project leads to clarify analytical goals and develop task plans aligned with management priorities.
- Collaborate with team members to conduct quantitative and qualitative analyses that inform decision‑making.
- Contribute to studies that evaluate, improve, and validate decision‑analytic models, simulations, and methodologies.
Communication
- Document analysis using analytical models, simulations, visualizations, or decision‑support tools.
- Prepare clear, concise briefings, technical papers, and summary reports to communicate findings and recommendations.
- Present analytical results, insights, and techniques to customers, project teams, and peers.
Innovation
- with each duty as
- . Could also keep subheadings? Probably not needed; just list duties.
Let's extract each duty:
- Apply foundational knowledge of operations research, mathematics, and analytical techniques to support project objectives.
- Work with project leads to clarify analytical goals and develop task plans aligned with management priorities.
- Collaborate with team members to conduct quantitative and qualitative analyses that inform decision‑making.
- Contribute to studies that evaluate, improve, and validate decision‑analytic models, simulations, and methodologies.
- Document analysis using analytical models, simulations, visualizations, or decision‑support tools.
- Prepare clear, concise briefings, technical papers, and summary reports to communicate findings and recommendations.
- Present analytical results, insights, and techniques to customers, project teams, and peers.
- Identify opportunities to enhance analytical methods and share creative, well‑supported solutions to complex problems.
- Participate in brainstorming sessions and contribute new ideas that strengthen project outcomes.
- Create system designs and architectures that position the team to integrate analytic efforts across functional communities and classes of supply.
- Stay current on emerging analytical tools, modeling techniques, and domain‑relevant technologies.
- Actively pursue professional development to deepen expertise in operations research, related disciplines, and domain knowledge.
- Diagnose complex software issues, develop efficient and scalable code, and implement solutions to maintain model performance and reliability.
That's a lot; we can keep them.
Qualifications: Required qualifications list:
- BA/BS degree in operations research, mathematics, industrial engineering, or a related field
- At least 2 years of experience applying scientific methods and techniques to analyze systems (e.g., professional work, DoW programs, and national security analytics)
- Fundamental knowledge of applying scientific methods and analytical techniques to systems and software
- Experience with at least one analytical or statistical language/tool (e.g., Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, and JMP)
- Basic experience (coursework, internship, or project‑based) developing or utilizing analytical models using Python, R, or C++
- Ability to analyze and interpret problems and recommend effective solutions
- Ability to quickly learn customer missions, systems, and problem domains
- Active Secret clearance
- Ability to obtain a DoD Top Secret clearance
Preferred qualifications:
- MS degree in operations research, mathematics, industrial engineering, or a related field
- 4–6 years of experience applying scientific methods and techniques to analyze systems (e.g., professional work, DoD programs, and national security analytics)
- Familiarity with DoD systems, weapon subsystem design, or military operations
- Proficiency with multiple analytical tools (e.g., Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, and JMP)
- Experience designing and developing analytical models using Python, R, and/or C++
- Demonstrated initiative in learning and applying new analytic techniques
- Active DoD Secret and/or Top Secret clearance
- Experience working in military logistics related fields
- Experience in system design and architecture with a focus on developing solutions to integrate modeling and analysis capabilities
We could combine required and preferred into a Qualifications section, maybe separate Required and Preferred subheadings? But instruction: use
for section headings; we could have Qualifications heading and then within that we could have
- for required and maybe another
- ... ...
- for preferred? But we need to avoid creating thin sections; we can combine all qualifications into one list, maybe marking required vs preferred? But we must preserve all substantive info; we could separate with headings inside? Not allowed to create extra headings beyond the allowed set? The instruction only says use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We could have Qualifications and then within that we could have two
- with a preceding
indicating Required and Preferred. That's okay. Skills: Could be derived from Technical Expertise and maybe from qualifications about tools. But we already have technical expertise in responsibilities. Could create a Skills section listing tools: Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, JMP, C++ maybe. But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Technical Expertise into Skills section. However we already have Responsibilities covering many duties; we could have Skills separate. But we need to decide which sections to include: About the role (position summary), Responsibilities, Qualifications, Skills, Benefits, Schedule. Pay not present, so omit. Let's extract Skills: from qualifications and responsibilities: Experience with at least one analytical or statistical language/tool (list). Proficiency with multiple analytical tools. Experience designing and developing analytical models using Python, R, and/or C++. Basic experience developing or utilizing analytical models using Python, R, or C++. Also maybe "Ability to analyze and interpret problems". But that's more ability. We could create a Skills section listing: Python, R, MATLAB, SAS, VBA, Java, SimPy, Simio, Gurobi, JMP, C++ (maybe also analytical modeling). But we need to ensure we don't invent. The posting explicitly mentions those tools in qualifications and preferred. So we can list them. Benefits: from "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." We should include that as Benefits. Schedule: "Working Hours: Standard (40 hrs/wk)" and "Location: Onsite at Wright-Patterson AFB, OH Travel Requirements: Minimal". Schedule could be Working Hours: Standard (40 hrs/wk). Location maybe not schedule but we could include location in About the role? Might be okay to include location in About the role? But we already have About the role summary; we could add location as a separate sentence? The instruction: preserve ALL substantive information; we should not drop location. Could add a short paragraph under About the role or maybe a separate section? There's no section for Location; we could incorporate into About the role as a sentence: "This position is onsite at Wright-Patterson AFB, OH with minimal travel." That preserves info. Travel Requirements: Minimal - we can include in same sentence. Thus About the role will include position summary plus location/travel. Now we need to output HTML fragment only, no /, no markdown. We'll produce:
About the role
... (position summary plus location/travel)
Responsibilities
Qualifications
Required:
- ...
Preferred:
- ...
for prose. Using inside
is okay. Or we could just have two
headings: "Required Qualifications:" and "Preferred Qualifications:" as prose then lists. Better:
Required qualifications:
- ...
Preferred qualifications:
- ...
Skills
- ...
Benefits
...
Schedule
Standard working hours: 40 hours per week.
We should not include Pay. Now let's craft the content precisely. About the role paragraph: "The Junior to Mid‑Level Operations Research Analyst applies operations research methods and mathematical modeling to support decision‑making and policy development. The analyst collects and analyzes data, develops decision‑support tools, and uses modern analytical techniques to generate insights. The focus of analysis centers on logistics feasibility, specifically as it relates to munitions and fuels posture, as well as resupply options and examination of alternatives. Further, the analyst will help shape overall software, modeling, and analysis architecture solutions to ensure a robust end-to-end analysis capability. They collaborate with team members on studies that improve processes, strengthen system performance, and enhance operational effectiveness. This position is onsite at Wright‑Patterson AFB, OH with minimal travel." Check that we didn't miss any detail: The original also said "Location: Onsite at Wright-Patterson AFB, OHTravel Requirements: MinimalWorking Hours: Standard (40 hrs/wk)". We included location and travel; we will handle working hours in Schedule. Now Responsibilities list: we need to ensure we captured all bullet points from the four subheadings. Let's list them exactly as in posting: Analysis - Apply foundational knowledge of operations research, mathematics, and analytical techniques to support project objectives. - Work with project leads to clarify analytical goals and develop task plans aligned with management priorities. - Collaborate with team members to conduct quantitative and qualitative analyses that inform decision‑making. - Contribute to studies that evaluate, improve, and validate decision‑analytic models, simulations, and methodologies. Communication - Document analysis using analytical models, simulations, visualizations, or decision‑support tools. - Prepare clear, concise briefings, technical papers, and summary reports to communicate findings and recommendations. - Present analytical results, insights, and techniques to customers, project teams, and peers. Innovation