Program Manager

techkraftinc
Apply Now ↗
📍 Kathmandu, NepalFull time
IT Services

About this role

Role Purpose

The Program Manager is responsible for ensuring that Techkraft’s engineering organization delivers commitments predictably, transparently, and with appropriate engineering discipline. This role sits at the intersection of engineering leadership, execution management, client/stakeholder coordination, and operational governance. The Program Manager reports directly to the Director of Engineering and works closely with the Staff Engineer to translate engineering priorities into well-structured, measurable, and consistently executed delivery. The role does not own technical architecture or engineering decisions. Technical direction remains with the Staff Engineer and relevant engineering leads. Instead, the Program Manager owns the system through which engineering work is planned, coordinated, tracked, escalated, communicated, and delivered.

 

Key Responsibilities

1.     Engineering Delivery Ownership
  • Own end-to-end delivery governance for assigned engineering teams and projects.
  • Translate strategic priorities into structured delivery plans, milestones, dependencies, and measurable outcomes.
  • Ensure engineering commitments have clear scope, ownership, timelines, acceptance criteria, and dependencies.
  • Maintain visibility into whether initiatives are on-track, at-risk, blocked, or off-track.
  • Identify delivery risks early and drive appropriate escalation and resolution.
  • Ensure teams close the loop between planning, execution, review, and retrospective.

2.     Engineering Planning & Execution

Work with the Staff Engineer and engineering leads to:

  • Establish realistic engineering plans based on technical complexity and team capacity.
  • Coordinate sprint and iteration planning.
  • Maintain visibility into engineering capacity and competing priorities.
  • Identify cross-team dependencies.
  • Track milestones and critical-path items.
  • Ensure blockers are surfaced quickly.
  • Prevent unplanned work from silently disrupting committed delivery.
  • Facilitate trade-off discussions when scope, capacity, quality, and deadlines conflict.
The Delivery Manager is responsible for the integrity of the delivery plan, while technical estimates and implementation decisions remain engineeringowned.

3.     Delivery Predictability

Establish and continuously improve metrics such as:

  • Planned vs. completed work
  • Milestone predictability
  • Cycle time
  • Lead time
  • Work-in-progress
  • Blocked work
  • Delivery variance
  • Defect/rework trends
  • Release frequency
  • Capacity allocation
  • Dependency aging
Metrics should be used to identify systemic problems and improve engineering effectiveness—not to micromanage individual engineers.

4.     Risk & Dependency Management

Maintain visibility across:

  • Technical dependencies
  • External/client dependencies
  • Infrastructure dependencies
  • Security and compliance dependencies
  • Staffing and capacity constraints
  • Third-party/vendor dependencies
  • Scope changes
  • Critical delivery assumptions
Maintain an appropriate RAID framework — Risks, Assumptions, Issues, and Dependencies — for significant initiatives.Escalate risks based on business impact rather than waiting until delivery dates have already been missed.

5.     Engineering Governance

Establish lightweight but consistent engineering delivery governance across teams.

Ensure that appropriate checkpoints exist for:

  • Requirements readiness
  • Technical design readiness
  • Security considerations
  • Infrastructure readiness
  • Testing and QA
  • Release readiness
  • Operational handover
  • Documentation
  • Post-release review
Governance should increase confidence without creating unnecessary bureaucracy.

6.     Stakeholder Communication

Act as the primary source of delivery visibility for engineering initiatives. Provide leadership and relevant stakeholders with concise communication covering:

  • Current status
  • Progress against milestones
  • Key accomplishments
  • Upcoming milestones
  • Risks
  • Blockers
  • Dependencies
  • Decisions required
  • Changes to scope or timeline
Ensure that leadership learns about problems before they become surprises.

7.     Client Delivery Coordination

For client-facing engineering engagements:

  • Maintain alignment between engineering commitments and client expectations.
  • Participate in appropriate client delivery discussions.
  • Coordinate delivery schedules and dependencies.
  • Surface scope changes and risks.
  • Ensure commitments communicated externally have engineering validation.
  • Maintain clear boundaries between committed scope and additional requests.
  • Support change-control processes where necessary.
The Program Manager must never commit engineering timelines or scope without appropriate technical validation.

8.     Continuous Improvement

Identify recurring delivery problems across teams and drive systemic improvements.

Examples include:

  • Poor estimation
  • Excessive work-in-progress
  • Requirement ambiguity
  • Slow technical decisions
  • Cross-team dependency bottlenecks
  • Release friction
  • Environment instability
  • Excessive rework
  • Ineffective ceremonies
  • Lack of ownership
  • Poor stakeholder communication
Facilitate retrospectives and ensure significant improvement actions are actually implemented.

Partnership With the Staff Engineer
  • Delivery planning
  • Execution governance
  • Milestone management
  • Delivery risk management
  • Dependency coordination
  • Capacity visibility
  • Stakeholder communication
  • Delivery metrics
  • Escalation
  • Process improvement

Required Experience
  • 5+ years of experience in software delivery, engineering program management, technical project management, or similar roles.
  • Experience working directly with software engineering teams.
  • Strong understanding of modern software development and SDLC practices.
  • Experience with Agile/Scrum/Kanban or similar iterative delivery models.
  • Demonstrated experience managing dependencies, delivery risks, and crossfunctional initiatives.
  • Experience communicating with senior stakeholders and clients.
  • Ability to understand technical discussions sufficiently to identify delivery implications without attempting to replace engineering leadership.
  • Experience working in software services, consulting, or client delivery environments.
  • Experience coordinating multiple engineering teams simultaneously.
  • Familiarity with cloud infrastructure, DevOps, SRE, cybersecurity, or data engineering environments.
  • Experience operating in environments with security, privacy, or compliance requirements.
  • Familiarity with engineering metrics and frameworks such as DORA, Flow Metrics, or similar approaches.


Frequently Asked Questions

Is the salary disclosed for the Program Manager position at techkraftinc?
The salary for this Program Manager role at techkraftinc is not publicly listed. Click "Apply Now" to learn more about the compensation package on their official careers page.
Where is the Program Manager position at techkraftinc located?
This Program Manager role at techkraftinc is based in Kathmandu, Nepal. The position is listed as on-site or hybrid. Check the full job description or apply directly to confirm the work arrangement.
Is the Program Manager role at techkraftinc full-time or part-time?
This is listed as a Full time position. It is posted as a Program Manager role at techkraftinc.
How do I apply for the Program Manager position at techkraftinc?
Click the "Apply Now" button on this page. You will be redirected to techkraftinc's official application portal hosted on zohorecruit where you can submit your application directly.
When was the Program Manager job at techkraftinc posted?
This Program Manager position at techkraftinc was posted on Aug 21, 2026. Apply as soon as possible — early applications are often reviewed first.
Program Manager
techkraftinc
Apply for this role ↗

You'll be redirected to techkraftinc's official application page on zohorecruit.