Product Owner/ Manager

• Drive end-to-end delivery across multiple connected tools and partner organizations, coordinating engineering, design, and business stakeholders toward a shared roadmap.
• Manage cross-team and third-party dependencies, integration points, and release/installer cadence so work flows predictably and capacity is never idle.
• Run a single, transparent decision-intake process with stakeholders - batching decisions, securing approvals and data/test assets, and maintaining a decision log with clear turnaround expectations.
• Identify, track, and mitigate risks; streamline meeting cadence and communication to protect developer focus time.
• Define and report delivery KPIs (throughput, cycle time, backlog and defect age, dependency/unblock latency) and use them to drive continuous improvement.

Product ownership (embedded)

• Own and continuously prioritize a single product backlog spanning multiple tools, balancing new features, enhancements, technical health, and defects.
• Translate business objectives into build-ready user stories, requirements, and acceptance criteria, enforcing a clear “definition of ready.”
• Set and defend product scope to prevent scope creep, and facilitate agile development, refinement, and reviews.

Minimum Education Required: High School diploma and higher Interview Process: Interview with team leads, panel with software developers, final interview with Customer Success Manager for the account Top 3 experience “must haves”:

1. Experience as a Product Owner, Product Manager, or Technical Program Manager
2. Experience managing a product backlog
3. Experience working with software developers, * Proven experience as a Technical Program Manager, Technical Product Manager, or Product Owner delivering software in an Agile, multi-stakeholder environment. * Demonstrated ability to coordinate across multiple teams and partner organizations, drive decisions, and remove blockers in ambiguous, fast-moving settings. * Excellent requirement-writing, prioritization, and stakeholder-management skills, with a track record of reducing requirement churn and delivery risk. * Experience with backlog/issue-tracking and program-tracking tools (e.g., Airtable, Jira, Azure DevOps) and Agile delivery practices.

Technical skills & platform fluency

• Ability to engage credibly with developers on Autodesk Revit add-in/plugin development and the Revit API, including the realities of supporting multiple Revit versions.
• Working understanding of the C# / .NET ecosystem (e.g., .NET Framework vs. .NET 8 migrations, Visual Studio solution structure, installer/build releases) and of Python-based scripting and tooling.
• Familiarity with the Autodesk Platform Services (APS/Forge) stack-including Autodesk Construction Cloud (ACC), Forma, and AEC data/model APIs-and the constraints of cloud model access, authentication, and large-file handling.
• Comfort reasoning about cross-tool data contracts and integrations and structured data exchange (CSV/Excel, JSON, parameter mapping), including schema versioning across tools.
• Ability to assess and communicate platform limitations (e.g., Revit/API product constraints) and translate them into pragmatic roadmap decisions and enhancement requests.
• Awareness of usage analytics and adoption-tracking approaches (e.g., telemetry/logging, Google Analytics) to measure ROI and tool adoption.

Industry & domain knowledge

• Background or strong working knowledge of AEC and CAD/BIM workflows; hands-on familiarity with Autodesk Revit and Civil 3D is highly desirable.
• Understanding of data-center physical infrastructure and cabling design-including ISP/OSP, fiber and structured cabling, cable trays/conduits/pathways, rack layouts and elevations, port mapping, BOM/cable schedules, and quantity-of-materials workflows-or a demonstrated ability to ramp quickly in a specialized engineering domain.

Soft skills

• Clear, concise written and verbal communication; able to translate between business stakeholders and technical teams.
• Self-directed and comfortable working autonomously in a contract capacity across distributed teams and time zones.

Duration: 12 Months Hours: Approximately 30 hours per week (6 hours/day) Travel: Limited travel may be required for occasional customer onsite visits. Time Zone: Flexible; team members currently support the account across all U.S. time zones. Working Hours: Candidate should be available for meetings occurring within approximately 9:00 AM - 5:00 PM ET, with flexibility outside of scheduled meetings.