C2 Systems Engineer

We are looking for an experienced systems engineer to help the Defense Information Systems Agency (DISA) strategically modernize the Global Command and Control System – Joint (GCCS-J). You’ll be the person who turns emerging warfighter problems into clear, testable requirements for GCCS-J modernization — engaging GCCS-J operators, distilling their needs, partnering with senior software developers on the design, and then helping the PMO plan and coordinate the delivery of modernized GCCS-J capability for real‑world operations. Our purpose is singular — to optimize warfighter performance through information technology.

• To become a member of the BluestoneLogic team, you’ll need:

  • 3-7 years experience in systems engineering for software‑intensive systems — eliciting requirements, defining acceptance criteria, and shaping designs with development teams.

  • Experience supporting Joint C2 systems is a bonus.

  • Familiarity with cloud and edge deployment patterns, API integration, and operating across classified networks (e.g., SIPR, SECRET/REL) is a bonus.

  • Bachelor’s and/or Master’s degree in Computer Science, Computer Information Systems, Systems Engineering, Mathematics, or similar technical discipline.

  • U.S. citizenship and an active DoD SECRET clearance, or eligibility to obtain a final DoD SECRET clearance or above.

  • Willingness to travel up to 6 weeks/year both CONUS and OCONUS, for Combatant Command engagements (e.g., Tampa, Colorado Springs, Doral, Stuttgart, and Oahu).

  • Ability to work in a hybrid model across BluestoneLogic HQ in Washington, D.C., DISA HQ at Fort Meade, MD, and remote.

As a systems engineer on our GCCS-J Strategic Engineering team, you’ll be the bridge between Combatant Command operators, the DISA GCCS-J Program Management Office (PMO), and the GCCS-J software development team.

• →

  Engage Combatant Command personnel to understand how they employ GCCS-J as part of their C2 mission, and capture the warfighter needs that will drive improvements and enhancements for GCCS-J.

• →

  Derive GCCS-J integration requirements through stakeholder engagement with the GCCS-J Family of Systems (FoS) program offices, other C2 systems delivered by US military service programs, third‑party data providers, and third-party data consumers (such as Palantir Maven Smart Systems).

• →

  Write clear, testable requirements and acceptance criteria that confirm successful delivery of warfighting outcomes desired by the Joint C2 community.

• →

  Partner with senior software developers to shape the design of the integrated solution before implementation — making architectural trade‑offs, weighing existing‑system reuse vs. commercial and open source solutions vs. custom software, and ensuring the design will satisfy the acceptance criteria.

• →

  Plan how GCCS-J modernization fits into Combatant Command demonstrations and exercises — what scenarios it supports, what data it carries, what success looks like, and what evidence we collect.

• →

  During demos and exercises, coordinate with the operations team that is using modernized GCCS-J — ensuring requirements are understood, scope is managed, and exercise objectives are met.

• →

  Produce the artifacts that move the program forward: DoDAF‑compliant architectural diagrams, data correlation rulesets, technical design and solution documentation, TEM minutes, demonstration reports, and trip reports.

• →

  Make recommendations and advise on improvements across C2 information systems architecture, networking, legacy and high‑speed data exchange, cybersecurity, DoD‑approved commercial cloud, frontier AI models and agents, and data correlation and management.

We are seeking C2 Systems Engineers who are good at:

• Engaging warfighters and program stakeholders to elicit needs and translate them into precise integration requirements with acceptance criteria.

• Designing scalable, enterprise integration solutions in collaboration with software development teams — understanding the technology deeply without owning the production code.

• Reasoning about C2 information systems architecture, APIs, data exchange, and integration across program, service, and network boundaries.

• Analyzing data — including correlation across heterogeneous sources — to make defensible decisions about integration approach.

• Communicating your ideas and the results of your work in both verbal and written form to engineers, program leadership, and uniformed operators.

• Collaborating with program offices, government leads, and warfighters to reach a shared goal.

• Doing what needs to be done to help your customer succeed — including showing up at exercises and Combatant Commands when it matters.