Software Systems Quality Engineer in AZ

About the Role

• Role: Software Systems Quality Engineer (Compliance)
• Location: Tucson, AZ
• Type: Onsite
• Company: Raytheon
• Focus: Supporting Land & Air Defense Systems (LADS) programs.
• Activities: Primarily at 1151 East Hermans Road, with collaboration at 9030 S. Rita Road and 3350 E. Hemisphere Loop.
• Work Environment: Performed in secure labs and dedicated workspaces.

Key Responsibilities

• SWQE Tasks:
• Review of Document Deliverables (CDRL), Command Media (Policies), SW Release Packages (Windchill PDM, Azure DevOps), SW Requirements Changes, SW/System Defects, SW Pulls (Code Reviews), Media, and Test Artifacts.
• Participation in Peer Reviews (SW, SE), Control Boards (CCB, SRB), Tracking Books (Metrics), Test Witnessing (SQT, FQT), and Audits.
• Compliance Focus:
• Ensure digital products adhere to contractual requirements.
• Review and approve inputs/outputs to/from partner organizations.
• Products Focus:
• Ensure integrity of the technical data package.
• Identify, collect, and measure software quality attributes, metrics, and data.
• Improvement Focus:
• Perform independent evaluations and risk assessments across the lifecycle.
• Facilitate root cause analysis and corrective actions.
• Processes Focus:
• Leverage modern experiences with software development and quality best practices.
• Increasingly adopt Agile and DevSecOps methodologies.
• Teamwork Focus:
• Interact with customers, product development, and test personnel.
• Provide guidance to senior leadership, team members, and group peers.

Requirements & Tech Stack

• Security Clearance:
• Ability to obtain and maintain a U.S. government issued Security Clearance.
• U.S. citizenship is required.
• DoD Clearance: Secret.
• Active and existing security clearance required after day 1.
• Agile:
• SCRUM teams, sprints/increments, stories/points, backlog/burndown, continuous integration/delivery (CI/CD).
• Testing:
• Execution witnessing, location, plans, procedures, requirements traceability, reports.
• Requirements:
• Verification, software specifications, systems specifications, functionality, performance, statement of work, contracts.
• Software:
• Lifecycle processes, requirements decomposition, code reviews, functions, features, builds, configuration management.
• Defects:
• Quantification, severity, priority, age, resolution, effort, impact, implementation.
• Release:
• Delivery management, checklists, labels, versions, licenses, repositories, software executables, release notes, security bulletins, training manuals, user guides.
• Metrics:
• Defining, developing, monitoring, measuring, reporting, dashboards, tools (e.g., Business Insight reports, Jira reports, Excel tables).
• Analysis:
• Identifying process issue Root Causes and implementing Corrective Actions.
• DevSecOps Toolchains:
• Confluence, ADS – Azure DevOps Server, Jenkins, GitHub, Coverity.
• Development Tools:
• Integrated Development Environment (IDE) applications, modeling, databases (ClearCase, DOORS, RQM, Cameo, Rhapsody, Oracle, SAP).
• Networking:
• Protocols: OSI, TCP, IP, IPsec, TLS, DHCP, SNMP, FC, SCSI, DNS, IDS, SIEM.
• Connectivity: physical networks, virtual networks, local area networks (LANs), wide area networks (WANs), cloud-based infrastructures.
• Configurations: routers, switches, firewalls, VPNs.

Qualifications

• Typically requires a Bachelor’s degree in Science, Technology, Engineering or Mathematics (STEM).
• Education or Training:
• Certifications: Quality, Software Eng., Systems Eng., Agile, Cyber / IA, Project Management.
• PowerPoint: briefing creation and presentation to Senior Management.
• Standards: quality principles via AS9115, AS9100, ISO9001.
• Policies: Quality Management Systems (QMS) and/or Operating Procedures (SOPs).
• Compliance: evaluation, validation, auditing, corrective actions.
• Maintenance: processes, patches, upgrades, installation, backups, recovery, synchronization.
• Projects: leading, coordination, planning, prioritization, execution, escalation.
• Interest Areas:
• Strategy: leading cross-functional initiatives, collaborating with Business-Technical stakeholders.
• Integration: security, systems, software, hardware, connectivity, tools, equipment.
• Technology: devices, applications, servers, virtual machines, networks, storage.