System Analyst

Sybilla Technologies designs, builds and operates robotic optical observatories for monitoring objects in space. The company specializes in complete systems and software for automated data acquisition, analysis, and scheduling networks of sensors. They work in the domains of Space Situational Awareness, Space Surveillance and Tracking, Space Traffic Management, stellar and planetary research, education, and commercial on-demand observations.

• Higher education in engineering, astronomy, astrophysics, computer science, physics, mathematics, or related STEM fields.
• Proficiency in English enabling effective communication and writing of technical documentation.
• Proven experience in system analysis or requirements engineering across the full project lifecycle (pre-contract through delivery).
• Ability to write, review, and evolve requirements including translating high-level mission needs into technical specifications and managing baselines and change requests.
• Knowledge of system engineering standards and norms.
• Experience with requirements, quality gates, traceability matrices, and requirement management tools (Jira, Doors, Polarion, or similar).
• Basic technical awareness to assess requirement feasibility before escalating to architecture.

Nice to have:

• Domain knowledge in Space or adjacent industries (aerospace, defense, Earth observation).
• System engineering standards certification.

• Tender review and mission analysis - assessing fit with existing capabilities, flagging gaps and risks.
• Providing commercial team with technical briefs and feasibility notes for contract negotiations.
• Writing requirements from scratch (SRS/SRD) following system engineering conventions and quality rules.
• Reviewing and improving client-provided requirements (SRS/SRD/SoW) against quality criteria.
• Translating high-level mission needs into structured technical specifications (performance, functional, constraint, interface, verification requirements).
• Maintaining requirements as scope evolves - baselines, change requests, impact analysis.
• Client and internal stakeholder engagement - eliciting needs from external clients and internal departments (e.g., SNO as internal client).
• Basic feasibility assessment - flagging unrealistic requirements; final validation by Architecture & Design.
• System context modelling (e.g. C4).
• Requirements quality gate - approve/reject before development baseline.
• Traceability matrix ownership — stakeholder needs through requirements to verification.
• Feeding validated requirements into the product roadmap via the Product Manager.