Harmony · New York City, United States
Product Engineer
Harmony, New York City. Hybrid: one to two days a week in our Manhattan office. Full-time. $130,000 to $180,000 base plus equity.
Millions of Americans qualify for support they never receive, because the system asks the most of the people with the least room to spare. Harmony is reimagining how people access essential services, starting with affordable housing in New York City. Housing is the entry point; access to every benefit a family already qualifies for is the destination.
The role
We're hiring a Product Engineer to own the day-to-day of our products: what's broken, what customers need next, what we build, and whether it works. You'll do that across our existing and future product portfolio, working hand-in-hand with our CEO, our engineers, and our designer. You'll also play a pivotal role in shaping the future of Harmony's products: which problems we take on next, what we build for them, and how we get there.
It's a product job for someone who works the way we work. Nearly everything at Harmony runs through Claude or another agentic tool, and this role is no exception: when you have an idea, you'll build it before you write about it. You don't need a traditional engineering background. You do need to be a product person who can stand up their own test environment, prototype an idea, build a skill the team needs, and produce a wireframe on our design system.
What you'll do
Sit with the marketing agents and compliance managers using Harmony, watch them work a real batch of applicants, and come back knowing what to build next
Figure out what Harmony looks like for future opportunities (SNAP, Medicaid, WIC, etc.): the rules, the people who run them, and the families applying
Use the product the way an agent and an applicant do, and catch what's wrong: bugs, rough edges, and places where it doesn't match how the regulations actually work
Turn an idea into a working prototype, and put it in front of the team or a customer the same week
Write the PRDs and tickets that engineers and agents build from, whether the source is a customer request, a bug you found, or a product we haven't started yet
Be the person our customers reach first: answer them, reproduce what they hit, and make the materials that keep them from hitting it again
Run our standups, clear blockers, and build the tools and processes a small agentic team needs
Pick up whatever else the team needs. We're at a stage where everyone is close to every part of the work
What we're looking for
You ship. You have an active GitHub with projects you built and contributions you made, and you got there with Claude Code, Cursor, or similar. You don't need to be an engineer in the traditional sense, but you do need to be able to take an idea to working software with agentic tools.
You've owned product decisions. We don't require a particular title or path. We care that you've decided what to build, why, and in what order, with actual customers on the other end, and that you got there by doing your own research: talking to the people involved, synthesizing what you heard, and changing your mind because of it.
You take initiative. When you want to know whether something works, you go find out. When something new comes up, whether that's our design system, a housing regulation, or a tool you've never used, you dig in rather than wait. There's a whole team here to help, but we're looking for people who start on their own.
You communicate well. In writing and in person, with engineers, customers, and founders alike. On a small, distributed team, effective communication is vital.
Bonus points
Experience working in or around housing, public benefits, civic tech, real estate, or another highly regulated industry
You've worked at an early-stage startup before
Computer science or engineering background
Experience shipping products or features built on an LLM
LANGUAGE REQUIREMENT: Detect the primary language used in the source document and write all generated descriptive text fields in that SAME language. For JD this includes: description_summary, intro_text, responsibilities, generated_html_description. Return salary fields separately as requested: salary_type, salary_period, salary_currency, salary_min, salary_max. Do NOT translate these fields to English unless the source is English. Detected source language code: en (English). Use this detected language for all generated narrative fields. If uncertain, default to English (en).