2. Main Responsibilities
2.1 Project Planning and Scope
1. Work with the CTO and product or business owners to understand goals, scope and constraints for each project.
2. Break high level requirements into clear, deliverable work items with the technical team.
3. Build and maintain realistic project plans, release plans and timelines.
2.2 Agile Delivery and Jira Management
4. Set up and manage projects and boards in Jira for each team or stream.
5. Organize and facilitate Agile ceremonies, for example planning, daily stand ups, reviews and retrospectives.
6. Keep the backlog clean, prioritised and up to date with the product or business owner.
7. Track progress in Jira, remove blockers and keep the team focused on the current sprint goals.
2.3 Coordination across SaaS platform and integrations
8. Coordinate work across a multi tenant SaaS platform, making sure changes do not negatively impact existing tenants.
9. Manage dependencies and integration work with third party APIs such as WhatsApp, Meta, Shopify and similar tools.
10. Work with engineering leads to plan and track API related tasks, versioning and rollouts.
2.4 Collaboration with Design and Delivery Teams
11. Coordinate work across development, QA, UI or UX design and any external vendors.
12. Work closely with the UI or UX Designer to manage design handovers, ensure designs are understood and confirm that implemented features match agreed designs.
13. Capture decisions, changes and action items and make sure they are reflected in Jira and project documentation.
2.5 Risk, Issue and Dependency Management
14. Identify risks and dependencies early and propose mitigation options.
15. Escalate issues that impact scope, timeline or quality in a structured way, with options and recommendations.
16. Help balance priorities when there are conflicts between projects, stakeholders or teams.
2.6 Quality, Handover and Closure
17. Work with QA and technical leads to define what "done" means for features and releases.
18. Ensure proper handover of deliverables to operations, support or clients when projects or releases go live.
19. Close projects formally, capture lessons learned and share them with the team.
2.7 Continuous Improvement
20. Use retrospectives and data from Jira to improve planning accuracy and team workflows.
21. Suggest improvements in processes, documentation and communication that support faster and more predictable delivery.
3. Key Performance Indicators
22. Delivery against agreed scope and timelines for projects and releases.
23. Predictability of sprints and releases, for example planned work vs completed work.
24. Number and impact of unmanaged risks or issues affecting deadlines or quality.
25. Stakeholder satisfaction with visibility, communication and project outcomes.
26. Team feedback on the clarity and usefulness of planning and coordination.
Requirements
4.1 Experience
27. 4 to 6 years of experience in project management in technology, software or digital products.
28. At least 2 years working in Agile environments with cross functional teams.
29. Hands on experience using Jira to manage projects, backlogs and sprints.
30. Experience in SaaS or startup environments is preferred, not mandatory.
4.2 Skills
31. Strong organisational skills and the ability to manage multiple projects at the same time.
32. Clear and concise communication, written and verbal, with both technical and non technical audiences.
33. Good understanding of Agile concepts such as backlog, sprint, user story, velocity and basic metrics.
34. Ability to read and interpret project data from Jira and other tools and use it to support decisions.
35. Basic understanding of the software development lifecycle and API concepts so that discussions with engineers are grounded.
4.3 Mindset and Behaviour
36. Ownership mindset. Focused on outcomes, not only on activities.
37. Calm under pressure, able to keep structure when priorities compete or change.
38. Practical problem solver, brings options instead of only highlighting problems.
39. Collaborative, respects the time of engineers, designers and other team members and keeps meetings purposeful and short.