Software Integration and Test Engineer

Role Overview

We are seeking a Software Testing & Integration Engineer responsible for validating software quality through

comprehensive testing, system integration, and compliance with mission-critical industry standards. You will

execute the full testing lifecycle for distributed desktop applications in the defence and situational awareness

domains.

Responsibilities

• Test Execution: Design and execute test plans for unit, integration, system qualification, and

performance testing phases.

• Documentation: Prepare IEEE-compliant documentation, including Software Test Plans (STP),

Descriptions (STD), and Reports (STR).

• System Integration: Validate sub-module interfaces, network communication channels (UDP/TCP), and

plugin-based architectures.

• Specialized Testing: Execute redundancy/failover tests (Hot Standby), Data Fusion integration, and

Record & Replay validation.

• Process Compliance: Work within CMMI-compliant frameworks to maintain strict requirements

traceability (RTM) from design to test results. Work with SQAG for generation of necessary compliant

reports.

• Automation & Tools: Use automation frameworks (GTest/Qt Test) and requirements management tools

like IBM DOORS or equivalent.

Required Skills

• Technical Testing: 2+ years of hands-on experience in testing/integrating multi-module C++ or

embedded desktop applications.

• Standards Knowledge: Deep understanding of IEEE standards (29148, 829, 1063) and SDLC/QA

processes.

• Performance Testing: Ability to define benchmarks and measure system throughput, latency, and GUI

rendering performance.

• Environment Mastery: Proficient in Linux (RHEL/Ubuntu), Git, SQAG, and defect lifecycle tools like Jira

or Redmine.

• Protocol & Middleware: Basic understanding of DDS (Pub/Sub) and socket programming to simulate

network data sources.

• Coding Basics: Sufficient knowledge of C++ or Python to write test harnesses and mock/simulation

scripts.

• GUI Render Performance Validation: Measuring and documenting frame rate under load using profiling

tools (QElapsedTimer, OpenGL frame timing, system-level GPU profiling on Linux).

• Visual State Validation Testing: Verifying that UI element visual states (e.g. color, shape, overlay)

change correctly in response to specific incoming network events, independent of other concurrent

activity.

• UI Interaction Testing: Designing and executing test cases for complex user interactions (multi-item

selection, context menus, hover behaviors) under simultaneous high-frequency data load.

• Error Handling Test Execution: Defining and running tests for network disconnection, malformed packet

injection, and graceful degradation scenarios.

• C++ & Automation Frameworks: Experience in C++ environment testing and Manual/Automation

frameworks.

• Technical Documentation: Proven ability to produce clear, structured technical documentation for

defense/aerospace standards.

Who Should Not Apply

This role requires a precision-oriented engineer comfortable with defense-grade protocols. Avoid candidates

with the following profiles:

• Manual-Only Testers: The POC explicitly requires the use of automatic tools for test plans and high-

frequency data simulation. If they cannot write scripts to automate tests, they will not meet the

requirement.

• Web-Application Specialists: Candidates who have only tested REST APIs, websites, or mobile apps. This

project involves low-level binary protocols (DDS) and multicast networking that require a different

debugging mindset.

• Standard OS Testers: If their experience is limited to Windows or macOS. The requirement for RHEL 9

and deployment via deploy.sh scripts is mandatory.

• Documentation-Averse Candidates: This role involves heavy IEEE and CMMI Level 4 compliance.

Candidates who find formal technical writing or strict adherence to documentation standards tedious will

not succeed here.

• "Black-Box" Only Testers: Because this involves Integration Engineering, the candidate must be able to

look at C++ structs and DDS IDL files to understand why data correlation might be failing.