Robby
Deployed Product Engineer
New York, NY · $150,000-$250,000 · Full-time
About the company
Robby is a YC W26 company building the AI sales and growth engine for home services, starting with HVAC. It was founded by three Harvard Business School dropouts who embedded so deeply in the industry they rode along with dozens of technicians and are studying for the EPA 608 exam to become certified techs themselves: Feroze Mohideen, Vineet Jammalamadaka, and Joe Schwarzmann. Traction is real: nine named customer logos, paying customers each uncovering six figures in new revenue weekly, and $40k in new business closed within the first hour of launch.
US home services, HVAC, plumbing, pool, is a $600B+ fragmented market of hundreds of thousands of SMB operators running on outdated software that technicians struggle to use. Robby turns each technician visit into structured data and revenue: it helps techs figure out what equipment to recommend on a job and present clean options to a homeowner, gives them clear talking points in the field, uses simple voice AI to capture insights, and rolls everything into a single view for GMs.
The hard part is building a genuinely technical product that feels effortless to non-technical users. Robby is live with HVAC operators across the US and expanding into other home services.
About the role
It's a customer-facing product-engineering role with an FDE hat worn part-time: because HVAC operators aren't technical and the incumbent software has failed them, a big part of the job is going to customers to train, teach, and onboard them, then turning messy, unstructured field feedback into product. Feroze was explicit that this is more a customer-facing product engineer than an FDE who happens to code, whoever they hire has to be comfortable talking directly to technicians and business owners, whether over calls or on-site.
Concretely, you'll spend some days in a truck with a plumber or HVAC tech watching how the product actually gets used, then head back to the NYC office to build. The deployments aren't complex and the users aren't technical, so this is less about deploying complicated systems and more about empathy, product sense, and translating what you see into good technical architecture.
Apply
Fill this out and then pick a time to talk.
