Technical Integrator- Entry Level
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting and decide which sections to include.
Let's extract key info:
- About the role: description of NRO, mission, position description: "Technical Integrator to serve as primary link between government prototyping team, Cosmic Horizon, and operational end users. Deploy to customer locations to embed with mission users, understand operational workflows, and deliver workflow-automation and AI integration solutions. This is an entry level position at the GG-07 to GG-11 level. The selected candidate will perform hands-on technical work while building operational, technical, and stakeholder-integration experience required for increased responsibility." Also location: Chantilly, VA, telework not available.
- Responsibilities: list under "What You Will Be Doing": bullet points.
- Requirements: "Basic Eligibility For A Position With The NRO": US Citizen, TS/SCI clearance, drug testing, polygraph. Also "Required Qualifications": list.
- Qualifications: maybe "Desired Qualifications".
- Skills: maybe "Key Competencies Candidates Should Demonstrate".
- Benefits: Not explicitly listed; there is mention of hiring incentives, trial period, veterans preference, etc. But not explicit benefits like health, retirement. Might not include Benefits section unless specific.
- Pay: Salary info: GG-07: $81,901 - $106,474; GG-09: $94,909 - $123,388; GG-11: $105,262 - $136,848. Also mention STEM pay etc. So we can include Pay section.
- Schedule: Not explicit schedule; maybe full-time, travel requirement. Travel requirement is separate; schedule maybe not given. Could include Travel under Responsibilities? Travel requirement is separate paragraph. Could include a "Travel" section? Not in allowed headings. Could embed under Responsibilities or maybe under "Schedule"? Not exactly schedule. The instruction says use headings for Benefits, Pay, Schedule. If schedule not specified, we should not create Schedule section. So we omit Schedule.
- Benefits: Not explicit; there is mention of hiring incentives, trial period, veterans preference, etc. Might be considered benefits but not explicit like health insurance. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does posting state benefits? It mentions "Hiring Incentives The NRO may offer hiring incentives and other entitlements at management's discretion." That's a benefit-ish. Also "Trial Period All new DCIPS employees will be required to serve a 2-year trial period." That's not a benefit. "Veterans' Preference". Might be considered benefit but not explicit like health, retirement. I'd say we can include a Benefits section if we have concrete info like hiring incentives. It's somewhat vague but still stated. I'd include Benefits with bullet points: hiring incentives, veterans' preference, trial period? Actually trial period is obligation not benefit. But we can include hiring incentives and veterans' preference.
Better to keep sections minimal: About the role (maybe as
About the role), Responsibilities (Responsibilities), Requirements (Requirements), Qualifications (Qualifications), Skills (Key Competencies) maybe combine Qualifications and Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
Let's extract content for each:
About the role: paragraph describing NRO mission and role overview.
Responsibilities: bullet list from "What You Will Be Doing".
Requirements: Basic Eligibility + Required Qualifications (maybe combine). Could separate Basic Eligibility as part of Requirements.
Qualifications: Desired Qualifications.
Skills: Key Competencies.
Benefits: Hiring Incentives, Veterans' Preference (maybe also mention trial period? but that's not benefit). We'll include hiring incentives and veterans' preference.
Pay: Salary ranges.
Schedule: Not present, omit.
We must not repeat job title as heading. The job title is "Technical Integrator". Not used.
We must not include Job ID/requisition numbers.
We must remove boilerplate: navigation, legal, EEO, etc. Also remove duplicated lines, application instructions (like "Resumes must be submitted by...").
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like travel requirement, location, etc. Where to put travel? Could be under Responsibilities or maybe a separate section? Not in allowed headings. Could embed under Responsibilities as a bullet: "Travel Requirement: substantial travel...". That is part of responsibilities. So we can add a bullet under Responsibilities for travel.
Also location: Chantilly, VA, telework not available. Could be under About the role or Responsibilities. Probably About the role.
We need to ensure we don't lose any substantive info: Basic eligibility, required qualifications, desired qualifications, key competencies, hiring incentives, veterans preference, trial period, etc.
We need to format lists with - . For prose, use
.
We must output only HTML fragment, no /, no markdown.
Let's craft.
Structure:
About the role
... paragraph ...
Responsibilities
- Deploy to domestic and international customer sites to work directly with operational users and field representatives.
- Serve as the primary technical integrator between Cosmic Horizon’s prototyping team and operational end users.
- Conduct user-needs assessments to understand mission workflows, pain points, data sources, system constraints, and desired operational outcomes.
- Translate user challenges and mission requirements into clear, actionable technical requirements, user stories, development priorities, and integration plans.
- Provide hands-on technical support, including software development, scripting, coding, data-pipeline development, application integration, testing, troubleshooting, and technical documentation.
- Support the design, development, prototyping, deployment, and sustainment of workflow-automation and AI-enabled capabilities.
- Integrate prototype capabilities with approved mission systems, data sources, and user workflows, consistent with applicable security, data-handling, and deployment requirements.
- Evaluate prototype performance with operational users; collect feedback; identify defects, usability issues, and technical risks; and recommend improvements.
- Coordinate technical activities among developers, data scientists, engineers, mission users, stakeholders, and field representatives.
- Build and maintain productive relationships with mission users, customer organizations, and other stakeholders to support capability adoption and mission outcomes.
- Communicate technical status, risks, dependencies, user feedback, and recommendations to government leadership and project stakeholders.
- Support Agile planning, backlog refinement, demonstrations, iterative development, and transition of successful prototypes to enduring capabilities.
- Travel Requirement: This position requires substantial travel, including deployments of approximately two to three months per rotation to locations where NRO tools and data are used by operational customers. The incumbent is expected to complete at least two embedded rotations per fiscal year, totaling a minimum of approximately four months annually away from the permanent duty location. Depending on mission needs, the incumbent may deploy up to three times per year. Travel may include domestic and overseas locations and may require work outside normal duty hours, including evenings, weekends, or holidays.
Requirements
Basic Eligibility:
- Must be a U.S. Citizen
- Must be able to obtain and maintain a TS/SCI security clearance
- Will be subject to pre-employment and periodic drug testing
- Will be subject to pre-employment and periodic polygraph examinations
Required Qualifications:
- Demonstrated knowledge of coding and software-development practices sufficient to contribute to technical projects and support development, integration, testing, or troubleshooting activities.
- Ability to gather and document user needs and translate them into technical requirements under supervision or with limited guidance.
- Ability and willingness to travel for extended periods in support of operational users.
- Experience applying software-development, data-engineering, systems-integration, or technical-analysis skills to solve user or mission problems.
Qualifications
Desired Qualifications:
- Bachelor’s or Master’s degree in computer science, software engineering, data science, information systems, engineering, or a closely related technical field.
- Experience with Agile software-development methods, including Scrum, Kanban, user stories, backlog management, sprint planning, and iterative delivery.
- Experience with DevSecOps practices, including secure software development, automated testing, continuous integration/continuous delivery (CI/CD), configuration management, and software release processes.
- Demonstrated ability to lead discrete technical projects or workstreams and contribute directly through hands-on coding, system integration, data-pipeline development, testing, or deployment.
- Experience working with users or stakeholders to define requirements, resolve technical issues, assess solution effectiveness, and improve delivered capabilities.
- Ability to operate with initiative in distributed, customer-facing, and mission-focused environments.
- Experience deploying or sustaining applications in cloud environments.
- Experience developing data pipelines, data-processing workflows, APIs, automation scripts, or AI/ML-enabled applications.
- Experience integrating software tools with operational systems and user workflows.
- Experience supporting geographically dispersed customers, field users, or mission partners.
- Strong written and verbal communication skills, particularly the ability to explain technical issues to nontechnical audiences.
Key Competencies
Candidates Should Demonstrate The Following Knowledge, Skills, And Abilities:
- Software Development: Knowledge of programming, software design, debugging, testing, version control, and technical documentation.
- Systems and Data Integration: Ability to connect applications, data sources, interfaces, and workflows into usable operational capabilities.
- Requirements Engineering: Ability to elicit, analyze, document, prioritize, and validate user and system requirements.
- Technical Problem Solving: Ability to identify root causes, assess alternatives, manage technical risks, and implement practical solutions.
- Customer Engagement: Ability to build trust with operational users, understand mission needs, and incorporate user feedback into delivered products.
- Project Execution: Ability to manage tasks, dependencies, schedules, and deliverables in a fast-paced prototyping environment.
- Communication: Ability to communicate technical concepts, status, risks, and recommendations clearly to technical and nontechnical stakeholders.
Benefits
- Hiring incentives may be offered at management's discretion.
- Veterans' Preference applied to eligible candidates in accordance with DoD policy.
Pay
Salary ranges (GG scale):
- GG-07: $81,901 - $106,474
- GG-09: $94,909 -
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting and decide which sections to include. Let's extract key info: - About the role: description of NRO, mission, position description: "Technical Integrator to serve as primary link between government prototyping team, Cosmic Horizon, and operational end users. Deploy to customer locations to embed with mission users, understand operational workflows, and deliver workflow-automation and AI integration solutions. This is an entry level position at the GG-07 to GG-11 level. The selected candidate will perform hands-on technical work while building operational, technical, and stakeholder-integration experience required for increased responsibility." Also location: Chantilly, VA, telework not available. - Responsibilities: list under "What You Will Be Doing": bullet points. - Requirements: "Basic Eligibility For A Position With The NRO": US Citizen, TS/SCI clearance, drug testing, polygraph. Also "Required Qualifications": list. - Qualifications: maybe "Desired Qualifications". - Skills: maybe "Key Competencies Candidates Should Demonstrate". - Benefits: Not explicitly listed; there is mention of hiring incentives, trial period, veterans preference, etc. But not explicit benefits like health, retirement. Might not include Benefits section unless specific. - Pay: Salary info: GG-07: $81,901 - $106,474; GG-09: $94,909 - $123,388; GG-11: $105,262 - $136,848. Also mention STEM pay etc. So we can include Pay section. - Schedule: Not explicit schedule; maybe full-time, travel requirement. Travel requirement is separate; schedule maybe not given. Could include Travel under Responsibilities? Travel requirement is separate paragraph. Could include a "Travel" section? Not in allowed headings. Could embed under Responsibilities or maybe under "Schedule"? Not exactly schedule. The instruction says use headings for Benefits, Pay, Schedule. If schedule not specified, we should not create Schedule section. So we omit Schedule. - Benefits: Not explicit; there is mention of hiring incentives, trial period, veterans preference, etc. Might be considered benefits but not explicit like health insurance. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does posting state benefits? It mentions "Hiring Incentives The NRO may offer hiring incentives and other entitlements at management's discretion." That's a benefit-ish. Also "Trial Period All new DCIPS employees will be required to serve a 2-year trial period." That's not a benefit. "Veterans' Preference". Might be considered benefit but not explicit like health, retirement. I'd say we can include a Benefits section if we have concrete info like hiring incentives. It's somewhat vague but still stated. I'd include Benefits with bullet points: hiring incentives, veterans' preference, trial period? Actually trial period is obligation not benefit. But we can include hiring incentives and veterans' preference. Better to keep sections minimal: About the role (maybe as
About the role), Responsibilities (Responsibilities), Requirements (Requirements), Qualifications (Qualifications), Skills (Key Competencies) maybe combine Qualifications and Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
Let's extract content for each:
About the role: paragraph describing NRO mission and role overview.
Responsibilities: bullet list from "What You Will Be Doing".
Requirements: Basic Eligibility + Required Qualifications (maybe combine). Could separate Basic Eligibility as part of Requirements.
Qualifications: Desired Qualifications.
Skills: Key Competencies.
Benefits: Hiring Incentives, Veterans' Preference (maybe also mention trial period? but that's not benefit). We'll include hiring incentives and veterans' preference.
Pay: Salary ranges.
Schedule: Not present, omit.
We must not repeat job title as heading. The job title is "Technical Integrator". Not used.
We must not include Job ID/requisition numbers.
We must remove boilerplate: navigation, legal, EEO, etc. Also remove duplicated lines, application instructions (like "Resumes must be submitted by...").
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like travel requirement, location, etc. Where to put travel? Could be under Responsibilities or maybe a separate section? Not in allowed headings. Could embed under Responsibilities as a bullet: "Travel Requirement: substantial travel...". That is part of responsibilities. So we can add a bullet under Responsibilities for travel.
Also location: Chantilly, VA, telework not available. Could be under About the role or Responsibilities. Probably About the role.
We need to ensure we don't lose any substantive info: Basic eligibility, required qualifications, desired qualifications, key competencies, hiring incentives, veterans preference, trial period, etc.
We need to format lists with - . For prose, use
.
We must output only HTML fragment, no /, no markdown.
Let's craft.
Structure:
About the role
... paragraph ...
Responsibilities
- Deploy to domestic and international customer sites to work directly with operational users and field representatives.
- Serve as the primary technical integrator between Cosmic Horizon’s prototyping team and operational end users.
- Conduct user-needs assessments to understand mission workflows, pain points, data sources, system constraints, and desired operational outcomes.
- Translate user challenges and mission requirements into clear, actionable technical requirements, user stories, development priorities, and integration plans.
- Provide hands-on technical support, including software development, scripting, coding, data-pipeline development, application integration, testing, troubleshooting, and technical documentation.
- Support the design, development, prototyping, deployment, and sustainment of workflow-automation and AI-enabled capabilities.
- Integrate prototype capabilities with approved mission systems, data sources, and user workflows, consistent with applicable security, data-handling, and deployment requirements.
- Evaluate prototype performance with operational users; collect feedback; identify defects, usability issues, and technical risks; and recommend improvements.
- Coordinate technical activities among developers, data scientists, engineers, mission users, stakeholders, and field representatives.
- Build and maintain productive relationships with mission users, customer organizations, and other stakeholders to support capability adoption and mission outcomes.
- Communicate technical status, risks, dependencies, user feedback, and recommendations to government leadership and project stakeholders.
- Support Agile planning, backlog refinement, demonstrations, iterative development, and transition of successful prototypes to enduring capabilities.
- Travel Requirement: This position requires substantial travel, including deployments of approximately two to three months per rotation to locations where NRO tools and data are used by operational customers. The incumbent is expected to complete at least two embedded rotations per fiscal year, totaling a minimum of approximately four months annually away from the permanent duty location. Depending on mission needs, the incumbent may deploy up to three times per year. Travel may include domestic and overseas locations and may require work outside normal duty hours, including evenings, weekends, or holidays.
Requirements
Basic Eligibility:
- Must be a U.S. Citizen
- Must be able to obtain and maintain a TS/SCI security clearance
- Will be subject to pre-employment and periodic drug testing
- Will be subject to pre-employment and periodic polygraph examinations
Required Qualifications:
- Demonstrated knowledge of coding and software-development practices sufficient to contribute to technical projects and support development, integration, testing, or troubleshooting activities.
- Ability to gather and document user needs and translate them into technical requirements under supervision or with limited guidance.
- Ability and willingness to travel for extended periods in support of operational users.
- Experience applying software-development, data-engineering, systems-integration, or technical-analysis skills to solve user or mission problems.
Qualifications
Desired Qualifications:
- Bachelor’s or Master’s degree in computer science, software engineering, data science, information systems, engineering, or a closely related technical field.
- Experience with Agile software-development methods, including Scrum, Kanban, user stories, backlog management, sprint planning, and iterative delivery.
- Experience with DevSecOps practices, including secure software development, automated testing, continuous integration/continuous delivery (CI/CD), configuration management, and software release processes.
- Demonstrated ability to lead discrete technical projects or workstreams and contribute directly through hands-on coding, system integration, data-pipeline development, testing, or deployment.
- Experience working with users or stakeholders to define requirements, resolve technical issues, assess solution effectiveness, and improve delivered capabilities.
- Ability to operate with initiative in distributed, customer-facing, and mission-focused environments.
- Experience deploying or sustaining applications in cloud environments.
- Experience developing data pipelines, data-processing workflows, APIs, automation scripts, or AI/ML-enabled applications.
- Experience integrating software tools with operational systems and user workflows.
- Experience supporting geographically dispersed customers, field users, or mission partners.
- Strong written and verbal communication skills, particularly the ability to explain technical issues to nontechnical audiences.
Key Competencies
Candidates Should Demonstrate The Following Knowledge, Skills, And Abilities:
- Software Development: Knowledge of programming, software design, debugging, testing, version control, and technical documentation.
- Systems and Data Integration: Ability to connect applications, data sources, interfaces, and workflows into usable operational capabilities.
- Requirements Engineering: Ability to elicit, analyze, document, prioritize, and validate user and system requirements.
- Technical Problem Solving: Ability to identify root causes, assess alternatives, manage technical risks, and implement practical solutions.
- Customer Engagement: Ability to build trust with operational users, understand mission needs, and incorporate user feedback into delivered products.
- Project Execution: Ability to manage tasks, dependencies, schedules, and deliverables in a fast-paced prototyping environment.
- Communication: Ability to communicate technical concepts, status, risks, and recommendations clearly to technical and nontechnical stakeholders.
Benefits
- Hiring incentives may be offered at management's discretion.
- Veterans' Preference applied to eligible candidates in accordance with DoD policy.
Pay
Salary ranges (GG scale):
- GG-07: $81,901 - $106,474
- GG-09: $94,909 -
Requirements), Qualifications (Qualifications), Skills (Key Competencies) maybe combine Qualifications and Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
Let's extract content for each:
About the role: paragraph describing NRO mission and role overview.
Responsibilities: bullet list from "What You Will Be Doing".
Requirements: Basic Eligibility + Required Qualifications (maybe combine). Could separate Basic Eligibility as part of Requirements.
Qualifications: Desired Qualifications.
Skills: Key Competencies.
Benefits: Hiring Incentives, Veterans' Preference (maybe also mention trial period? but that's not benefit). We'll include hiring incentives and veterans' preference.
Pay: Salary ranges.
Schedule: Not present, omit.
We must not repeat job title as heading. The job title is "Technical Integrator". Not used.
We must not include Job ID/requisition numbers.
We must remove boilerplate: navigation, legal, EEO, etc. Also remove duplicated lines, application instructions (like "Resumes must be submitted by...").
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like travel requirement, location, etc. Where to put travel? Could be under Responsibilities or maybe a separate section? Not in allowed headings. Could embed under Responsibilities as a bullet: "Travel Requirement: substantial travel...". That is part of responsibilities. So we can add a bullet under Responsibilities for travel.
Also location: Chantilly, VA, telework not available. Could be under About the role or Responsibilities. Probably About the role.
We need to ensure we don't lose any substantive info: Basic eligibility, required qualifications, desired qualifications, key competencies, hiring incentives, veterans preference, trial period, etc.
We need to format lists with - . For prose, use
.
We must output only HTML fragment, no /, no markdown.
Let's craft.
Structure:
About the role
... paragraph ...
Responsibilities
- Deploy to domestic and international customer sites to work directly with operational users and field representatives.
- Serve as the primary technical integrator between Cosmic Horizon’s prototyping team and operational end users.
- Conduct user-needs assessments to understand mission workflows, pain points, data sources, system constraints, and desired operational outcomes.
- Translate user challenges and mission requirements into clear, actionable technical requirements, user stories, development priorities, and integration plans.
- Provide hands-on technical support, including software development, scripting, coding, data-pipeline development, application integration, testing, troubleshooting, and technical documentation.
- Support the design, development, prototyping, deployment, and sustainment of workflow-automation and AI-enabled capabilities.
- Integrate prototype capabilities with approved mission systems, data sources, and user workflows, consistent with applicable security, data-handling, and deployment requirements.
- Evaluate prototype performance with operational users; collect feedback; identify defects, usability issues, and technical risks; and recommend improvements.
- Coordinate technical activities among developers, data scientists, engineers, mission users, stakeholders, and field representatives.
- Build and maintain productive relationships with mission users, customer organizations, and other stakeholders to support capability adoption and mission outcomes.
- Communicate technical status, risks, dependencies, user feedback, and recommendations to government leadership and project stakeholders.
- Support Agile planning, backlog refinement, demonstrations, iterative development, and transition of successful prototypes to enduring capabilities.
- Travel Requirement: This position requires substantial travel, including deployments of approximately two to three months per rotation to locations where NRO tools and data are used by operational customers. The incumbent is expected to complete at least two embedded rotations per fiscal year, totaling a minimum of approximately four months annually away from the permanent duty location. Depending on mission needs, the incumbent may deploy up to three times per year. Travel may include domestic and overseas locations and may require work outside normal duty hours, including evenings, weekends, or holidays.
Requirements
Basic Eligibility:
- Must be a U.S. Citizen
- Must be able to obtain and maintain a TS/SCI security clearance
- Will be subject to pre-employment and periodic drug testing
- Will be subject to pre-employment and periodic polygraph examinations
Required Qualifications:
- Demonstrated knowledge of coding and software-development practices sufficient to contribute to technical projects and support development, integration, testing, or troubleshooting activities.
- Ability to gather and document user needs and translate them into technical requirements under supervision or with limited guidance.
- Ability and willingness to travel for extended periods in support of operational users.
- Experience applying software-development, data-engineering, systems-integration, or technical-analysis skills to solve user or mission problems.
Qualifications
Desired Qualifications:
- Bachelor’s or Master’s degree in computer science, software engineering, data science, information systems, engineering, or a closely related technical field.
- Experience with Agile software-development methods, including Scrum, Kanban, user stories, backlog management, sprint planning, and iterative delivery.
- Experience with DevSecOps practices, including secure software development, automated testing, continuous integration/continuous delivery (CI/CD), configuration management, and software release processes.
- Demonstrated ability to lead discrete technical projects or workstreams and contribute directly through hands-on coding, system integration, data-pipeline development, testing, or deployment.
- Experience working with users or stakeholders to define requirements, resolve technical issues, assess solution effectiveness, and improve delivered capabilities.
- Ability to operate with initiative in distributed, customer-facing, and mission-focused environments.
- Experience deploying or sustaining applications in cloud environments.
- Experience developing data pipelines, data-processing workflows, APIs, automation scripts, or AI/ML-enabled applications.
- Experience integrating software tools with operational systems and user workflows.
- Experience supporting geographically dispersed customers, field users, or mission partners.
- Strong written and verbal communication skills, particularly the ability to explain technical issues to nontechnical audiences.
Key Competencies
Candidates Should Demonstrate The Following Knowledge, Skills, And Abilities:
- Software Development: Knowledge of programming, software design, debugging, testing, version control, and technical documentation.
- Systems and Data Integration: Ability to connect applications, data sources, interfaces, and workflows into usable operational capabilities.
- Requirements Engineering: Ability to elicit, analyze, document, prioritize, and validate user and system requirements.
- Technical Problem Solving: Ability to identify root causes, assess alternatives, manage technical risks, and implement practical solutions.
- Customer Engagement: Ability to build trust with operational users, understand mission needs, and incorporate user feedback into delivered products.
- Project Execution: Ability to manage tasks, dependencies, schedules, and deliverables in a fast-paced prototyping environment.
- Communication: Ability to communicate technical concepts, status, risks, and recommendations clearly to technical and nontechnical stakeholders.
Benefits
- Hiring incentives may be offered at management's discretion.
- Veterans' Preference applied to eligible candidates in accordance with DoD policy.
Pay
Salary ranges (GG scale):
- GG-07: $81,901 - $106,474
- GG-09: $94,909 -
Key Competencies) maybe combine Qualifications and Skills? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
Let's extract content for each:
About the role: paragraph describing NRO mission and role overview.
Responsibilities: bullet list from "What You Will Be Doing".
Requirements: Basic Eligibility + Required Qualifications (maybe combine). Could separate Basic Eligibility as part of Requirements.
Qualifications: Desired Qualifications.
Skills: Key Competencies.
Benefits: Hiring Incentives, Veterans' Preference (maybe also mention trial period? but that's not benefit). We'll include hiring incentives and veterans' preference.
Pay: Salary ranges.
Schedule: Not present, omit.
We must not repeat job title as heading. The job title is "Technical Integrator". Not used.
We must not include Job ID/requisition numbers.
We must remove boilerplate: navigation, legal, EEO, etc. Also remove duplicated lines, application instructions (like "Resumes must be submitted by...").
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like travel requirement, location, etc. Where to put travel? Could be under Responsibilities or maybe a separate section? Not in allowed headings. Could embed under Responsibilities as a bullet: "Travel Requirement: substantial travel...". That is part of responsibilities. So we can add a bullet under Responsibilities for travel.
Also location: Chantilly, VA, telework not available. Could be under About the role or Responsibilities. Probably About the role.
We need to ensure we don't lose any substantive info: Basic eligibility, required qualifications, desired qualifications, key competencies, hiring incentives, veterans preference, trial period, etc.
We need to format lists with - . For prose, use
.
We must output only HTML fragment, no /, no markdown.
Let's craft.
Structure:
About the role
... paragraph ...
Responsibilities
- Deploy to domestic and international customer sites to work directly with operational users and field representatives.
- Serve as the primary technical integrator between Cosmic Horizon’s prototyping team and operational end users.
- Conduct user-needs assessments to understand mission workflows, pain points, data sources, system constraints, and desired operational outcomes.
- Translate user challenges and mission requirements into clear, actionable technical requirements, user stories, development priorities, and integration plans.
- Provide hands-on technical support, including software development, scripting, coding, data-pipeline development, application integration, testing, troubleshooting, and technical documentation.
- Support the design, development, prototyping, deployment, and sustainment of workflow-automation and AI-enabled capabilities.
- Integrate prototype capabilities with approved mission systems, data sources, and user workflows, consistent with applicable security, data-handling, and deployment requirements.
- Evaluate prototype performance with operational users; collect feedback; identify defects, usability issues, and technical risks; and recommend improvements.
- Coordinate technical activities among developers, data scientists, engineers, mission users, stakeholders, and field representatives.
- Build and maintain productive relationships with mission users, customer organizations, and other stakeholders to support capability adoption and mission outcomes.
- Communicate technical status, risks, dependencies, user feedback, and recommendations to government leadership and project stakeholders.
- Support Agile planning, backlog refinement, demonstrations, iterative development, and transition of successful prototypes to enduring capabilities.
- Travel Requirement: This position requires substantial travel, including deployments of approximately two to three months per rotation to locations where NRO tools and data are used by operational customers. The incumbent is expected to complete at least two embedded rotations per fiscal year, totaling a minimum of approximately four months annually away from the permanent duty location. Depending on mission needs, the incumbent may deploy up to three times per year. Travel may include domestic and overseas locations and may require work outside normal duty hours, including evenings, weekends, or holidays.
Requirements
Basic Eligibility:
- Must be a U.S. Citizen
- Must be able to obtain and maintain a TS/SCI security clearance
- Will be subject to pre-employment and periodic drug testing
- Will be subject to pre-employment and periodic polygraph examinations
Required Qualifications:
- Demonstrated knowledge of coding and software-development practices sufficient to contribute to technical projects and support development, integration, testing, or troubleshooting activities.
- Ability to gather and document user needs and translate them into technical requirements under supervision or with limited guidance.
- Ability and willingness to travel for extended periods in support of operational users.
- Experience applying software-development, data-engineering, systems-integration, or technical-analysis skills to solve user or mission problems.
Qualifications
Desired Qualifications:
- Bachelor’s or Master’s degree in computer science, software engineering, data science, information systems, engineering, or a closely related technical field.
- Experience with Agile software-development methods, including Scrum, Kanban, user stories, backlog management, sprint planning, and iterative delivery.
- Experience with DevSecOps practices, including secure software development, automated testing, continuous integration/continuous delivery (CI/CD), configuration management, and software release processes.
- Demonstrated ability to lead discrete technical projects or workstreams and contribute directly through hands-on coding, system integration, data-pipeline development, testing, or deployment.
- Experience working with users or stakeholders to define requirements, resolve technical issues, assess solution effectiveness, and improve delivered capabilities.
- Ability to operate with initiative in distributed, customer-facing, and mission-focused environments.
- Experience deploying or sustaining applications in cloud environments.
- Experience developing data pipelines, data-processing workflows, APIs, automation scripts, or AI/ML-enabled applications.
- Experience integrating software tools with operational systems and user workflows.
- Experience supporting geographically dispersed customers, field users, or mission partners.
- Strong written and verbal communication skills, particularly the ability to explain technical issues to nontechnical audiences.
Key Competencies
Candidates Should Demonstrate The Following Knowledge, Skills, And Abilities:
- Software Development: Knowledge of programming, software design, debugging, testing, version control, and technical documentation.
- Systems and Data Integration: Ability to connect applications, data sources, interfaces, and workflows into usable operational capabilities.
- Requirements Engineering: Ability to elicit, analyze, document, prioritize, and validate user and system requirements.
- Technical Problem Solving: Ability to identify root causes, assess alternatives, manage technical risks, and implement practical solutions.
- Customer Engagement: Ability to build trust with operational users, understand mission needs, and incorporate user feedback into delivered products.
- Project Execution: Ability to manage tasks, dependencies, schedules, and deliverables in a fast-paced prototyping environment.
- Communication: Ability to communicate technical concepts, status, risks, and recommendations clearly to technical and nontechnical stakeholders.
Benefits
- Hiring incentives may be offered at management's discretion.
- Veterans' Preference applied to eligible candidates in accordance with DoD policy.
Pay
Salary ranges (GG scale):
- GG-07: $81,901 - $106,474
- GG-09: $94,909 -
. We must output only HTML fragment, no /, no markdown. Let's craft. Structure:
About the role
... paragraph ...
Responsibilities
- Deploy to domestic and international customer sites to work directly with operational users and field representatives.
- Serve as the primary technical integrator between Cosmic Horizon’s prototyping team and operational end users.
- Conduct user-needs assessments to understand mission workflows, pain points, data sources, system constraints, and desired operational outcomes.
- Translate user challenges and mission requirements into clear, actionable technical requirements, user stories, development priorities, and integration plans.
- Provide hands-on technical support, including software development, scripting, coding, data-pipeline development, application integration, testing, troubleshooting, and technical documentation.
- Support the design, development, prototyping, deployment, and sustainment of workflow-automation and AI-enabled capabilities.
- Integrate prototype capabilities with approved mission systems, data sources, and user workflows, consistent with applicable security, data-handling, and deployment requirements.
- Evaluate prototype performance with operational users; collect feedback; identify defects, usability issues, and technical risks; and recommend improvements.
- Coordinate technical activities among developers, data scientists, engineers, mission users, stakeholders, and field representatives.
- Build and maintain productive relationships with mission users, customer organizations, and other stakeholders to support capability adoption and mission outcomes.
- Communicate technical status, risks, dependencies, user feedback, and recommendations to government leadership and project stakeholders.
- Support Agile planning, backlog refinement, demonstrations, iterative development, and transition of successful prototypes to enduring capabilities.
- Travel Requirement: This position requires substantial travel, including deployments of approximately two to three months per rotation to locations where NRO tools and data are used by operational customers. The incumbent is expected to complete at least two embedded rotations per fiscal year, totaling a minimum of approximately four months annually away from the permanent duty location. Depending on mission needs, the incumbent may deploy up to three times per year. Travel may include domestic and overseas locations and may require work outside normal duty hours, including evenings, weekends, or holidays.
Requirements
Basic Eligibility:
- Must be a U.S. Citizen
- Must be able to obtain and maintain a TS/SCI security clearance
- Will be subject to pre-employment and periodic drug testing
- Will be subject to pre-employment and periodic polygraph examinations
Required Qualifications:
- Demonstrated knowledge of coding and software-development practices sufficient to contribute to technical projects and support development, integration, testing, or troubleshooting activities.
- Ability to gather and document user needs and translate them into technical requirements under supervision or with limited guidance.
- Ability and willingness to travel for extended periods in support of operational users.
- Experience applying software-development, data-engineering, systems-integration, or technical-analysis skills to solve user or mission problems.
Qualifications
Desired Qualifications:
- Bachelor’s or Master’s degree in computer science, software engineering, data science, information systems, engineering, or a closely related technical field.
- Experience with Agile software-development methods, including Scrum, Kanban, user stories, backlog management, sprint planning, and iterative delivery.
- Experience with DevSecOps practices, including secure software development, automated testing, continuous integration/continuous delivery (CI/CD), configuration management, and software release processes.
- Demonstrated ability to lead discrete technical projects or workstreams and contribute directly through hands-on coding, system integration, data-pipeline development, testing, or deployment.
- Experience working with users or stakeholders to define requirements, resolve technical issues, assess solution effectiveness, and improve delivered capabilities.
- Ability to operate with initiative in distributed, customer-facing, and mission-focused environments.
- Experience deploying or sustaining applications in cloud environments.
- Experience developing data pipelines, data-processing workflows, APIs, automation scripts, or AI/ML-enabled applications.
- Experience integrating software tools with operational systems and user workflows.
- Experience supporting geographically dispersed customers, field users, or mission partners.
- Strong written and verbal communication skills, particularly the ability to explain technical issues to nontechnical audiences.
Key Competencies
Candidates Should Demonstrate The Following Knowledge, Skills, And Abilities:
- Software Development: Knowledge of programming, software design, debugging, testing, version control, and technical documentation.
- Systems and Data Integration: Ability to connect applications, data sources, interfaces, and workflows into usable operational capabilities.
- Requirements Engineering: Ability to elicit, analyze, document, prioritize, and validate user and system requirements.
- Technical Problem Solving: Ability to identify root causes, assess alternatives, manage technical risks, and implement practical solutions.
- Customer Engagement: Ability to build trust with operational users, understand mission needs, and incorporate user feedback into delivered products.
- Project Execution: Ability to manage tasks, dependencies, schedules, and deliverables in a fast-paced prototyping environment.
- Communication: Ability to communicate technical concepts, status, risks, and recommendations clearly to technical and nontechnical stakeholders.
Benefits
- Hiring incentives may be offered at management's discretion.
- Veterans' Preference applied to eligible candidates in accordance with DoD policy.
Pay
Salary ranges (GG scale):
- GG-07: $81,901 - $106,474
- GG-09: $94,909 -