Technical Project Lead

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.

Job Summary

We are seeking a highly motivated Technical Product Manager with strong exposure to software development to drive product strategy, roadmap execution, and cross-functional collaboration. The ideal candidate will bridge the gap between business stakeholders and engineering teams, ensuring delivery of scalable, high-quality software products.

Key Responsibilities.

prior exposure to Software Development.

Collaborate closely with engineering, design, QA, and business teams to deliver end-to-end product solutions.

Translate business requirements into technical specifications and user stories.

Work with development teams to ensure timely delivery of features and releases.

Prioritize product backlog based on business value, customer needs, and technical feasibility.

Participate in Agile/Scrum ceremonies such as sprint planning, stand-ups, and retrospectives.

Analyze product performance and user feedback to drive continuous improvement.

Ensure product scalability, performance, and technical feasibility.

Coordinate with stakeholders for product launches and go-to-market strategies.

• Maintain product documentation including PRDs, technical documents, and release notes.

Required Skills

Strong understanding of software development lifecycle (SDLC).

Hands-on experience or exposure to programming languages (Python preferred most )

Experience working with Agile/Scrum methodologies.

Strong knowledge of APIs, microservices, and system design concepts.

Ability to work closely with engineering teams and understand technical challenges.

Excellent analytical, problem-solving, and communication skills.

• Experience with product management tools (JIRA, Confluence, etc.).

Job Title: Technical Delivery lead – Full stack

Experience:

·       12+ years overall

·       5+ years as Technical Delivery lead

Position Summary

We are looking for an experienced Technical Delivery Lead with 12+ years of software development experience to lead the design, development, integration, deployment, and support of enterprise digital solutions. The ideal candidate should have strong hands-on technical expertise and be capable of actively contributing to development by designing and implementing complex features, integrations, and critical business functionalities while leading the cross-function team.

Key Responsibilities

Technical Leadership

·      Lead end-to-end application delivery from requirements gathering through production deployment.

·      Define solution architecture, technical standards, and development best practices.

·      Conduct design reviews, code reviews, and technical discussions.

·      Mentor development teams and provide technical guidance.

·      Collaborate with business stakeholders, architects, product owners, and project managers.

Hands-on Development

·      Actively participate in application development and contribute code for complex and critical features.

·      Design and implement scalable solutions for high-priority business requirements.

·      Lead troubleshooting and resolution of complex technical and production issues.

·      Review and optimize application performance, security, and scalability.

·      Support development teams in resolving technical blockers and challenges.

Required Technical Skills

·      Sitecore XP/XM

·      OutSystems

·      Node.js, .NET Core, ASP.NET MVC, C#, Java

·      React.js, JavaScript, TypeScript

·      REST APIs, Microservices Architecture

·      SQL Server, Oracle, MySQL

·      Azure/AWS, CI/CD, Docker, Jenkins, Git

Candidate Profile

·      12+ years of software development experience.

·      5+ years of experience as Technical Delivery Lead or Solution Lead.

·      Strong hands-on coding experience with the ability to independently deliver complex technical solutions.

·      Experience leading Agile teams and managing end-to-end delivery.

·      Excellent stakeholder management and communication skills.

Key Phrase

Hands-on Technical delivery Lead who is expected to contribute 30-40% of the time in coding based on the availability, solution implementation, code reviews, and complex technical problem-solving.

Supercharge Your Career as a Technical Project Manager at Technoidentity!

At Technoidentity, we're a Data & AI product engineering company with over 15 years of expertise in building durable digital products, intelligent enterprise solutions, and scalable Data & AI platforms. As we continue expanding globally, it's the perfect time to join our team of tech innovators and make a lasting impact.

What’s in it for You?

We are looking for a seasoned, techno-functional Project Manager who can own end-to-end delivery for multiple projects while building and growing a high-performing team of 15–18 people. This is a hands-on project management role that blends three dimensions: delivery excellence (on-time, first-time-right, within scope and cost), customer partnership (building trusted relationships and delivering measurable business impact), and people leadership (developing, upskilling, and growing your team).

The ideal candidate is equally comfortable in a technical design discussion, a customer QBR, and a career conversation with a team member.

What Will You Be Doing?

Key Responsibilities

1. Delivery Execution & Ownership

• Own end-to-end delivery of projects/releases — on-time, first-time-right, and within the agreed cost, timeline, and scope.
• Drive project and release planning, including work breakdown, estimation, resource planning, dependency mapping, and risk-adjusted scheduling.
• Track and manage scope changes with disciplined change control; balance customer asks against commercial and timeline commitments.
• Proactively identify delivery risks and drive mitigation before they become escalations.

2. Quality & Continuous Improvement

• Define, track, and report quality metrics (defect density, leakage, first-time-right rate, SLA adherence, velocity/predictability).
• Institutionalize first-time-right practices: reviews, definition of done, test coverage, and release readiness gates.
• Drive continuous improvement through retrospectives, root-cause analysis, and measurable corrective actions carried into subsequent releases.

