Systems Engineer / Test Engineer (Junior–Mid)

We are looking for an early-career systems engineer who likes figuring out what a system actually needs to do and then proving that it does. You’ll sit down with the operators who use DoD mission systems every day, turn what they tell you into clear, testable requirements, and write the test procedures that operators and developers use to verify each release. Just as important, you’ll explain why a request should or shouldn’t be built, and stand behind that recommendation. Our purpose is singular — to optimize warfighter performance through information technology. We hire for talent and drive over years on a résumé. Strong recent graduates are encouraged to apply. You have… • A clear, structured voice. You can walk someone through a problem — the situation, the options you weighed, what you decided, and the result so operators, engineers, and leaders follow it the first time. • A curious mind. You want to understand how a system is really used, not just how it was designed. • A good ear and good judgment. You listen for what operators need versus what they ask for, weigh it against technical constraints and the backlog, and can tell a customer “not now” while pointing them to a better path. • An ownership mindset. When something is blocked, you go find the person who can unblock it instead of waiting. • A dedication to detail. A vague requirement becomes a bug or a dispute later, so you pin it down now. • A focus on the craft. You want to go deep in systems engineering and software requirements, test, and how software actually gets built. • An open mind. You welcome feedback on your work and want to grow as an engineer. We have… • A devotion to making technology work for the warfighter. We help operators work faster, better, and smarter. • An affinity to action. We’d rather start, learn, and iterate than wait for the perfect plan. • A drive for continuous improvement. We look for better ways to solve old problems, for our customers and ourselves. • Senior engineers who mentor. You’ll learn requirements and test practice alongside experienced test leads and SMEs. What you’ll do… Requirements elicitation and decomposition Run discovery with operators, subject matter experts, and government leads, through interviews, site visits, and demos, to understand mission workflows, pain points, and what would make a capability acceptable to them. • Decompose customer-expressed and contract requirements into clear, atomic, testable requirements, breaking large asks into smaller parts that can be weighed against effort to implement. • Trace requirements across subsystems and interfaces (APIs, data exchanges, connected systems) and assess the ripple effect of each change. • Capture non-functional requirements (the “-ilities”): performance, reliability, security, and operation in degraded or disconnected (DDIL) conditions. • Maintain requirements traceability from source (operator input, PWS, user stories) through design and test. Operator input and prioritization • Capture every operator or customer request as a data point: log it in the backlog, link it to existing requirements, and track it to a decision. • Weigh requests against mission value, technical constraints, and the existing backlog; recommend build, defer, or decline, and explain why. • Reconcile conflicting inputs from different operators or stakeholders and bring a recommended resolution to the team. • Close the loop with operators on what was decided and when. Documentation • Document requirements, use cases, and operational workflows in formats operators and developers both understand. • Write user stories with measurable acceptance criteria, including Given-When-Then (Gherkin) scenarios. • Use quick prototypes or mockups (including AI-assisted ones) to confirm intent with operators and show developers the target outcome, without dictating how they build it. • Produce supporting artifacts: workflow and system diagrams, Technical Exchange Meeting (TEM) minutes, and test reports. Test planning and execution • Write step-by-step test procedures and scripts that operators and developers can follow to verify functionality. • Execute and support functional, regression, integration, and user acceptance testing (UAT) for software releases. • Record results, log defects with clear reproduction steps, and verify fixes. • Help automate repeatable testing: write simple scripts for test data and log checks, turn manual procedures into automated test cases and BDD step definitions, and add them to the GitLab CI/CD pipeline with the test lead. • Contribute to functional security test cases (authentication, access control) under the guidance of the test lead. Collaboration • Work alongside developers, test leads, cybersecurity staff, and program management in an Agile environment. • Coordinate across multiple organizations and drive communication plans that keep responses and deliverables on schedule. • Participate in sprint planning, TEMs, and customer reviews; brief findings clearly to technical and non-technical audiences. • Help developers reproduce and isolate defects by reading logs and tracing system behavior to narrow the root cause. • Contribute technical writing to proposals as opportunities arise.