Technical Project Manager
Job description
About the role
You own the delivery of modernization programs that move production systems into operation and retire legacy workloads.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
This outcome serves the customer engagement by ensuring that production changes happen on schedule.
Delivery timelines stay on track while scope, budget, and sprint execution remain managed through direct ownership of the plan. The purpose of this duty is to keep customer engagements on their committed dates.
Agent platforms compress repetitive engineering work so that project timelines shorten and delivery accelerates.
Personal problem solving removes blockers and drives escalations to closure so that risks never reach the client as a surprise. Each escalation is handled directly by you to protect the client from unexpected delays.
Daily, sprint, and client cadences align engineering and business stakeholders while keeping expectations consistent across all time zones. Consistent expectations support the engagement by reducing confusion about dates and responsibilities.
Requirements
You own delivery outcomes for scope, timeline, budget, and sprint execution on customer engagements with committed dates in writing. This requirement ensures that delivery ownership is clear from the start of the engagement.
A slipping date is your problem to resolve, not a status-report line item that waits for notice. You must treat schedule variance as your own problem to fix.
You run the full cadence of ceremonies and drive delivery outcomes instead of only facilitating conversations that lack resolution. Ceremonies must lead to concrete delivery actions.
You escalate and resolve issues to closure without forwarding messages between the client and engineering teams to avoid delays. Direct resolution keeps the engagement on track.
You carry ownership across distributed teams located in India and three US time zones to ensure coordination does not fall behind. Distributed collaboration requires your active ownership.
Practical notes
This role requires delivery ownership with committed dates across distributed teams in multiple locations. You must remove blockers and drive escalations directly instead of coordinating reports that do not solve problems. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Modernization programs use agent platforms to automate repetitive work and compress timelines. Engineering teams rely on tools that handle repetitive tasks so project work focuses on outcomes. Distributed collaboration across multiple time zones is a core part of how this role operates.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Mactores is the agent-native AWS modernization firm. We ship AWS modernization to production in weeks, data platforms migrated, legacy applications and databases refactored, AI agents running against real data, for mid-market and lower-enterprise companies in financial services, healthcare and life sciences, internet and software, manufacturing, and TMEGS.