3. Customer & Stakeholder Management

• Build and deepen relationships with customer stakeholders at working and leadership levels; act as a trusted delivery partner, not just a status reporter.
• Own the cadence of customer communication — Weekly Status Reports (WSR), Monthly Business Reviews (MBR), and Quarterly Business Reviews (QBR) — with crisp, data-backed narratives on progress, risks, and value delivered.
• Build deep business and domain knowledge of the customer and the projects under the client portfolio; use that context to anticipate needs, shape solutions, and identify growth opportunities.
• Manage expectations transparently — communicate early on risks, trade-offs, and course corrections.

4. Governance, Reporting & Delivery Standards

• Ensure adherence to organizational delivery standards, processes, and governance frameworks across all projects.
• Maintain rigorous delivery hygiene: minutes of meetings, action-item tracking to closure, and up-to-date RAID logs (Risks, Assumptions, Issues, Dependencies).
• Provide accurate and timely internal reporting — project health, margins, utilization, staffing, and escalations — to delivery leadership.
• Work in synergy with support functions (HR, Talent Acquisition, Finance, IT, Operations) for staffing, invoicing, compliance, and enablement needs.

5. People Leadership & Development

• Manage, mentor, and grow a team of 15–18 engineers and leads — spanning goal setting, regular 1:1s, performance management, and career development conversations.
• Build individual upskill plans aligned to project needs and career aspirations; track progress and create stretch opportunities.
• Develop a leadership pipeline by identifying and grooming leads and anchors within the team.
• Foster a culture of customer-first, ownership, accountability, and continuous learning; manage performance issues early, fairly, and constructively.
• Drive team engagement, retention, and recognition.

6. Techno-Functional Contribution

• Participate credibly in solution and architecture discussions; challenge estimates and technical approaches where needed.
• Translate business requirements into technical direction for the team, and technical constraints into business language for the customer.
• Stay current with engineering practices (Agile/Scrum, DevOps, CI/CD, cloud, and AI-assisted development) and drive their adoption where they improve delivery outcomes.

Requirements

What Makes You the Perfect Fit?

• 8–10 years of overall experience in IT services, with at least 3–4 years managing delivery and teams of 12+ members.
• Strong techno-functional profile: an engineering background with hands-on technical experience earlier in the career, now combined with delivery and domain depth.
• Proven track record of on-time, within-budget delivery across multiple releases or projects.
• Demonstrated experience running customer governance cadences (WSR/MBR/QBR) and managing senior client stakeholders.
• Solid command of estimation techniques, release planning, quality metrics, and delivery governance artifacts (RAID logs, MoM, action trackers, status dashboards).
• Experience with Agile/Scrum and hybrid delivery models; working knowledge of tools such as Jira, Azure DevOps, or equivalent.
• Strong people-management credentials: performance management, upskilling, career development, and conflict resolution.
• Excellent written and verbal communication — able to produce crisp executive-level reporting and lead difficult conversations with confidence and empathy.

Good to Have

• PMP, PRINCE2, CSM/PSM certification.
• Exposure to AI-assisted delivery practices and productivity tooling.
• Domain exposure (e.g., energy/utilities, real estate, or public sector).
• Experience contributing to presales, account growth, or delivery excellence initiatives.

Education

• Bachelor's degree in Engineering / Computer Science or equivalent; MBA or equivalent management qualification is a plus.

About the role

You'll join a growing engineering team as a Lead Engineer / Architect, leading a small team in India and working closely with engineering teams in the US and Mexico. You'll be responsible for driving technical execution, solving complex engineering problems, and leading a team to build, deliver, and maintain reliable software.

This is a hands-on leadership role for someone with strong backend engineering expertise who can also contribute across the stack when needed.

Location: Hyderabad

Work Mode: Hybrid

What you'll do

• Lead a small engineering team in India, driving day-to-day technical execution and delivery
• Work closely with teams in the US and Mexico to plan, develop, and deliver software
• Design and build robust, scalable backend systems using .NET
• Own technical decisions around architecture, implementation, and engineering best practices
• Contribute across the full stack when needed.
• Break down complex technical problems and drive them through to implementation and delivery
• Mentor engineers and help maintain a high standard of engineering quality
• Collaborate with distributed teams and communicate technical decisions clearly

What we're looking for

• 8+ years of software engineering experience, with experience in a lead-level role
• 2+ years of experience leading a team
• Strong, hands-on expertise in .NET and backend engineering
• Strong understanding of software architecture and scalable backend systems
• Full-stack experience is preferred, with React being a plus
• Experience leading a small engineering team and driving technical delivery
• Excellent communication skills, particularly when working with distributed teams
• Strong problem-solving skills and a hands-on approach to engineering
• AI expertise is a plus
• Experience with payment systems or payment-related products is a plus

