Director of Product

At SupplyHouse.com, we value every individual team member and cultivate a community where people come first. Led by our core values of Generosity, Respect, Innovation, Teamwork, and GRIT, we’re dedicated to maintaining a supportive work environment that celebrates diversity and empowers everyone to reach their full potential. As an industry-leading e-commerce company specializing in HVAC, plumbing, heating, and electrical supplies since 2004, we strive to foster growth while providing the best possible experience for our customers.

We are looking for a Director of Product to own our product operating model end to end: the practice of product management, the delivery engine that gets work shipped, and the annual roadmap that connects both to company strategy. Reporting into our COO, this individual will lead a team of Product Managers embedded in cross-functional pods and hold those pods accountable for measurable customer and business outcomes. The Director of Product will work in close partnership with the VP of IT, Senior Manager of UX, Director of Enterprise AI Adoption, and business leaders to connect customer needs, business priorities, technical strategy, and execution. If you’re passionate about building high-performing product organizations, enjoy turning strategy into action, and are excited to lead cross-functional teams in delivering product experiences that are strategically sound, technically feasible, thoughtfully designed, and impactful for customers and the business, we want to hear from you!

This remote position is open to individuals who live in, or are open to relocating to, the following states: Arizona, Delaware, Florida, Georgia, Kentucky, Nevada, New Jersey, New York, North Carolina, Ohio, Rhode Island, South Carolina, Tennessee, Texas, Virginia, and Washington.

This position requires travel to our headquarters in Melville, NY 6 times per year for internal meetings and team building activities. We reimburse reasonable and necessary travel expenses, and you’re also welcome to work on-site anytime beyond these visits – our doors are always open.

• →Accountability across the pod structure 
  • →Pod ownership. Own outcome accountability for every product pod, ensuring each has a clear mission, a primary success metric, and explicit guardrail metrics.
  • →Decision rights and shared accountability. Establish clear decision rights across Product, UX, and Engineering. Product leads customer problem definition, business outcomes, prioritization, and roadmap decisions; UX leads research and experience design; Engineering leads technical architecture and implementation. Hold each trio jointly accountable for delivering measurable outcomes, with unresolved tradeoffs escalated and decided quickly.
  • →Cross-pod seams. Resolve cross-pod dependencies, sequencing conflicts, and platform-versus-feature tradeoffs before they become delivery risk.
  • →Operating cadence. Define and maintain the standards that make pods legible to leadership: how bets are written, how success is defined up front, how results get reported, and what happens when we need to pivot.
• →Leading and developing product managers
  • →People leadership. Directly manage and coach a team of product managers with clear leveling expectations and honest, specific feedback.
  • →Craft development. Build Product Management craft across discovery and delivery: opportunity framing, jobs-to-be-done and customer problem definition, hypothesis writing, experiment design, and evidence-based prioritization.
  • →Hiring. Recruit, onboard, and retain strong product talent. Own the hiring bar and the interview loop for the function.
  • →Influence without authority. Coach Product Managers to lead through influence across Merchandising, Marketing, Operations, Customer Service, and Engineering without relying on formal authority.
• →Managing to outcomes, not outputs
  • →Outcome definition. Translate company strategy into a product strategy with a north star metric and a supporting metric tree, so every pod can trace its work to a business result.
  • →Measurement. Replace feature-count reporting with outcome reporting: leading and lagging indicators, target versus actual, and a clear read on what we learned.
  • →Continuous discovery. Partner with the Director of Customer Experience to establish a consistent customer research and usability practice across product teams, validate bets before they consume significant engineering capacity, and stop or pivot work that is not moving the intended metric.
  • →Evidence-based prioritization. Ensure prioritization reflects qualitative customer insight, behavioral data, business performance, and operational feedback rather than stakeholder preference alone.
  • →Customer proximity. Build direct exposure to professional tradespeople and internal users into the product management operating model.
  • →Portfolio balance. Manage capacity as a portfolio of bets across core growth, platform health, and exploratory work, and be able to defend that allocation to the executive team.
• →Roadmap ownership
  • →Annual roadmap. Build and publish the annual product roadmap, then maintain it as a living now / next / later view rather than a fixed feature calendar with dates attached to everything.
  • →Quarterly planning. Run the quarterly planning process: OKR setting, bet selection, capacity modeling, and tradeoff decisions with clear rationale.
  • →Executive alignment. Keep the roadmap credible with senior leadership and the board through clear, unhedged communication about what is committed, what is a bet, and what changed.
  • →Backlog health. Maintain a rigorously prioritized backlog with a real definition of ready and definition of done, so pods are never blocked on ambiguity.
