Associate Technical Program Manager

We are seeking a Senior Technical Product Manager with 6+ years of experience to own product strategy and delivery end-to-end. You'll define the roadmap, translate business needs into clear requirements, and drive execution with engineering and design, using technical depth to partner on APIs, integrations, and platform decisions.

Key Responsibilities

• Own and communicate the product roadmap and priorities

• Gather requirements from stakeholders and users; write clear specs

• Partner with engineering and design through agile delivery

• Make data-driven decisions using product analytics

• Balance business goals, user needs, and technical constraints

• Track outcomes and iterate on the product

Mandatory Skills

• 6+ years in product management for technical products

• Roadmap ownership and prioritization

• Strong requirements gathering and user research

• Agile delivery with engineering teams

• Data-driven decision making (analytics)

• Excellent stakeholder communication

Nice to Have: technical background (APIs/architecture); SaaS/platform product experience

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

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.).

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.

About Us

We believe the future of software development is AI-native — where engineers operate at a higher level of abstraction and quality remains non-negotiable. 

Incubyte is a software craft consultancy where the “how” of building software matters as much as the “what”.  

We partner with companies of all sizes, from helping enterprises build, scale, and modernize to early-stage founders bring their ideas to life. 

Our engineers operate in an AI-native development model, using AI as a collaborator across the SDLC to accelerate development while upholding the discipline of software craftsmanship. Guided by Software Craftsmanship and Extreme Programming practices, we build reliable, maintainable, and scalable systems with speed, without compromising quality. If this way of building software resonates with you, we’d like to talk. 

Our Guiding Principles 

These principles define how we work at Incubyte. They are non-negotiable. 

Relentless Pursuit of Quality with Pragmatism 

  We build high-quality systems without losing sight of delivery. 

Extreme Ownership 

  We take responsibility end-to-end for decisions, execution, and outcomes. 

Proactive Collaboration 

  We collaborate closely, challenge each other, and solve problems together. 

Active Pursuit of Mastery 

  We continuously improve our craft and raise our bar. 

Invite, Give, and Act on Feedback 

We seek, give, and act on feedback to get better every day. 

Ensuring Client Success 

We act as trusted partners and focus on real outcomes, not just output. 

Job Description

This is a remote position.

Experience Level

This role is ideal for professionals with a technical/engineering background who have transitioned into program management, client-facing, or pre-sales roles. We're looking for someone who can operate with minimal oversight, thrives in ownership-driven environments, and is equally comfortable in a room with engineers as in a room with clients evaluating a partnership.

What You'll Do as Account Manager

• Manage and drive technical programs from initiation to delivery, ensuring projects are completed on time, within scope, and to a high standard of quality
• Collaborate effectively with engineering, product, and other cross-functional teams to define project requirements, scope, and timelines
• Proactively identify and mitigate risks and dependencies, escalating issues as needed
• Track and communicate project status, progress, and key milestones to stakeholders
• Facilitate clear communication and alignment across teams
• Identify opportunities within existing and prospective client engagements, and pitch Incubyte's value add clearly — going beyond jargon to articulate real business impact
• Build and maintain trust with clients through consistent, high-quality communication and delivery
• Contribute to the continuous improvement of our program management processes

Requirements

What You'll Bring

• A dev background — enough technical depth to understand engineering trade-offs, speak credibly with engineers, and translate technical work into business value
• A strong desire to learn, take ownership, and collaborate effectively
• Excellent communication and interpersonal skills — not just fluency in language, but the ability to communicate at the right level of abstraction and add real value in every conversation
• Prior experience in sales or a client-facing capacity, with a demonstrated ability to identify opportunities and sell — pitching value, not just capability
• Proven ability to manage projects and deliver results
• Strong problem-solving skills and the ability to independently define and execute tasks
• Technical/Engineering background or MBA preferred
• Understanding of Agile methodologies, Scrum, and Sprints is a plus
• Familiarity with tools like Jira and Confluence is a plus
• Comfort working in a high-ownership.

What We Value

• Extreme ownership – you take responsibility for outcomes and drive work end-to-end
• Ability to execute independently and define problems, not just solve assigned tasks
• A strong product mindset – willingness to talk to customers, understand problems deeply, and define direction when needed
• The ability to build trust and sell value, not just deliver output
• High standards, autonomy, and a bias toward action.

Benefits

Life at Incubyte

​

We are a remote-first company with structured flexibility. Teams commit to shared rhythms during core hours, ensuring smooth collaboration while maintaining autonomy. Twice a year, we come together in person for a co-working sprint and once a year for a retreat - with all travel expenses covered. 

Our environment is built for crafters: pairing, refactoring, experimenting with AI, and pushing the boundaries of software excellence. We are all lifelong learners, and our work is our passion. 

​

