Product Manager, Platform & Delivery

We're looking for a Product Manager who can own the full delivery lifecycle of our core platform — from shaping requirements to seeing features shipped and documented. This is a hands-on, high-context role at a lean, fast-moving startup. You'll sit at the center of engineering, leadership, and day-to-day execution, acting as the connective tissue between business direction and technical delivery.

The ideal candidate is process-minded but pragmatic — someone who can bring order to ambiguity without adding bureaucratic drag. You'll be comfortable context-switching frequently, doing light technical work when needed, and pushing the team toward better habits while protecting the delivery pace that makes us effective.

Cubyl is a growing startup building innovative platform solutions for our customers. We move fast, ship often, and operate as a tight-knit team where everyone's work has direct impact. We're based on the East Coast and offer fully remote employment.

• Engineering standup: Run the daily developer standup each morning. Come prepared with a review of overnight Linear updates; field blockers raised during the meeting and action them afterward.
• Leadership sync: Participate in a daily sync with the CEO and Chief of Staff. Deliver a substantive update on engineering progress, surface blockers, and carry forward any directional decisions into tickets or planning artifacts.
• Ticket writing: Create well-scoped Linear tickets for near-term and upcoming work — lightweight but requiring clarity on business intent and technical feasibility.
• Engineering Q&A: Field questions from developers on ticket intent, feature behavior, and expected outcomes. Serve as the primary PM-side resource during active sprints.

• Backlog ownership: Maintain Linear as the system of record for all active and upcoming work. Write tickets proactively, keep priorities current, and model good Linear hygiene — including consistent use of ticket states, naming conventions, and prioritization signals.
• Roadmap communication: Maintain a near-term rolling plan (typically a few upcoming weeks) and communicate it clearly to leadership on request. Format is lightweight — block diagrams or visual artifacts — but should be predictable and proactive rather than purely reactive.

• Release coordination: Establish and own a formal release cycle. Define what “done” means, coordinate across engineering and QA, and ensure features ship with documentation.
• Platform testing: Treat feature testing as a core PM responsibility. Actively test the platform and key features before release rather than delegating QA entirely to engineering.

Interested in remote work opportunities in Product Management? Discover Product Management Remote Jobs featuring exclusive positions from top companies that offer flexible work arrangements.

• Documentation: Require all shipped features to include documentation. Track documentation status in Linear or equivalent, and review developer-submitted docs before sign-off.

• Stakeholder support: Respond to questions and directional requests from the CEO (Ilaria) and COO/Chief of Staff (Kelly). Prepare scope-of-work documents and other ad hoc planning artifacts as needed.
• Technical feasibility: Work closely with the Backend Lead to validate feasibility of product ideas before scoping or build begins. He is the primary source of truth on current technical capabilities.
• Data & PoC support: Engage with data exploration, cleaning, and light proof-of-concept development as needed. Use tooling (such as Google Antigravity, Google’s fork of Cursor) to demonstrate how data can be accessed or surfaced.
• Developer unblocking: Respond to mid-sprint blockers and informal feature walkthroughs from developers. Sign off on work-in-progress and provide feedback before features are considered complete.

• Experience: 1+ years of experience in product management, with meaningful time spent on technical or platform-based products in a startup or fast-moving environment.
• Agile execution: Hands-on experience managing backlogs, writing user stories and acceptance criteria, and running sprint ceremonies without relying on heavy process frameworks.
• Technical acumen: Solid working knowledge of modern web application architecture — including frontend frameworks, backend systems, APIs, and cloud infrastructure — sufficient to scope work, validate feasibility, and engage credibly with engineers.
• Requirements writing: Proven ability to translate business objectives into clear, actionable tickets and specs that allow engineering to execute without constant PM intervention.
• Stakeholder communication: Strong written and verbal communication skills. Comfortable briefing executives, fielding developer questions, and navigating the full spectrum from strategic conversation to in-the-weeds technical discussion.
• Ownership orientation: A demonstrated track record of driving initiatives end-to-end — from definition through delivery — and holding yourself accountable to outcomes, not just outputs.
• Comfort with ambiguity: Ability to operate effectively in a lean, fast-changing environment where not everything is defined, structured, or predictable.

Browse our curated collection of remote jobs across all categories and industries, featuring positions from top companies worldwide.

• AI/ML/LLM experience: Prior work with AI-driven products, including integration of Large Language Models or experience on data-intensive or intelligent systems.
• Startup experience: Firsthand experience in an early-stage company where you wore multiple hats and built processes from scratch.
• Technical background: Previous experience as a software engineer, technical analyst, or in a highly technical individual contributor role.
• Data skills: Comfort with data exploration, cleaning, or light scripting — enough to engage meaningfully with data work without requiring a dedicated data engineer for every task.
• QA experience: Familiarity with formal QA processes and release cycle management, including defining testing criteria and coordinating cross-functional sign-off.

This is not a role where the PM sets strategy from a distance. Expect to be deeply embedded in daily engineering work, context-switching frequently, and operating with a high degree of autonomy. Ad hoc requests are the norm, not the exception — on a heavy day they can consume the full workday.

At the same time, this is a meaningful opportunity to bring structure where there currently isn’t any. The incoming PM will help define what good looks like across our release cycle, Linear hygiene, documentation workflow, and QA process. You’ll have real ownership and visible impact from day one.

Send a short note to hiring@cubyl.com with the subject line “Product Manager, Platform & Delivery”. Tell us:

• Why this company, stage, and role interest you
• CV