• →Project management and delivery
  • →Integrated planning. Ensure significant initiatives have clear scope, milestones, owners, dependencies, resource assumptions, risks, decision points, and launch criteria.
  • →Risk management. Establish a consistent process for identifying, escalating, and resolving delivery risks before they affect committed outcomes or timelines.
  • →Delivery accountability. Hold product managers accountable for maintaining clear plans, decisions, status reporting, and stakeholder alignment from discovery through post-launch evaluation.
  • →Cross-functional execution. Coordinate dependencies across Product, IT, UX, AI Enterprise Enablement, Marketing, Merchandising, Operations, Customer Service, and other impacted teams.
  • →Commitment discipline. Differentiate committed work from discovery, experiments, and potential future investments so leadership has an accurate view of delivery confidence.
  • →Change management and adoption. Ensure significant product launches include stakeholder communication, training, operational readiness, adoption planning, and feedback mechanisms. Hold product teams accountable for sustained adoption and value realization, not only technical release.
  • →Post-launch accountability. Require adoption, performance, customer feedback, operational impact, and lessons learned to be reviewed after launch.
  • →Delivery health. Measure and improve delivery health through indicators such as cycle time, throughput, and predictability.
  • →Process stewardship. Improve the tools and operating rhythms that make delivery visible, while removing process that does not improve decisions, accountability, or execution.
• →Technical product leadership
  • →Partner with the VP of IT and engineering leaders to align the product roadmap with technical strategy, architecture, capacity, security, reliability, scalability, and platform health.
  • →Ensure product managers can translate business and customer needs into requirements that account for system dependencies, integrations, data flows, APIs, and nonfunctional requirements.
  • →Evaluate build, buy, and partner options using customer value, business impact, technical feasibility, implementation risk, total cost, and long-term maintainability.
  • →Balance customer-facing enhancements with platform modernization, technical debt reduction, system reliability, and foundational capabilities.
  • →Ensure technical constraints and dependencies are surfaced early enough to inform prioritization, sequencing, and executive decisions.
  • →Establish strong partnership between product managers and technical leads without expecting product managers to dictate engineering solutions.
• →AI-enabled product strategy
  • →Partner closely with the Director of AI Enterprise Enablement to identify, evaluate, and prioritize AI opportunities across customer-facing products and internal workflows.
  • →Translate validated AI opportunities into product roadmaps with clear users, business outcomes, success measures, data requirements, and adoption plans.
  • →Ensure AI-enabled product decisions consider usability, data quality, security, responsible-use expectations, technical feasibility, and ongoing performance.
  • →Distinguish between experimentation and scalable production capabilities, with clear criteria for piloting, measuring, expanding, or discontinuing AI solutions.
  • →Promote reuse of enterprise AI capabilities and prevent fragmented tools or duplicative solutions from developing across product teams.
• →Data and analytics
  • →Product measurement. Establish the analytics, instrumentation, and reporting needed to evaluate product adoption, customer behavior, operational impact, and business results.
  • →Measurement readiness. Partner with data and technical teams to ensure product decisions are based on reliable information and that measurement requirements are defined before launch. 

Additional Details: 

• Remote employees are expected to work in a distraction-free environment. Personal devices, background noise, and other distractions should be kept to a minimum to avoid disrupting virtual meetings or business operations.
• Applicants must be currently authorized to work in the U.S. on a full-time basis. SupplyHouse.com will not sponsor applicants for work visas.
• SupplyHouse.com is an Equal Opportunity Employer. We welcome and encourage individuals of all backgrounds, experiences, and perspectives to apply. Employment decisions are based on qualifications, merit, and business needs.
• To ensure fairness and trust in our hiring process, we ask that all application materials, assessments, and interview responses reflect your own thinking and perspective. You may use AI tools to assist in preparing your responses, as long as this use is clearly disclosed and you can speak authentically to your ideas and work. Our focus is on honesty, judgment, and how you approach problem-solving. We appreciate your transparency and look forward to learning more about your skills.
• We are committed to providing a safe and secure work environment and conduct thorough background checks on all potential employees in accordance with applicable laws and regulations.
• All emails from the SupplyHouse team will only be sent from an @supplyhouse.com email address. Please exercise caution if you receive an email from an alternate domain.