Perks

• Dedicated learning & development budget. 
• Sponsorship for conference talks. 
• Comprehensive medical & term insurance. 
• Employee-friendly leave policies. 
• Home Office fund 
• Medical Insurance 

About the Role

We are looking for a highly organized and proactive Program Manager to act as the central operational hub for our team at Innovxcare. As we build next-generation AI solutions for radiology, you will lead sprint execution for our Software and AI engineering teams while maintaining tight alignment with our Product Management and Commercial teams to deliver critical releases on schedule.

Location & Work Model

• Location: Whitefield, Bangalore.
• Work Arrangement: Hybrid (4 days on-site, 1 day work-from-home per week).

Key Responsibilities

• Facilitate Agile Ceremonies: Lead all core sprint meetings, including daily standups, sprint planning, retrospectives, and end-of-sprint demos.
• Manage Tech Execution: Oversee daily workflows and task progress for the Software and AI engineering teams to keep deliverables moving smoothly.
• Drive Cross-Functional Alignment: Coordinate continuously with Product and Commercial teams to ensure shared clarity on product timelines and release dates.
• Identify & Mitigate Risks: Proactively flag execution bottlenecks, technical blockers, and potential delays, facilitating immediate solutions.
• Own Team Reporting: Serve as the single source of truth for timelines by maintaining regular progress reports and visibility for the whole company.

What We Are Looking For

• Proven experience in technical program or project management, ideally within a fast-paced startup or healthcare technology environment.
• Strong hands-on experience running Scrum/Agile ceremonies (standups, retros, demos).
• Solid understanding of software development lifecycles (SDLC) and an ability to grasp AI development workflows.
• Exceptional communication skills, capable of bridging technical engineering discussions with commercial and product strategies.
• Proficiency with modern team management and ticketing tools (Jira)

Compensation

• Salary Range: ₹10,00,000 to ₹20,00,000 per annum, commensurate with experience.

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.

Strong Engineering Manager / Lead Profiles

2

Mandatory (Experience 1) – Must have minimum 8+ years of overall Software Engineering / Development experience with a strong IC foundation.

3

Mandatory (Experience 2) – Must have 2+ years of formal Engineering Manager experience with direct people-management responsibility (informal Senior Engineer / Tech Lead experience managing a team does not count)

4

Mandatory (Experience 3) – Must have directly managed 4–6+ engineers, including 1:1s, performance management, growth plans, promotions, mentoring, and team development.

5

Mandatory (Experience 4) – Must own technical direction and delivery for an engineering team/pod, including architecture, system design, code/PR reviews, execution planning, and engineering quality.

6

Mandatory (Experience 5) – Must have strong backend/software engineering experience with hands-on technical depth in building APIs, services, integrations, and scalable systems; specific language/framework can vary.

7

Mandatory (Experience 6) – Must have experience owning production operations, including on-call, incident management, debugging, and postmortems for their area.

8

Mandatory (Experience 7) – Must have experience driving cross-functional alignment with Product and Design and translating ambiguous business/product requirements into scalable technical solutions.

9

Mandatory (Company) – Must be from a Product Company / Startup, particularly B2B SaaS, Fintech, Payments, or similar technology product environments. (Refer Target Company List)

10

Mandatory (Role Fit) – Role is 80% people/team management and 20% technical/IC involvement;

11

Preferred (Education) - Tier 1 engineering college

What you'll do

Own a client end to end. Learn their business, find what to automate or rebuild, and lead the work that ships it.

Turn business problems into technical solutions sit in the call, understand the real problem, design the fix, and decide how it gets built.

Stay hands-on. You'll still write code, build integrations, and work with APIs every day.

Build on whatever the client runs Zoho, Salesforce, Azure, similar platforms, and custom apps where needed.

Run delivery: scope it, sequence it, ship it, support it. The timeline is yours.

Review code and designs. Mentor the developers on your projects and unblock them fast.

Be the escalation point when something breaks or an integration misbehaves.

Own client communication on the technical side status, tradeoffs, bad news, early.

Keep the bar high: clear docs, clear updates, clear commit history.

What we're looking for

4–7 years shipping software, with real depth in REST APIs and system integrations.

Experience leading projects or small teams — the person others check with before they build.

Strong with business platforms (Zoho, Salesforce, or similar). Much of the leverage lives there, not in custom code.

You can sit with a non-technical client, understand the problem, and come back with a working solution.

Still enjoy building. This is technical leadership, not coordination.

Self-driven. You'll often be the senior-most engineer on the account.

Why you'll love this role

Full ownership from first call to delivery — you run projects, not a ticket queue.

Direct access to clients and leadership. Your decisions ship the same week.

Constant variety: new systems, new problems, new builds.

A step into technical leadership without giving up the hands-on work.