Project Manager, Business Systems & Technology Analysis

Mactores is the agent-native AWS modernization firm. Most modernization work doesn't ship, it stalls in pilots, slips a year, or lands at three times the budget. We exist to ship it: production systems running, legacy retired, outcomes measured. Our delivery is built on Aedeon, the agent platform built by Mactores' founders' sister company, which absorbs the repetitive 60–70% of engagement work, discovery, dependency mapping, validation, test generation, that traditional consulting bills human hours against.

Forward-deployed engineers own the rest: architecture, judgment, and cutover, on dates we commit to in the contract.

We put delivery dates in contracts and carry the overage risk ourselves. That only works if someone owns the delivery-scope, timeline, budget, and sprint execution and treats a slipping date as their problem, not a status-report line item. That someone is you.

As our Project Manager, you'll run distributed engineering teams across India and three US time zones on customer engagements where the date is committed. You'll run the daily, sprint, and client cadences, translate fluently between engineering and business stakeholders, and push back on scope creep with data. Agents compress the repetitive engineering work, which makes delivery faster and makes your job sharper: shorter timelines leave no room for blockers that sit in a log for days.

We're looking for the PM who gets things done who personally removes blockers, drives escalations to closure, and makes sure no risk reaches the client as a surprise.

This role is not for you if:

• Your default is to forward messages between the client and engineering.
• Your role has primarily been reporting and coordination without delivery ownership.
• You've only facilitated agile ceremonies without driving delivery outcomes.
• Sprint ownership and execution were largely driven by a Business Analyst or Product Owner in your previous roles.

• Build the project plan in Smartsheet from the Solutions Architect's scope of work, real dependencies, a defensible critical path, sprint boundaries overlaid on the timeline.
• Track scope, hours, and budget in real time. Flag burn-rate risk early and push back on scope creep with numbers, not gut feel.
• Maintain a live risk register. Spot risks before they become issues, surface the right ones to the client at the right time, and drive mitigation actively.
• Maintain a live RAID log (Risks, Assumptions, Issues, Dependencies) and an action tracker with clear ownership, accountability, and timely closure.
• Run crisp daily stand-ups, sprint planning, and retrospectives that produce decisions, not discussions.
• Remove sprint blockers personally. Chase the client-side data dependency, escalated stuck cloud permission, redirect pulled resources don't let "waiting on" sit in a log for days.
• Handle sprint-level risks in real time: reprioritize, descope, swap stories, or upscale before commitments slip.
• Keep trackers honest. Action items have owners and dates; delays are visible and followed up on time.
• Translate technical progress into business language for the customer, and business priorities into clear, estimable requirements for engineers.
• Facilitate internal and external architecture reviews across India and three US time zones; document decisions and circulate them the same day.
• Produce weekly customer status updates a senior business leader can absorb in 90 seconds — RAG colors backed by evidence, not sentiment.
• Own customer escalations and drive them to resolution. Communicate status, risks, and decisions needed — proactively, not reactively.
• Onboard engineers on customer systems, scope, process, deliverables, and documentation standards.
• Create kick-off presentations, project charters, and tracking…