Who you are

• You take ownership and drive work through to completion
• You're hands-on and enjoy solving challenging engineering problems
• You're curious, resourceful, and always looking to learn
• You communicate clearly and work well with teams across different locations
• You lead by example and help the team deliver high-quality work

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. Must have Hands-on familiarity with AutoCAD, Revit or experience at a product company in the CAD / AutoCAD / BIM / PLM / EDA /simulation space

Role overview-

We are hiring one Technical Product 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

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.

The floor & the team.

Our requirements do not come from a product spec written in a vacuum. They come from structural and detailing engineers sitting on the floor with decades of practice behind them. Converting that into software is the defining skill of this job.

• Partner with structural and detailing engineers to turn drawing standards, project practice, and domain expectation into unambiguous, implementable requirements
• Run requirement sessions whose output is a written spec — sample data, expected output,edge cases, and explicit non-goals — not a shared verbal understanding.
• Arbitrate the constant gap between “how it has always been done on site” and “what can be deterministically automated.”
• Set up validation loops so domain experts review generated output early and repeatedly, rather than at the end of a sprint.
• Maintain a decision log for domain rules so the same question is not re-litigated three sprints later by different people.
• Manage internal stakeholder expectations and, where relevant, commitments made to customers.
• Spot when a “small clarification” is actually a scope change, and handle it as one.
• Make sure engineers get access to the domain expert directly — your job is to structure that contact, not to become a relay in the middle of it.

Challenges you’ll solve.

We prefer to be candid. These are the problems that make this role genuinely difficult — and genuinely interesting.

Domain knowledge that arrives as tribal knowledge

Our structural and detailing engineers know what a correct drawing looks like, but much of that knowledge is tacit. Your job is to extract it into deterministic, testable rules before an engineer starts building. Getting this wrong is the single most expensive failure mode we have

— it produces work that looks finished and is not.

Three disciplines, one release

Backend (AWS serverless), frontend (Angular / React), and AI engineers ship into the same

product. They have different failure modes, different testing regimes, and different natural cadences. Sequencing them so nobody idles and nothing integrates late is the core scheduling problem here.

Correctness is not negotiable

This is construction software. A wrong drawing, a wrong quantity, a wrong permission, or a wrong payroll figure has consequences outside the screen. “Ship it and iterate” has limits here, and you will need judgement about exactly where those limits sit for each workstream.

AI workstreams do not estimate like CRUD

Drawing generation and extraction work is research-shaped: some weeks produce a breakthrough, some produce a negative result. You will plan around that uncertainty honestly— with timeboxes, decision points, and fallbacks — instead of pretending an unknown is a two-

week ticket.

Live customers, finite engineers

Companies run their operations on this platform daily. Production incidents, customer escalations, and enterprise integrations (Asite, Autodesk Construction Cloud) compete with roadmap work for exactly the same people. You will make that trade-off explicitly, every week,

and be able to defend it.

Two products, one organisation

The operations platform and the drawing-automation platform have different customers, different rhythms, and partly shared people. Keeping both moving — without either becoming the perpetual second priority — is a standing constraint on every plan you make.

Founder-adjacent, fast-changing priorities

Direction can change on new customer information, and sometimes it should. You are the shock absorber: re-plan quickly, communicate the change clearly and once, and make sure the team experiences it as a decision rather than as chaos.

Qualifications.

• 6–7 years minimum in software delivery, including at least 4 years directly managing engineering teams as a project, delivery, or engineering program manager.
• Proven experience running teams of 10+ engineers across more than one discipline —backend, frontend, mobile, data, or AI.
• Fluency in modern delivery practice — Agile / Scrum or Kanban applied with judgement rather than ceremony — plus genuine facility with Jira or Linear, Git workflows, CI/CD, and release management.

Strongly preferred

• Experience at a product company in the CAD / AutoCAD / BIM / PLM / EDA /simulation space — Autodesk, Bentley, Dassault, Siemens, PTC, Trimble, Hexagon, Ansys or similar.
• Exposure to AEC, construction tech, manufacturing, or industrial software where domain correctness matters more than interface polish.
• Experience managing teams that included AI / ML engineers alongside conventional product engineers.
• Hands-on familiarity with AutoCAD, Revit, Civil 3D, Tekla, or DXF / drawing-export workflows.

The bar, the process, the offer.

The manager we’re looking for

Technical enough to be trusted

Engineers respect the questions you ask, not just the dates you set.

Owns outcomes, not activity

Measures the job by what shipped and worked, not by how busy the board looked.

Direct and specific

Says the uncomfortable thing early, in plain language, to the person who needs to hear it.

Reduces chaos

Leaves every process, plan, and handoff simpler than they found it.

Holds opinions loosely

Strong views on how to run delivery, updated when the evidence changes.

Raises the standard around them

The team becomes more predictable and more capable because you are in it.