Head of Product Execution

About SensorFlow

SensorFlow is at the forefront of IoT-driven automation for the hospitality industry. We leverage real-time data and smart control systems to help hotels operate more efficiently, reduce energy consumption, and improve sustainability without compromising guest comfort.

Our platform combines IoT hardware, firmware, and cloud software to manage energy usage across guest rooms and shared spaces in live hotel environments around the world. By turning operational data into actionable control, we help hotel owners, operators, and asset managers generate measurable, auditable financial and environmental outcomes.

The role

We are looking for a Head of Product Execution to work closely with the CEO and engineering leaders to translate a clear product strategy into consistent, high-quality delivery.

This is not a vision-only product role. The strategy and direction are defined. The challenge, and the opportunity, is execution across a complex, full-stack IoT system with real-world constraints.

If you enjoy turning high-level goals into practical plans, aligning teams around priorities, and making sure what ships actually delivers customer value, this role will suit you well.

Your role is to ensure that product work is:

• Well scoped
• Correctly sequenced
• Measurable
• Delivered with a strong understanding of dependencies and risk

What you will be responsible for

You will own product execution end-to-end.

This includes:

• Translating outcome-based strategy into clear product initiatives and delivery plans
• Owning prioritization across multiple workstreams (room-level systems, building-level systems, platform capabilities)
• Working closely with engineering leads to:
  • Define scope and milestones
  • Manage dependencies across firmware, backend, cloud, and frontend systems
  • Make tradeoffs when constraints arise
• Ensuring every major initiative has:
  • A clear success metric
  • An accountable owner
  • An agreed rollback or stop condition
• Maintaining focus as new ideas, requests, or edge cases emerge
• Making execution risks visible early so they can be addressed deliberately

You will be evaluated primarily on whether product work delivers measurable outcomes, not on the volume of features shipped.

Technical expectations

This role requires strong technical understanding, though it is not a hands-on coding role.

You should be comfortable:

• Understanding how firmware, gateways, cloud services, and user-facing applications interact in a full-stack IoT system
• Reasoning about technical tradeoffs, constraints, and dependencies across layers
• Working effectively with engineers to shape feasible solutions and realistic timelines
• Asking the right technical questions to surface risk early

You are not expected to write code, but you are expected to have a solid appreciation of how complex systems are built, deployed, and operated in production environments.

What you will not be responsible for

This role does not require you to:

• Define company vision or long-term strategy
• Own market positioning or fundraising narratives
• Act as a standalone “CEO of Product”
• Introduce heavy process for its own sake

The goal is clarity and momentum, not ceremony.

What success looks like

Success in this role looks like:

• Engineering teams have clear priorities and fewer execution bottlenecks
• Product decisions are made quickly and consistently
• Delivery is predictable and aligned with business outcomes
• The CEO and COO are not day-to-day execution bottlenecks
• It is easy to explain what is working, what is not, and why

The background that fits well

We are open to different profiles, but strong candidates often come from:

• Senior product roles in complex systems (industrial software, infrastructure, IoT, energy, hardware-adjacent SaaS)
• Engineering leadership roles with strong product instincts
• Hybrid product and delivery roles in operationally complex environments

What matters most:

• Comfort making tradeoffs with incomplete information
• Ability to say no and keep teams focused
• Systems thinking rather than feature-by-feature thinking
• A strong bias toward practical delivery and real-world outcomes

How we assess fit

In conversations, we look for people who:

• Ask about sequencing and dependencies
• Care about how success is measured
• Think about failure modes and rollout risk
• Can discuss technical constraints clearly, even without coding
• Have experience stopping or reshaping work that was not delivering value

Why this role matters

This role plays a central part in the company’s next phase of growth. Strong execution here directly affects customer outcomes, team effectiveness, and the company’s trajectory.

It is a role with real responsibility, real influence, and clear expectations.

How to apply

When applying, feel free to include:

• A brief example of a complex product or system you helped deliver
• A difficult prioritization or tradeoff you owned
• A situation where technical or execution constraints forced a change in plan