Salary
💰 $120,000 - $140,000 per year
About the role
- The Technical Project Manager (TPM) focused on software development and delivery is responsible for overseeing the end-to-end execution of software projects, ensuring that development processes are efficient, technically sound, and aligned with product requirements. They translate business and product goals into detailed technical plans, working closely with IT and engineering teams to break down features into tasks, define architecture needs, manage dependencies, and ensure adherence to best practices in coding, testing, and integration.
- In systems and software delivery, TPMs are responsible for orchestrating the smooth release of features and applications, from development through staging to production. TPMs plan release schedules, manage version control and rollout strategies, and ensure post-release monitoring is in place for stability and performance. They collaborate with designers, QA, DevOps, and infrastructure teams to enable automated testing, continuous integration, and deployment pipelines are reliable and efficient. Their technicaloversight ensures that software is not only delivered on time but also scalable, secure, and maintainable—bridging execution and engineering excellence with reliable delivery.
- Ensures delivery commitments are met: Projects are delivered on time, within agreed scope, and to defined quality standards, reducing the cost of delays and rework. Stakeholder expectations are consistently met or exceeded through transparent communication and trust-based relationships. Project progress and risks are visible to all relevant parties, enabling informed decision-making and early course correction. Cross-functional alignment reduces conflicting priorities and accelerates delivery of business benefits.
- Drive Clarity and Alignment in project definition and requirements: Proactively partner with business leads to uncover needs and address challenges, transforming vague or fragmented requests. Initiates IT projects aligned to business priorities. New projects are initiated only when they have clear, validated business objectives, ensuring resources are invested in the highest-value opportunities. Project scope, goals, and success criteria are explicitly tied to measurable business benefits, enabling clear success evaluation. Delivery roadmaps and schedules support timely realization of business value, avoiding wasted investment from delays or misalignment.
- Maintains project stability and reduces delivery risk: Risks, dependencies, and blockers are addressed early, preventing costly overruns or quality issues. Formal change management ensures scope changes support business goals without jeopardizing delivery timelines. Project budgets are managed to prevent overspend and optimize return on investment.
- Manages software release cycles to maximize value delivery: Releases are executed with minimal disruption, ensuring business operations remain stable during deployments. Feature updates reach users faster, increasing responsiveness to market and customer needs. Coordinated release planning optimizes development team capacity, avoiding bottlenecks and downtime.
- Delivers high-value, business-driven features: Released features directly address customer and business needs, driving measurable gains in adoption, efficiency, revenue, or satisfaction. Prioritization ensures that the most impactful initiatives are delivered first, maximizing business benefit from available resources.
- Safeguards quality to protect business outcomes: Delivered solutions meet acceptance criteria and technical standards, reducing post-release defects and operational disruptions. Testing coverage ensures reliability, reducing the risk of outages, lost revenue, or reputational damage.
- Drives and supports continuous improvement to increase future delivery speed and quality: Process and tooling improvements result in faster delivery cycles and higher code quality over time. Adoption of engineering best practices increases maintainability, reduces defects, and lowers long-term technical debt. Teams are more productive and engaged due to streamlined workflows and fewer delivery obstacles
Requirements
- Bachelor’s degree in Computer Science, Business Management, Information Management Systems, or a related field (or equivalent experience).
- 5+ years of experience in an IT or Software Development Project or hybrid cross-functional role (BA/QA/PM) within a software development environment.
- Expert understanding and approach to applying best practices in Agile, Waterfall, hybrid and other project management methodologies
- Proven experience working in early-stage or fast-evolving teams; comfortable in environments with evolving roles and nascent processes.
- Experience implementing change and process improvements
- Minimum 5–7 years experience in managing technology projects, preferably within complex or enterprise environments.
- At least 3 years in a leadership or team lead role, managing technology teams
- Proven track record in prioritization frameworks, risk management, and facilitating cross-functional decision-making.
- Relevant professional certifications such as CBAP (Certified Business Analysis Professional), PMI-PBA (Professional in Business Analysis), or Agile certifications are highly desirable.
- PMP (Project Management Professional) — Widely recognized certification that complements BA skills with project leadership and delivery management expertise.
- PRINCE2 Practitioner — Especially relevant in regions or organizations using PRINCE2 methodology for project management.
- Certified ScrumMaster (CSM) — Helps BAs understand Agile Scrum team roles and ceremonies to better collaborate with development teams