Technical Project Manager (Hands-On / BA-Heavy)

Company: NavigAid
Location: US-based, Remote (must work EST hours)
Type: B2B SaaS

About NavigAid

NavigAid is a fast-moving B2B SaaS company building technology for complex eligibility and application workflows.
We are scaling quickly—and right now, engineering time is being lost to unclear requirements, overthinking, and unnecessary complexity.
This role exists to fix that.

The Role (Read This Carefully)

This is not a traditional PM role. You are not here to run ceremonies or write long, exhaustive specs.
You are here to:
Create clarity quickly
Ensure requirements are correct and buildable
Keep engineers moving without confusion or rework
You sit at the center of product, business, and engineering and turn vague ideas into clear, well-scoped, execution-ready work.
If you prefer long planning cycles, exhaustive documentation, or waiting for perfect clarity before moving forward—this is not the role.

What Success Looks Like

Engineers can start work confidently without guessing
Requirements go from idea → clear enough for development without rework in hours, not days
Tickets are concise but complete—logic and key edge cases are covered, without unnecessary detail
The team consistently ships MVP, not overbuilt features
You cut scope where needed to protect delivery speed
You resolve blockers quickly and directly, without relying on heavy process or excessive meetings
Jira is always clean, prioritized, and ready for execution

Core Responsibilities

Turn vague business ideas into clear, well-scoped user stories and acceptance criteria
Own requirements end-to-end—you are the source of clarity for engineering
Balance speed and accuracy: move quickly, while ensuring requirements are clear enough to avoid rework
Resolve ambiguity in real time (hours, not days) through decisive thinking and targeted collaboration
Own Jira: ticket creation, backlog grooming, prioritization, and dev readiness
Keep engineers moving by removing ambiguity and blockers immediately
Push back on over-engineering and unnecessary complexity
Maintain lightweight, execution-focused documentation (no bloat)

What This Role Is NOT

Not a Scrum Master role
Not a meeting-heavy coordination role
Not a “perfect spec before execution” role
Not a documentation-heavy or process-driven role

Requirements

Proven experience in B2B SaaS as a Technical PM, Business Analyst, or Product Ops
Demonstrated ability to create clear, dev-ready requirements efficiently
Strong Jira ownership (tickets, backlog, prioritization, readiness)
Ability to work with strong engineers and keep them focused and shipping
Comfortable making decisions with incomplete information
Strong judgment in balancing clarity, speed, and scope

Huge Plus

Experience with Medicaid applications, eligibility workflows, or gov-adjacent systems

Why This Role

High ownership, high impact
You directly influence team velocity, clarity, and delivery quality
You solve one of the biggest problems in product teams: unclear requirements and overbuilding