About the role
Complex programs fail on communication long before they fail on technology. You'll run multi-team programs with calm, clear communication, honest status and a firm grip on risks and dependencies.
You'll work with executives, engineers and vendors, keeping everyone pointed at the same outcome.
Your team
You'll partner with engagement leads and senior engineers, with a delivery practice that shares templates and playbooks.
The impact you'll have
Predictable delivery
Plans that hold up, and early warning when they won't.
Aligned stakeholders
Everyone knows what is happening, what is at risk and what is needed.
Stronger teams
Lightweight practices teams keep after you leave.
What you'll do
- Plan and run multi-workstream technology programs
- Manage risks, dependencies, budgets and stakeholders
- Report status with honesty and clarity
- Coach teams on delivery practices
A typical week might include
- Cross-team dependency sync
- Updating risk register and forecasts
- Steering committee preparation
- Unblocking a vendor issue
Technical scope and expected depth
The areas this role may cover. The exact environment and priorities are agreed for each engagement.
Program structure
Translate strategic intent into a program charter, outcomes, workstreams, accountable owners, and delivery boundaries. Identify decisions that require executive sponsorship.
Dependencies and sequencing
Map technical and organizational dependencies, critical paths, integration points, and external commitments. Replan explicitly when assumptions change.
Risk and escalation
Maintain a usable risk, issue, assumption, and dependency register. Present options, recommended action, decision deadline, and consequence of inaction.
Delivery governance
Design working forums and reporting that help teams make decisions. Balance milestone commitments with evidence from actual engineering progress.
Launch and operational readiness
Coordinate testing, rollout, support, change communication, incident coverage, and acceptance criteria across affected teams.
Stakeholder communication
Prepare concise executive updates and detailed working artifacts suited to each audience. Record decisions and close the loop on actions.
What you'll deliver
Outcome framework
Shared language for what success means, how it will be measured, and what must be true for the outcome to hold.
Integrated delivery plan
Sequenced work, milestones, dependencies, decision gates, capacity assumptions, and credible critical paths.
Risk and decision system
A living view of risks, issues, options, owners, escalations, and decisions that keeps action timely.
Operating cadence
Forums and artifacts that reduce status work while increasing alignment, accountability, and delivery confidence.
What you bring
- 7+ years in technical program or project management
- Track record delivering cloud, data or software programs
- Excellent executive communication
Practical capabilities we will discuss
- Technical fluency
- Explain how architecture choices, environments, security reviews, testing, integrations, and operational readiness affect a delivery plan. You should be able to identify when a milestone hides an unresolved technical dependency.
- Planning judgment
- Discuss how you establish a baseline, track assumptions, forecast under uncertainty, and revise a commitment when evidence changes. Explain how resource constraints affect sequencing.
- Executive communication
- Bring an example of a difficult program decision. Describe the options, tradeoffs, stakeholder concerns, escalation path, and recommendation you presented.
- Delivery evidence
- Walk through a program you owned from planning to outcome. Explain how you handled dependencies, changes, launch readiness, and the transition to ongoing ownership.
Nice to have
- PMP, SAFe or similar
- Prior engineering background
How success is assessed
Success criteria are agreed at the start of the engagement and reviewed as the work progresses. Typical signals include:
- Leaders can make decisions with current information instead of waiting for a status meeting.
- Teams understand priorities, dependencies, ownership, and what is expected next.
- Risks are surfaced with options and recommendations early enough to change the outcome.
- The program protects delivery focus instead of adding reporting burden without leverage.
- The organization retains a usable operating rhythm after the engagement changes or ends.
Your first 90 days
First 30 days
- Learn the program, teams and stakeholders
- Audit the plan, risks and dependencies
- Set up a clear reporting rhythm
By day 60
- Own planning and status for the program
- Remove top blockers
- Run steering committee updates
By day 90
- Improve delivery metrics
- Coach teams on practices
- Prepare the next phase plan
How we work with clients
- Prepare workshops with a clear decision, relevant evidence, and the people needed to act on the outcome.
- Document assumptions, alternatives, costs, dependencies, and risks so stakeholders can review your recommendation.
- Escalate delivery or quality concerns early with options and a recommended course of action.
- Protect confidential information and use approved collaboration and delivery environments.
- Transfer knowledge through pairing, practical documentation, and walkthroughs with the people taking ownership.
Tools you may use
- Jira
- Confluence
- Smartsheet
- Linear
- Notion
- PowerBI dashboards
Interview process
- 01
Apply
Share your background. A human reads every application.
- 02
Intro call
30 minutes on your goals, experience and what you want next.
- 03
Technical conversation
A practical discussion with a practitioner — no trick puzzles.
- Program deep-dive. Walk through a large program you ran, including what went wrong.
- Stakeholder scenario. Handle a conflict between engineering and the business.
- 04
Team & terms
Meet the people you'd work with, then agree scope and terms in writing.
Location, engagement and compensation
This is an expression-of-interest profile for client work we are shaping. A confirmed vacancy, employment arrangement, travel requirements and compensation range have not yet been published. Before an approved role proceeds, we agree client context, availability, duration, compensation or rate and any benefits in writing.
Telugu Technologies is an equal opportunity employer. We consider all qualified applicants regardless of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability or veteran status, and provide reasonable accommodations on request — email careers@telugutechnologies.com.