Technical Project Manager

Ajaia is an AI implementation consultancy and product studio. We help organizations move from AI experimentation to measurable return on investment across four practices: AI Strategy and Advisory, Workforce Training and Enablement, Process Optimization, and Custom AI Development. Our work sits with executives and the people who do the actual work, and it is judged on whether something changed in production, not on whether a pilot looked good in a deck.

Position Overview
Ajaia is hiring a remote Technical Project Manager to run delivery on client AI builds from kickoff to a system that actually works in production. You will triage the pile of requests that lands on your desk this week, keep a mess of moving parts organized without dropping a thread, and know enough about the code to call out what will not hold up before a client ever sees it. You are not the person who decided what to build. You are the person who makes sure it gets built, on time, on scope, and honestly reported the whole way through.

This is a technical seat with a delivery mandate. You should be able to sit down and build a working automation yourself when that is faster than explaining to someone else what to build. We care far more about what you can build and run than how long you have held a title.

You will run delivery for US clients with a team based in New York. Client calls, standups, and escalations happen on US Eastern time, so this role is built around daily overlap with the US team, not asynchronous handoffs.

Compensation: Competitive, benchmarked to senior delivery roles in your market, plus a performance bonus tied to delivery outcomes. We will share a specific number for your location early in the process.

How we expect you to work
AI use is a core execution requirement at Ajaia, not optional tooling. You will use AI daily to draft status updates, stand up small automations, generate test data, and get a first pass on a code review, then apply your own judgment on top. Project managers at Ajaia write code: a script that cleans up a messy dataset, an automation that wires two systems together. You should be able to do that yourself, and comfortable saying when an AI-generated first draft is wrong.

Staying current on new tools is part of the job, and so is being straight with people: an engineer on a technical risk, a client on a date.

Remote works here when the writing is strong. Status, risks, and decisions get written down where the team and the client can read them, not held until the next call.

What you will do

• Build working automations and scripts yourself when that solves the problem faster than a meeting would.
• Read the code. Call out specifically what will break in production, not just whether the ticket is checked off.
• Keep a lot of moving parts straight at once: the backlog, the risk list, three overlapping deadlines, and whichever client is calling today.
• Triage ruthlessly. A pile of requests lands every week, and deciding what gets worked now and what waits is most of the job.
• Write to clients like a person. Plain, specific, and honest, especially when the news is not great.
• Run client calls and standups on US Eastern time and be reachable during the overlap window when something breaks.
• Own the delivery plan for your engagements end to end: sequencing, dependencies, and the date.
• Unblock technical decisions inside the team, then live with the consequence of the call you made.
• Escalate risks as soon as you see them, not after they have already cost the date.
• Define done for a deliverable before the engineer starts building it, not after they finish.
• Stay on the number after go-live long enough to know whether adoption is real or the dashboard is lying

• Highly organized across many moving parts at once: a backlog, several risks, more than one client.
• Reads code and specs well enough to say what will break in production.
• Builds small automations and scripts to solve problems fast.
• Calm, clear, honest client communication in written and spoken English, especially when the news is bad.
• AI fluent: uses AI daily to draft, build, and check work, and can tell good output from slop.
• Comfortable making priority calls under pressure and owns them.
• Two or more years in technical delivery, program management, or a comparable role.
• Available for at least 7 to 8 hours of daily overlap with US Eastern time (9am to 6pm ET), consistently.
• Reliable internet, a quiet place to take client calls, and your own laptop.
• Legally able to work as an independent contractor or through an employer of record in your country.
• A bachelor's degree is preferred and is not a requirement.

Competitive benefits.