Technical Project Coordinator

Dispatch Integration

9d•Remote

About The Position

You will help our delivery teams run work well — across everything from defined client projects to ongoing managed services engagements to our internal IP and product initiatives. You'll own the work, or be paired with a leader who owns the technical direction and the client relationship or product, and your job is to keep plans on track, track the numbers that show whether an engagement is healthy, prepare time and budget reports, run the cadence, and make sure nothing falls between the cracks. This is a hands-on coordination role in a genuinely technical environment. It is the entry point into our delivery management career track, and we're looking for someone at the start of their career who wants to build something here.

Requirements

A technical foundation — a degree or equivalent in computer science, engineering, information systems, or data; or 1–2 years in a hands-on technical role
Evidence you finish things: a completed project, a shipped side project, a role you held to the end, a commitment you kept under pressure
Strong written communication — much of this role is clear, brief, well-timed writing
Comfort with collaboration and tracking tools, and willingness to learn our clients' tools as well as our own
Genuine curiosity about how businesses actually run, and how data and systems move inside them
You're technical, or you're becoming technical. You need to be able to follow a conversation about why an integration failed, write a backlog item an engineer doesn't have to rewrite, and know when something you're being told sounds wrong. A software, data, or engineering background is what we have in mind.
You're conscientious in a way other people can rely on. This means you finish what you start, you notice when something has gone quiet, you keep records accurate when nobody is checking, and you follow through without being chased.
You're comfortable being the person who says the uncomfortable thing. Telling a senior colleague that the thing they committed to hasn't happened is a real part of this job. So is asking an engineer to explain something for the third time.
You want to build a career in delivery, not just pass through. This is a coordination role, not an engineering role.

Nice To Haves

Any exposure to integration, automation, or data platforms — Workday, Workato, Snowflake, Databricks, or iPaaS tooling of any kind
Coordination, service desk, or operations experience in a technology environment
Familiarity with agile ways of working
CAPM or equivalent, or working toward some project management certification
Experience in, or exposure to, a certified or regulated environment (ISO 27001, SOC 2)

Responsibilities

Keeping the cadence: scheduling, preparing materials, recording decisions, and following up on actions for team sessions, governance reviews, and quarterly business reviews.
Maintaining plans, backlogs, and actions: This includes maintaining the plan, RAID log, and project tasks for project work. For backlog-driven engagements, it involves ensuring items are properly described, duplicates are merged, stale items are surfaced for decision, and intake criteria are applied.
Making the work visible: Tracking and reporting engagement health measures, such as milestones and burn on projects.
Time and budget administration: Preparing time records and budget-versus-actual reporting for review and approval.
Documentation and access discipline: Maintaining engagement documentation and keeping access lists current.
Client coordination: Coordinating schedules, following up on blockers, and confirming agreements with clients.