Technical Program Manager at Cambridge Technology · Hyderabad · 11 - 20 years · ₹25L - ₹40L / yr · Profitable · Posted 9 May 2023
Java
NodeJS (Node.js)
Python
Android Development
iOS App DevelopmentWe are looking for a Technical Program Manager with at least 12 years of experience managing the planning, execution, and delivery of complex technical projects or programs. You will ensure that technical projects are completed within agreed-upon timelines, budgets, and quality standards, and shall play a critical role in ensuring the successful delivery of complex technical projects and programs.
No of Positions 1
Skills Required
- 12+ years experience with development background and excellent communication skills
- Should have strong project management and people skills along with technology skills (primarily web based application development, but can be any)
- Program Planning: Define the scope and objectives of the program and develop a detailed project plan, including schedules, budgets, and resource requirements.
- Risk Management: Manage program risks, develops mitigation plans, and communicates risk status to stakeholders.
- Stakeholder Management: Work closely with stakeholders to ensure that program objectives are aligned with business goals and objectives.
- Communication: Communicate program status, risks, and issues to stakeholders and senior management.
- Project Management: Manage the day-to-day \ activities of the project team, ensuring that tasks are completed on time and within budget.
- Quality Assurance: Ensure that the program meets the required quality standards.
- Resource Management: Manage program resources, including staffing, budget, and equipment.
- Change Management: Manage changes to the program scope, schedule, and budget and ensures that stakeholders are informed and aligned with the changes.
- Technical Expertise: You will have the strong technical expertise to understand the technical aspects of the program and provide guidance to the project team.
- Continuous Improvement: Continuously monitor and evaluate program performance and identify opportunities for improvement.
- Collaboration: Collaborate effectively with cross-functional teams, including software engineers, product managers, and other stakeholders. You must be able to build and maintain strong relationships with team members and stakeholders to ensure the project's success.
Roles & Responsibilities:
- Supervise, plan, and manage the stages of product development, approving the product at each stage.
- For maximum efficiency, create detailed project plans at each stage of product development.
- Maintain a steady flow of ideas and solutions during product development initiatives in order to introduce innovation and improve operational efficiency.
- Keep track of key metrics and create reports to communicate development progress to senior management, product managers, and cross-functional stakeholders.
- Work with a variety of teams, such as software architects, software engineers, system engineers, developers, and product teams.
- Determine cross-team dependencies and include them in the program planning process.
- Determine how to solve technical problems by diagnosing them and suggesting potential solutions.
- Ensure that product development and delivery can be completed within the product budget and timeframe.
- Oversee the product deployment process and, if necessary, assist with the integration process.
- Make necessary changes to product development processes based on performance metrics.
- Stay current on the latest developments in our product category and industry.
- Ensure complete compliance with industry standards by documenting all processes and adjusting them as needed.
- Manage project escalations and assist in the formation of project teams as needed.
- Maintain and implement project plans within the organization necessary technical programs to assist product management teams.
Experience: 12+Years
Location: Hyderabad
Shubham Vishwakarma
Full Stack Developer - Averlon
Similar jobs (3)
ROLE SUMMARY:
In this role, you will be responsible for supporting people, technical processes, and engineering execution to ensure projects are delivered as per scope, budget, and timelines.
This role includes developing detailed project plans and comprehensive technical documentation, managing project Engineers and their availability, measuring engineering performance, tracking progress, and communicating project status to clients and internal stakeholders. You will work directly with Solutions Architects, Tech Leads, and Engineering teams to evaluate technical trade-offs, drive system design feasibility, and unblock engineering bottlenecks.
You will be a reliable and crucial team member who can anticipate client needs and translate complex technical requirements into actionable project milestones.
As a Technical Project Manager, you will be the point of contact for all stakeholders from initiation to closure and will be responsible for leading the technical delivery team to achieve project objectives. You will work towards balancing technical constraints, technical debt, and Engineer availability on the project. You will report project status to client and internal stakeholders, escalate technical and operational issues as needed, and perform risk management to identify and mitigate architectural and delivery risks while maintaining strong advocacy within your spheres of influence.
QUALIFICATIONS:
Technical Project Manager with 7+ years experience: Including minimum 3 years of IT (Mobile/Web) project management experience and a prior background as a Software Engineer, Tech Lead, or Developer.
Strong expertise in Agile methodologies (Scrum/Kanban).
Must have handled end-to-end SDLC projects as a Technical Project Manager or Scrum Master.
WHAT WILL YOU NEED TO BE SUCCESSFUL IN THIS ROLE?
Handle a portfolio of technical projects and clients in parallel and across geographies.
Develop an execution plan for projects, release schedules, CI/CD milestones, and team allocation.
Partner with technical leads to review high-level system designs, break down complex requirements into epics and user stories, and challenge technical estimates effectively.
Maintain strong relationships with product delivery, engineering leads, sales teams, clients, and account managers.
Expertise in project estimation, planning, tracking, scope control, technical risk and issues management, as well as engineering status reporting.
GOOD TO HAVE:
Hands-on or architecture exposure to.NET/Java/AWS/Azure or microservices architectures.
PMP / PMI-ACP / CSM (Certified ScrumMaster) certification.
Jira/Confluence project management tools expertise, Git workflows, and strong working knowledge of Microsoft Office.
COMPETENCIES:
Strong commitment to professional client service and engineering excellence.
Excellent communication (written, verbal, and presentation), persuasive, and negotiating skills—with the ability to bridge technical and non-technical stakeholders.
Encourage, motivate, and mentor team members on agile practices and technical ownership.
Proactive can-do and technical problem-solving approach to the job.
Regards
Strong Technical Project Manager Profile with hands-on delivery ownership and technical depth
2
Mandatory (Experience 1): Must have 8+ years of experience, including 4+ years leading cross-functional software product delivery across multiple medium-sized companies
3
Mandatory (Experience 2): Must have proven experience delivering software projects from concept through production in a service-delivery environment within a mid-sized organisation.
4
Mandatory (Experience 3): Must have strong experience with Agile/Scrum, estimation techniques, release planning, and end-to-end project execution — including release readiness, production rollouts, rollback planning, hypercare, and customer acceptance.
5
Mandatory (Experience 4): Must have experience managing multiple workstreams, cross-team dependencies, and stakeholders in fast-paced environments, and building/managing project teams from initiation to delivery.
6
Mandatory (Experience 5): Must have experience with integrations (REST APIs, IdP, payment gateways, CRM, ERP, POS) and familiarity with CI/CD, cloud (AWS/Azure/GCP), and the deployment lifecycle
7
Mandatory (Experience 6): Must have experience working with global customers (US/EU) in a customer-facing delivery role, with international exposure.
8
Mandatory (Tech skill 1): Must have a high-level understanding of backend systems, REST APIs, and microservices architecture (Node.js exposure preferred), plus system design principles (scalability, reliability, fault tolerance, performance).
9
Mandatory (Tech skill 2): Must be able to participate in architecture discussions, review technical proposals, evaluate trade-offs, and constructively challenge engineering decisions.
10
Mandatory (AI): Must have experience using AI tools (e.g. Claude, GitHub Copilot) to improve delivery productivity.
11
Mandatory (Communication): Must have excellent written and verbal communication with engineering teams, business stakeholders, customers, and leadership.
12
Mandatory (Company): Must come from a mid-level service company.
13
Mandatory (Certification): Must have PMP and/or CSM certification.
14
Mandatory (Education): Must have a BE/MS in Computer Science or a related field
15
Preferred (Background): Development background earlier in career (QA / mobile / web developer who moved into TPM); ability to create SRS/RFP; business-analysis capability.
Technical Project Manager.
Run delivery for 15–25 backend, frontend, and AI engineers building construction
tech and CAD drawing-automation software — with structural engineers on one
side of you and the codebase on the other.
FULL-TIME
MANAGER · 7+ YRS
Engineering — Delivery & Program Management
TEAM YOU’LL RUN
15–25 engineers · Backend · Frontend · AI
LOCATION
India
EXPERIENCE
6–7 yrs min · 4+ yrs managing engineers
WORK MODE
Hybrid
DOMAIN
ENGAGEMENT
AEC · CAD / BIM automation · Multi-tenant SaaS
About BuildTwin
BuildTwin is a multi-tenant SaaS platform that runs the day-to-day operations of construction
and infrastructure companies — their workforce, projects, commercials, and documents — on a
single system. Alongside it we build an AI drawing-automation platform that turns structured
element data into production-ready technical drawings and exports them to PDF and DXF.
Both products are built by a small, senior engineering group in India: backend engineers on an
AWS serverless platform, frontend engineers on Angular and React, and AI engineers working
on drawing generation and data extraction. Sitting next to them — not in another building, not
in another timezone — are the structural and detailing engineers who define what a correct
drawing actually is.
That adjacency is our biggest advantage and our hardest coordination problem. This role exists
to make it work.
Role overview
We are hiring one Technical Project Manager to own delivery across our engineering teams in
Bengaluru. You will run 15–25 engineers across backend, frontend, and AI workstreams, and
you will be the person who turns requirements originating with our structural and detailing
engineers into scoped, sequenced, shipped software.
This is a technical role. You will not be handed a groomed backlog and asked to move cards
across it. You will sit in the design discussion and have a view on how and when — you will
push back on an approach that will not scale, ask why a trade-off was made, and know the
difference between a two-day change and a two-sprint one. You are not expected to write
production code. You are expected to read it, understand the system, and never be the least
informed person in a technical conversation you are chairing.
The centre of gravity of this job is the floor, not the calendar. Most of your day is
spent with the people building and the people specifying — closing the gap between what a
domain expert means and what an engineer can implement deterministically. Status
reporting is a by-product of doing that well, not the job itself.
What you’ll own.
Delivery ownership
Own the end-to-end delivery plan for every active workstream — scope, sequence,
dependencies, capacity, and dates that actually hold.
Break large, ambiguous product intent into engineering-sized increments with explicit
acceptance criteria, agreed with the people who will build them.
Run the operating cadence: planning, standups, refinement, demos, and retrospectives that
change something the following week.
Maintain one honest view of status — on track, at risk, slipped, and why — visible to the
founders and to the team at the same time.
Manage cross-team dependencies between backend, frontend, AI, and drawing-automation
workstreams so no team idles waiting on another.
Surface risk early, quantify it, and arrive with options — never an escalation without a
proposal.
Protect the team from thrash: absorb changing priorities, re-plan properly, and say no or not
now when a plan cannot take more.
Drive releases to genuinely done — QA, UAT with domain experts, documentation, and post
release verification included.
Own and improve the delivery metrics that matter: cycle time, predictability of committed
scope, defect escape rate, and rework.
Run the release calendar across two products so neither becomes the permanent second
priority.
Technical partnership
Participate substantively in technical discussions on design, sequencing, and trade-offs —
and hold your own with senior engineers.
Understand the architecture well enough to reason about blast radius: what a schema
change touches, why a migration is risky, why an API contract must be agreed before two
teams start.
Challenge estimates that look wrong in either direction, and recognise when an estimate is
uncertain because the problem is still unclear.
Translate technical constraints into decisions leadership can act on, and business constraints
into direction engineers can act on.
Keep testing, observability, and debt-reduction work on the plan instead of losing to features
every single quarter.
Insist that decisions get written down — architecture choices, drawing rules, API contracts,
and the reasoning behind each.
Stay close to the artefacts: read the tickets, the design docs, the PR titles, and the incident
write-ups.
Chair technical discussions where the outcome is a decision with an owner and a date, not a
longer discussion.
Follow CutshortShubham Vishwakarma
Full Stack Developer - Averlon