- Gather and assess requirements from user teams: Operations, Testing, Avionics, GNC/OBS, Systems, Analysis.
- Translate these needs into actionable backlog items: clear problem statements, acceptance criteria, and operational impact if not addressed.
- Manage and maintain a single, prioritized backlog covering all software tools, aligned with the development and qualification schedule.
- Arbitrate between competing requests and document decisions and their rationale.
- Identify whether an issue stems from a tooling need or from a process or usage deficiency.
Technical Contribution to Development
- Take ownership of backlog items end-to-end: coding, testing, review, integration, CI, etc.
- Contribute to the maintenance of deployed software.
- Ensure acceptance testing of deliverables.
Execution Management and Coordination
- Facilitate team rituals: backlog reviews, sprints, progress meetings, and demo reviews.
- Ensure the availability of business and technical stakeholders to resolve questions blocking developers.
- Monitor progress and flag deviations; escalate decisions beyond the role’s scope to the Department Manager, including capacity, cross-team priorities, and subcontracting budgets.
- Govern the use of AI assistance in CI/CD and software development: define areas where it provides genuine value and those where human review and verification remain mandatory.
Data Chain Consistency
- Ensure consistency of the cross-functional data model. For example, equipment declared in one software tool must be addressable in another.
- Ensure that the configuration baseline of a mission is captured as native metadata within generated data, as this is essential for subsequent usability and analysis.
- Maintain an end-to-end view of upstream and downstream dependencies and identify changes that could weaken the overall data chain.
Processes, Quality and Traceability
- Formalize CDM processes: data lifecycle, approval workflows, change management, and acceptance criteria.
- Define the verification strategy for tools generating onboard artifacts, such as builders and configuration compilers, where failures may remain silent and propagate downstream.
- Ensure traceability: for a given mission, identify which version of each database, tool, and file was used.
- Manage technical debt and keep it visible within the backlog rather than allowing it to accumulate outside formal tracking.
Capacity Planning and Resourcing
- Define recruitment and subcontracting needs: scope, required skills, capacity, and schedule.
- Raise alerts regarding capacity risks, particularly when critical expertise is concentrated in a single developer (bus factor).
- Maintain a clear and readable workload and capacity plan for the department.
Position Specifics
- Mainly office-based position.
- Regular interaction with other departments and projects.
- Confidentiality level: Normal.