Project Manager

GEMBA CONCEPTS · TECHNOLOGY DIVISION

 · JOB DESCRIPTION

Technical Delivery Manager – Services LOCATION Bengaluru (Hybrid) ABOUT GEMBA CONCEPTS EXPERIENCE 5–8 years REPORTS TO Chief Technology Officer TYPE Full-time Gemba Concepts helps manufacturers and enterprises improve how their operations run. Our technology division builds and runs Gemba Connect, a suite of enterprise SaaS products spanning warehouse management, logistics, ERP, and applied AI/ML, deployed across 30+ active client accounts in manufacturing, pharma, FMCG and retail.

ABOUT THE ROLE

We're looking for a technical leader to own Gemba's services business end to end: delivery, people, commercials and reporting. You'll run every client implementation and custom development engagement, build and manage the team that delivers them, and be the single point of accountability to clients and leadership for how services perform. You've written production Java code, can read a Spring Boot service and a SQL execution plan, and have since hired, reviewed and led delivery teams. The product roadmap stays with product leadership; everything we deliver to clients runs through you.

WHAT YOU'LL OWN Services business ownership

• Own the health of the services portfolio: delivery, client satisfaction, billing milestones and account growth.

• Run post-sale SOW execution. Ensure milestones are hit and billed on time, and follow up with finance and clients on receivables.

• Grow accounts by converting change requests and enhancements into scoped, priced, billable work.

• Track effort, utilisation and margin by account; act when an engagement turns unprofitable. Delivery

• Run multiple concurrent client implementations, owning scope, timeline, cost and quality.

• Plan and run sprints with Tech Leads: grooming, estimation, capacity planning, reviews and retros.

• Own go-lives (UAT, cutover, data migration, hypercare) and post-go-live support SLAs.

• Maintain RAID logs and delivery dashboards; flag risk early, with a proposed fix. Requirements and change control

• Be the single intake point between consulting teams, clients and engineering; convert requirements into user stories with testable acceptance criteria.

• Baseline scope and run a formal change-request process. Every change is priced in effort, cost and date before it's accepted.

• Make sure what's agreed is documented before it's built. People and hiring • Plan services headcount against the delivery pipeline and run hiring end to end (role definition, interviews, closing) at a high bar.

• Run goal-setting, regular 1:1s and performance reviews for the services team; give input on promotions, compensation and performance plans.

• Grow Tech Leads and senior engineers into people who can own accounts independently.

• Own team retention and morale. Know who's at risk before they resign. Gemba Concepts · Technology Division Page 1GEMBA CONCEPTS · TECHNICAL DELIVERY MANAGER – SERVICES Reporting

• Publish monthly services MIS to leadership: revenue billed, collections, on-time delivery, SLA adherence, utilisation, hiring and attrition.

• Contribute the services section to quarterly board reporting.

• Run monthly or quarterly business reviews with key client stakeholders. Technical oversight

• Work with Tech Leads on design reviews, integrations (ERP, WMS, third-party systems) and non-functional requirements.

• Lead incident triage and root-cause reviews on client escalations; track corrective actions to closure.

• Coordinate with DevOps on environments, CI/CD and release windows.

• Uphold security and compliance controls (e.g., SOC 2) across delivery. Improving how we deliver

• Drive adoption of AI-assisted development and testing tools, and measure whether they actually raise throughput per engineer.

• Tighten estimation accuracy, definition of done and release discipline across the services team. MUST-HAVES

• 5–8 years in software, including 2+ years as a hands-on Java developer and 2+ years in delivery or project management.

• 1+ year leading a team of 5+ directly, including hiring and performance reviews.

• Strong working knowledge of Java and Spring Boot. You can review a PR, understand how a service is structured, and challenge an estimate.

• Solid SQL: schema design, writing and debugging queries, and understanding of indexing, transactions and production issues such as slow queries and connection pool exhaustion (SQL Server/Azure SQL, PostgreSQL or MySQL).

• Hands-on exposure to cloud platforms (Azure preferred, AWS/GCP acceptable).

• Working experience with the commercial side of client engagements: SOWs, milestone billing and change orders. Margin tracking is a plus.

• Track record of delivering enterprise B2B software to external clients across multiple parallel engagements.

• Proficiency with Jira or Azure DevOps, Confluence and Git-based workflows.

• Clear communication. You can present to a client CXO, write a board-ready MIS, and give an engineer hard feedback. GOOD TO HAVE

• Domain experience in manufacturing, supply chain, warehousing, logistics or ERP.

• Background in an IT services firm or the services arm of a product company.

• Familiarity with microservices, REST API design and message queues.

• Experience delivering AI/ML features.

• Exposure to SOC 2 or ISO 27001 audits.

• Certifications (PMP, CSM, PMI-ACP) are welcome but won't substitute for a delivery and team-building track record. WHAT SUCCESS LOOKS LIKE IN YOUR FIRST 6 MONTHS

• 85%+ of implementations go live on the committed date.

• Billing milestones are invoiced on time, and receivables ageing is visibly down. • Every active account has baselined scope, a live RAID log and a change log.

• Services hiring is on plan, with near-zero regretted attrition.

• Leadership gets a monthly services MIS without having to chase it. WHO YOU'LL WORK WITH The services delivery team (engineers, Tech Leads, BAs, QA), product squads, DevOps, consulting teams, finance and client stakeholders.

WHY JOIN Own a real business line with direct access to leadership. Build the team and operating model your way. Work on enterprise products in active growth, including applied AI.

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.

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.