Jobs · Administrative · Virginia

COMM Referent - NRO Office of the Director

National Reconnaissance Office (NRO) · Chantilly, VA · 1 mo ago
On-siteAdministrative$105k–$137k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Salary info (STEM pay range). So we can include Pay section with that salary range. Benefits? The posting mentions hiring incentives may be offered, trial period, veterans' preference, etc. Those could be considered benefits? The instruction: include Benefits section only if posting actually states them. There's mention: "The NRO may offer hiring incentives and other entitlements at management’s discretion." Also trial period, veterans' preference, etc. Could be considered benefits. However we need to be careful: not to create thin sections. Might combine into Benefits. Also Schedule? Not mentioned explicitly; only "full-time position". No schedule details. So we should not create Schedule section. Benefits we can include if there is substantive content: hiring incentives, trial period, veterans' preference, financial disclosure, etc. But many of those are more like "Other Information". Could treat as Benefits? Might be better to have a "Benefits" section with hiring incentives, trial period, veterans' preference, financial disclosure, etc. However the instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role (summary), Responsibilities (What You Will Be Doing), Requirements (Basic Eligibility + Who May Apply?), Qualifications (What You Need), Skills (maybe combine with Qualifications?), Pay (salary), Benefits (hiring incentives, trial period, veterans' preference, etc). But we need to avoid duplication. Let's parse content: - Intro about NRO (mission) - could be About the role? Actually "About the role" could be description of the position context. We'll include a short paragraph summarizing the role: The Communications Directorate (COMM) within NRO seeking COMM Referent - NRO Office of the Director, providing executive level Tier I and II enterprise technical support to NRO Director and COMM Director suites, reporting to Chief and Deputy Chief of Operations Division within Digital-Workspace Solutions Group (COMM/DSG/OPS). Provide context. - Responsibilities: list of duties from "What You Will Be Doing". That's a long list; we can turn into
  • items. - Requirements: Basic Eligibility (US Citizen, TS/SCI clearance, drug testing, polygraph) plus Who May Apply (public, federal employees grade level, etc). Also location Chantilly, VA, telework not available. Also maybe "Geographic Mobility Agreement", "Information Assurance certification", "Emergency Essential". Those could be requirements. - Qualifications: "What You Need" includes Highly Desired Qualifications (Bachelor's degree, experience with interrelationships, understanding IT architecture, knowledge of new IT developments) and Desired Qualifications (Program Management or technical management expertise, experience with NRO missions, knowledge of DoW/IC). Also "Qualifying experience may have been acquired..." etc. Also resume length limit. Could be Qualifications. - Skills: maybe we can extract specific skills from responsibilities: providing technical advice, interpreting policies, applying new developments, etc. But we might avoid thin Skills section; maybe combine into Qualifications. - Pay: Salary range for GG-12: $117,753 – $153,082 (also mention GG-11 range but position is GG-12). Also mention DCIPS TLMS STEM pay. So we can include Pay. - Benefits: hiring incentives, trial period (2-year), veterans' preference, financial disclosure (OGE Form 450), DAWIA certification requirement, Information Assurance certification within six months, Geographic Mobility Agreement, Emergency Essential, etc. Also maybe "Telework not available" is not a benefit. We'll include those as benefits. - Schedule: not specified beyond full-time; we should not create Schedule section. We must not include boilerplate like EEO, Privacy Act Notice, etc. Remove those. We must not repeat job title as heading. So no heading for "COMM Referent - NRO Office of the Director". We'll just have sections. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    • ...

    Requirements

    • U.S. Citizenship
    • Ability to obtain and maintain a TS/SCI security clearance
    • Subject to pre‑employment and periodic drug testing
    • Subject to pre‑employment and periodic polygraph examinations
    • Located in Chantilly, VA; telework not available
    • Must be willing to meet geographic mobility, information assurance (IA) certification within six months, and emergency‑essential duties if applicable
    Maybe also include federal employee grade requirement: For federal applicants, must be at GG‑11‑12 grade level and apply laterally; external applicants open to public. Could be under Requirements.

    Qualifications

    • Bachelor’s degree in a related field (software engineering, information technology, cybersecurity, systems/network engineering, etc.)
    • Experience with the interrelationships of multiple IT specialties
    • Understanding of an organization's IT architecture
    • Knowledge of new IT developments and applications
    • Program management or technical management expertise (cost, performance, schedule, technical reporting) highly desirable
    • Experience with NRO missions, programs, and management processes
    • Knowledge of DoD and Intelligence Community (IC) organizations, missions, relevant policies, and processes
    • Qualifying experience must be reflected in the resume; resume limited to two pages per OPM Merit Hiring Plan
    Maybe also include "Desired Qualifications" but we already captured.

    Pay

    This position is a GG‑12 role under the Defense Civilian Intelligence Personnel System (DCIPS) with Targeted Local Market Supplement (TLMS) STEM pay. Salary range: $117,753 – $153,082 per year.

    Benefits

    • Potential hiring incentives and other entitlements at management’s discretion
    • Two‑year trial period for new DCIPS employees
    • Veterans’ preference applicable to eligible candidates
    • Financial disclosure requirement (OGE Form 450) upon appointment and annually thereafter
    • DAWIA certification requirement within 24 months of appointment (maintain 80 continuous learning points every 24 months)
    • Information Assurance (IA) certification required within six months of assignment
    • Geographic mobility agreement – possible directed reassignment for mission effectiveness or career development
    • Positions may be designated emergency‑essential, requiring willingness to meet all position requirements
    We should ensure we didn't include any filler like "commensurate with experience". Not present. Check for any duplicated lines removed. Check for any mention of "Telework is not available" - we included location statement. Check for "Overtime Statement: MAY be required to work other than normal duty hours, which may include evenings, weekends, and/or holidays." That's a schedule/overtime detail; maybe we could include under Benefits? Actually it's about overtime, could be considered part of Schedule? But we decided not to create Schedule section. Could we add a line under Benefits about potential overtime? Might be considered a condition of work, not benefit. But we could incorporate into Responsibilities? Not exactly. The instruction: "Prefer a few substantive sections over many thin ones." Overtime statement is substantive; we could add a

    under Benefits or maybe a separate section "Work Conditions"? But not in allowed headings. The allowed headings list includes Benefits, Pay, Schedule. Overtime could go under Schedule? But schedule is about work hours; we could create a Schedule section if we have actual schedule info. The posting includes overtime statement, which is schedule-related. So we could create a Schedule section with that statement. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state overtime statement, so we can create Schedule section with that. Good. Thus we add Schedule section:

    Schedule

    May be required to work outside normal duty hours, including evenings, weekends, and/or holidays.

    Now we have sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule. We omitted Skills as thin. Check that we didn't include any boilerplate like EEO, Privacy Act, etc. We removed those. Now ensure we preserved all substantive information: Let's verify we captured: - NRO mission intro (maybe not needed but we included in About the role). Did we capture the mission description? We included a brief about COMM Directorate role. Might be missing some details like "Using a diversified architecture of spacecraft..." but that's about NRO generally, not specific to role. Could be omitted as not substantive to role? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The NRO mission description is substantive but maybe not directly about the role. However it's part of the posting; we might need to include it somewhere. Could include in About the role as context. Let's add a sentence: "For sixty years, the NRO has developed, acquired, launched and operated the satellites that provide America’s advantage in space, using a diversified architecture of spacecraft to collect and deliver space‑based intelligence, surveillance, and reconnaissance." That is from intro. We'll incorporate. - Basic Eligibility: we captured. - Where You Will Work: we captured location and directorate. - The description of COMM/DSG: we could include in About the role. - The NRO Cadre collecting resumes etc: we could note that this is a GG-12 position, open dates, resume deadline. We included open dates? Not yet. We should include the opening/closing dates and deadline. That's substantive. Where to put? Could be under About the role or Requirements? Probably under About the role as metadata. Let's add a paragraph: "This is a full‑time position open from 2026‑09‑16 to 2026‑09‑30; resumes must be submitted by 11:59 PM EST on 2026‑09‑30." - Who May Apply: we captured federal employee grade requirement and public open. - The statement about Federal employees must be at grade level or higher, not a promotion, lateral transition, etc. We captured. - The statement about NRO Cadre employees should apply internally, external applicants only, etc. We captured? We said "Federal government employees MUST currently be at the GG 11-12 grade level and may ONLY apply for a lateral reassignment at their current grade level and step." Also "The NRO is only accepting external applicants for this job announcement. Current NRO Cadre employees should apply internally." We need to include that. Let's add to Requirements or About the role. We'll add to Requirements bullet: "Open to the public; federal applicants must be at GG‑11‑12 grade and apply laterally; current NRO Cadre employees must apply internally." - The statement about reemployed federal annuitant not qualifying: we could include but it's minor. Might be okay to omit? The instruction: preserve ALL substantive information. That is substantive. We'll add a bullet: "Position does not

Similar jobs

Director PMO - NPI/NPD

Ichor Systems, Inc.Austin, TX· 1 mo ago
Information Technologyapply on fa-eovh-saasfaprod1.fa.ocs.oraclecloud.com