Project Manager

JLOOP • Full-time • Remote (Long Beach, CA, US) • $90,000 - $110,000 / year • 3d ago

IMPORTANT: Must live inSouthern California. This is a hybrid role and requires visiting the JLOOP HQ in Long Beach, CA
1 to 4 days per month. Unfortunately, we cannot entertain any candidates who do not reside in Southern California.

-

The Project Manager is the engine of execution discipline across JLOOP Enterprise. This role owns the how and when of all projects: resource allocation, scheduling, milestone tracking, task management, and delivery velocity. The PM takes clearly defined scope from a JLOOP Producer and turns it into an executable plan with named owners, committed timelines, deadlines, and zero ambiguity about who is doing what and by when.

This role reports to their assigned Producer(s) and exists so that the Producer can speak to project status with confidence without chasing individual contributors (IC’s). The PM does not define scope, own the client relationship, or make architectural decisions.

Ideal Candidate Traits

A project management influencer, NOT a dictator.
Trained, experienced project manager.
Fluent in PM delivery systems.
Rigorous, relentless, detail-obsessed. Independent and does not need to be micro-managed.
Experienced in managing shared resources across multiple concurrent projects in a tech/software/design agency environment.

Requirements

Core Accountabilities1. Execution Planning & Resource Allocation

Translates Producer-defined scope into sprint plans, task breakdowns, and resource assignments.
Owns capacity planning across JLOOP Enterprise: knows who is available, who is overloaded, and what trade-offs exist before they become problems.
Assigns work to specific team members based on pre-defined skill set, availability, and project priority. No work starts unassigned.

The PM turns defined scope into executable schedules.

2. Delivery Tracking & Accountability

Owns Project Management Platform (ie. Asana, Jira, or equivalent) hygiene, ticket quality, sprint tracking, and burndown reporting.
Tracks every active task against its deadline. Knows at all times what is on track, what is slipping, and why.
Enforces the self-reinforcing loop: if the Producer has not documented clear requirements, the PM does not schedule the work. No ambiguity enters the pipeline.

The PM is the reason things get done on time or the first person to know they won’t.

3. Rollups & Status Reporting

Delivers structured rollups to the Producer on a predictable cadence; the Producer should never have to chase for status.
Maintains a current risk register. Flags blockers, dependencies, and capacity conflicts before they cause delays.
Always ready to provide visibility and transparency any time a JLOOP stakeholder or executive makes a request.

The PM gives the Producer and leadership a reliable, honest picture of execution reality.

4. Dependency & Cross-Project Coordination

Manages dependencies across concurrent projects and shared resources.
The PM owns the coordination layer.
Coordinates QA cycles, testing handoffs, and release timing with the Technical Leader and engineering team.
Runs or supports sprint ceremonies: standups, planning, retros.
The PM keeps teams and IC’s on time and deliveries on track with predefined deadlines.

The PM prevents one project from silently starving another.

5. Process Introduction & Continuous Improvement

Stands up project management infrastructure if/when/where none currently exists — PM platform configurations, sprint cadences, status templates, definitions of done, etc.
Introduces discipline as a core value to the business.
Identifies process gaps and proposes improvements. Tracks what’s working and what isn’t. Iterates.

The PM builds the engine while running it.

Success Indicators