Senior Operations Research Analyst

We need to output HTML fragment with sections: About the role, Responsibilities (What You Will Do), Requirements (Required Qualifications), maybe Qualifications (Desired Qualifications), Skills maybe not separate, Benefits (Compensation And Benefits), Pay? The posting says compensation is competitive, commensurate with education, clearance, and directly relevant experience. That's vague; we should not create Pay section if it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they list health, dental, vision insurance, 401(k) with match, PTO, paid federal holidays, support for professional affiliations. That's specific enough for Benefits section. Pay: they say compensation is competitive ... commensurate with education, clearance, and directly relevant experience. That's vague, not a specific number or range. According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since compensation description is vague, we should not create a Pay section. Benefits we have specifics, so include Benefits. Schedule: they say full-time on-site, no remote option. Could we create Schedule section? They said only create Schedule if posting actually states them. It does state full-time on-site, no remote option. That's schedule info. However they said prefer a few substantive sections over many thin ones. Could combine schedule into Benefits? Probably better to have a Schedule section with that info. It's specific: full-time on-site, no remote. Not filler. So include Schedule. We need headings:

for each section: About the role, Responsibilities, Requirements, Qualifications (maybe Desired Qualifications), Benefits, Schedule. Possibly also Skills? Not needed. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information. Must not invent or summarize away detail. Must include details from About The Role paragraph, What You Will Do list, Required Qualifications, Desired Qualifications, Work Environment maybe? Work Environment includes classification, location, etc. Should we include that as part of About the role or separate? Could be part of About the role or maybe a separate section like Work Environment. But instruction: prefer few substantive sections over many thin ones. Could incorporate work environment details into About the role or Benefits? Probably include in About the role as it's part of role description. However we already have About the role section with the paragraph. Could add more details there. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities (What You Will Do) we need a list. For Required Qualifications we need a list? It's a paragraph with bullet-like sentences. Could format as list. For Desired Qualifications also list. For Benefits list. We need to preserve all substantive information: include location, clearance, travel none, etc. Let's extract: About The Role paragraph: "Heartland Consulting is hiring a Senior Operations Research Analyst to sit on-site with Commander, Submarine Group Two (COMSUBGRU TWO) in its role as Theater Undersea Warfare Commander (TUSWC) for U.S. Second Fleet. The analyst is the command's embedded OA/OR capability - the person who finds where analysis can improve TUSWC planning, builds the methods, trains the staff to use them, and leaves behind documented processes the watch floor can run without the contractor in the room. This is not a remote study contract and not a generic "data analyst" seat. You will work in a classified Navy staff environment, handle operational data, brief seniors (including flag-level audiences), and institutionalize operations-analysis methods for maritime homeland defense and theater undersea warfare. Heartland is the incumbent on this effort. The current analyst is in the seat today. We are recruiting the successor now so the command has a clean, qualified handoff and no gap in on-site support." We can keep that as

  . What You Will Do list: bullet points: - Provide on-site operations analysis / operations research support to the TUSWC staff at COMSUBGRU TWO. - Identify opportunities to insert OA/OR into the TUSWC planning process and improve operational effectiveness. - Collect, clean, manage, and employ operational datasets for trend analysis and predictive analytics. - Formulate and solve optimization problems (linear, nonlinear, network, and integer programming) that inform planning choices. - Build and use stochastic models (Markov chains, Poisson processes, queueing, renewal processes) and simulation with design-of-experiments techniques. - Apply systems analysis, including risk-benefit and cost-benefit analysis, to deployment, requirements, and course-of-action questions. - Employ OA/OR tools in live TUSWC planning and operations - not only after-action studies. - Develop and document methods, processes, and procedures the TUSWC staff can implement. - Train TUSWC staff on those methods and leave behind usable SOPs, briefs, and implementation products. - Liaise with other TUSWC staffs, OA/OR subject-matter experts, and tool developers. - Deliver the contract products: OA/OR Support Plan Brief (30 days after award), monthly progress and financial status reports, interim progress reviews, a final annotated brief, and a Final OA/OR Implementation Plan. - Brief results independently, in writing and orally, including annotated PowerPoint for senior leadership with read-aheads. We'll make

  • for each. Required Qualifications: list: - Education: Bachelor's degree in Operations Research or Operations Analysis. (The contract is specific - related degrees such as mathematics, statistics, or engineering do not substitute for this requirement.) - Preferred: Master of Science in Operations Research or Operations Analysis (NPS Curriculum 360 / 355 or civilian equivalent). - Experience: Ten (10) years applying operations research / operations analysis to Navy warfighting analysis. - Demonstrated skill in mathematics and computation, including programming for complex analysis, algorithm development, and simulation. - Demonstrated skill in data preparation (collect, clean, manipulate) and statistical / probability analysis of decision problems. - Demonstrated skill in optimization, stochastic modeling, simulation with design of experiments, and systems analysis. - Proven ability to conduct independent analysis and present results orally and in writing to operational customers. - Clearance: Active Top Secret / SCI. U.S. citizenship required. Ability to obtain NATO briefings after hire. Must be eligible for a DISS Visit Access Request to COMSUBGRU TWO. - Ability to work full-time on-site at NSA Hampton Roads / Naval Station Norfolk (Building NH-13 / TUSWC spaces). No remote option for this seat. We'll format as list items. Desired Qualifications list: - Navy 3211P / 3211Q operations-analysis subspecialty, or equivalent civilian utilization tour at a Fleet, TYCOM, numbered-fleet, OPNAV N81, UWDC Tactical Analysis Group, CNA field, NUWC, or TUSWC staff. - Direct undersea warfare, theater ASW, maritime homeland defense, or submarine-force staff experience. - Prior on-site embed at a Navy operational staff (not only laboratory or headquarters studies). - Experience training operators or staff officers on analytic methods and leaving durable process documentation. - Familiarity with SIPRNet collaboration, OPSEC, and handling of classified / CUI / PPBE data. - Tools such as Python, R, MATLAB, Julia, or equivalent; optimization solvers; discrete-event or combat simulation; and standard Navy briefing products. - Experience briefing O-6 / flag / SES audiences. Work Environment maybe we can incorporate into About the role or separate. Since we have schedule and benefits separate, we could add a Work Environment section with classification, location, etc. But instruction: prefer few substantive sections over many thin ones. Could merge work environment details into About the role or Benefits? Probably better to add a short paragraph after About the role? But we must not create headings with filler. If we add a Work Environment heading, we need substantive content. We have location, classification, travel none, etc. That's substantive. Could be its own section. However we already have Schedule (full-time on-site, no remote) and Benefits. Work Environment could include classification, location, etc. That's okay. But we might avoid too many sections. Let's think: About the role already includes location? It mentions sit on-site with COMSUBGRU TWO in Norfolk, VA. It mentions classified Navy staff environment. Could add more details there. However the About the role paragraph we have does not include classification details, location specifics (Building NH-13). We could expand About the role to include those details from Work Environment section. That would keep sections fewer. Thus we can edit About the role paragraph to include: location (NSA Hampton Roads / Naval Station Norfolk, Building NH-13 / TUSWC spaces), classification (work up to TOP SECRET / SCI; incidental TS/SCI research into models; meetings at TS/SCI; NATO information access), travel none, government provides NIPR and SIPR access, contractor provides personal analytic tools unless otherwise furnished, analysis etc become government property. Also mention that compensation is competitive etc (but we decided not to include Pay). We could include compensation description in Benefits? It's not specific benefits; maybe we could add a note about compensation being competitive but not specific; but instruction says avoid filler. So maybe omit compensation entirely? But we need to preserve ALL substantive information. Compensation is substantive albeit vague. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation is competitive ... commensurate with education, clearance, and directly relevant experience. That's a statement about compensation, albeit vague. Should we include it? The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "commensurate with experience" is considered filler. So we should not create a Pay section with that phrase. However we could include that sentence somewhere else, maybe in a paragraph under About the role or Benefits? But that would still be filler text. The instruction says never emit a heading followed by filler/placeholder text. It doesn't forbid including that sentence in a paragraph, as long as it's not a heading with filler. So we could include a sentence about compensation in a paragraph under About the role or maybe a separate paragraph without a heading. However we must preserve all substantive information; we could add a sentence: "Compensation is competitive for a TS/SCI, on-site Navy warfighting OR seat in Hampton Roads and is commensurate with education, clearance, and directly relevant experience." That's not a heading, it's just a sentence. That seems okay. Similarly, we have "Target start is aligned to contract award / 29 September 2026, with an earlier overlap preferred so the outgoing analyst can conduct a structured turnover." That's substantive about start date. Could include in a paragraph maybe under About the role or a separate section like "Start Date". But we could add to About the role. We need to avoid creating sections with filler. So we will have sections: About the role, Responsibilities, Requirements, Qualifications (Desired), Benefits, Schedule. Possibly also include a short paragraph about compensation and start date inside About the role or maybe a separate "Additional Details" but that might be thin. Better to incorporate into About the role. Thus About the role paragraph will be expanded to include: location details, classification, travel none, government provides NIPR/SIPR, contractor provides personal tools, IP becomes government property, compensation statement, target start date. We must ensure not to repeat job title as heading. Now produce HTML. Structure:

    About the role

    ... (expanded)

    Responsibilities

    • ... each

    Required Qualifications