Technical Project Manager

AJAIA•New York, NY

11h•$90,000 - $175,000•Onsite

About The Position

Ajaia is hiring a 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.

Requirements

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

Nice To Haves

A GitHub profile or other public evidence of what you have shipped.
Working fluency in Python, SQL, or a no-code tool such as n8n, Zapier, or Make.
Experience on a small consulting or professional services delivery team.
Exposure to a regulated or operationally complex industry such as logistics, healthcare, or financial services.

Responsibilities

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