A complete application in a minute
Tailored resume and cover letter, ready to send.
CloudLinux, the maker of Imunify360, seeks a Product Owner for a small, senior, fully remote squad. You will own the concept pipeline, drive discovery, and deliver MVPs within quarterly windows, while coaching engineers and collaborating with CPO on strategy.
You’ll balance customer conversations, scoping, and hands-on prototyping to validate ideas fast. The role emphasizes leadership in a distributed team, 50% discovery and 50% building, with AI-augmented development and production-ready MVPs
CloudLinux is the maker of Imunify360 — a suite of security products protecting millions of websites across the web hosting industry — and of CloudLinux OS, the operating system behind a large share of the world’s shared hosting. To learn more about our company and products, visit our websites: and . Alongside those established product lines we run a small innovation team whose job is to find and prove the next ones.
We are looking for a Product Owner to lead that team: a small, senior, fully remote squad of engineers that takes new product concepts from idea to a working MVP in customers’ hands, then hands proven products to a product line and moves on to the next concept. You will be accountable for the pipeline of ideas, the speed and rigour with which they are tested, and the evidence behind every go / no-go recommendation.
The innovation team sits across CloudLinux and Imunify and owns the product concepts that do not yet have a home in an established product line. Ideas come from customer conversations, industry events, telemetry across more than 80,000 servers and the CPO’s strategy; the team’s job is to turn them into something a customer will pay for within a quarter, using AI coding agents throughout.
Run the pipeline of product concepts: capture, size and rank ideas with their assumptions written down, and keep the backlog of bets visible to the CPO and leadership.
Take each funded concept to a working MVP on a fixed timebox, typically one quarter, with a named customer or design partner testing it.
Define success criteria up front and report against them with real numbers rather than adjectives: usage, conversion, willingness to pay, support load.
Make the go / no-go call honestly: hand proven products to a product line with a written runbook and roadmap, and capture what was learned from concepts that did not prove out.
Report status and risk to the CPO weekly; every item carries an owner and a due date.
Choose the fastest credible build for each concept — buy, borrow, open source or write — with the trade-offs made explicit.
Build prototypes and demo stands yourself where that is the quickest route to evidence; review designs and code on everything the team ships.
Keep MVPs production-worthy enough to run on real customer servers: packaging, safe rollout, rollback and observability from the first release.
Work with the architecture group and the product teams so a successful MVP can be adopted without a rewrite.
Lead a small distributed team: 1:1s, goal setting, performance reviews, and career development.
Hire: define the profile, run technical interviews, onboard, and mentor engineers.
Set the working agreements that make fast async work possible — written decisions, public‑by‑default communication, demos over status meetings.
We evaluate engineers partly on how effectively they work with coding agents, and in the innovation team this is the main lever on speed. As the lead you model and coach it: prompt specificity, review quality on agent‑generated code, context provision, iteration and error recovery, and end‑to‑end task completion. Expect to use agents to build prototypes, generate test corpora and draft customer‑facing material.
30 days: Complete 1:1s with every team member and produce a written read on the team’s strengths and gaps; review the concepts in flight and the evidence behind each; spend time with sales, support and at least three hosting customers.
60 days: Own the concept pipeline and the weekly status; publish success criteria for every active concept; ship at least one prototype or demo yourself.
90 days: Present a ranked portfolio of bets for the next two quarters agreed with the CPO, including one go / no-go recommendation backed by customer evidence and a staffing recommendation.