Product Engineer

Who We Are

Ingage helps our clients win. A win is a better number on the client scoreboard: fewer cancelled appointments, higher close rates, faster rep ramp, bigger tickets, more referrals. We do not define that scoreboard. We help them put points on it.

We got there by naming a problem the trades had lived with for decades. Most companies do not have a talent problem, they have a readiness problem. Standards get set every time a salesperson sits down across from a homeowner, not in Monday meetings. The standard is not what you expect, it is what you accept.

We are 40 people headquartered in Yardley, Pennsylvania, serving home improvement companies focused on replacement projects like roofing, siding, windows, doors, gutters, coatings and one-day baths.

We're a curious team that moves with agency. Not agency as a buzzword — agency as in: when James hit a wall on a recent feature, he didn't wait for someone to unblock him. He pulled the right people into a room that day, got early feedback on the architecture before writing more code than he needed to, and watched customer calls himself to check his thinking against reality instead of working off secondhand notes. That's the norm here, not the exception, for the people we're building this role around.

We care about the code we ship, we challenge each other's thinking directly and respectfully, and we'd rather ship something useful today and improve it tomorrow than wait for perfect.

The Opportunity

We're naming something that already exists on part of our team, and setting it as the real bar going forward.

Some of our engineers take a roadmap item and run — they ask sharp questions, own the feature end to end, and don't need a fully-written spec to get moving. Others need tickets, detailed requirements, and a lot more hand-holding before they'll take initiative. That gap is real, and it's holding us back.

The Product Engineer role is what we're calling the first kind of engineer. Not a traditional software engineer waiting on requirements. Someone who partners directly with our Product Manager to shape what gets built, then owns it — scoping, documenting, coordinating the build (including directing AI agents), reviewing the work, and delivering it.

The Challenge We're Solving

We're a small team, and AI is changing what engineering work actually looks like. Engineers are writing less code by hand and doing more of the thinking that used to sit with product management — understanding the problem, shaping the requirements, directing the build. If we don't make that shift deliberately, our roadmap becomes bottlenecked on our Product Manager's bandwidth to write ever more detailed tickets. If we do make the shift, we scale by adding engineers who can own outcomes, not by adding layers of specification between idea and shipped feature.

Success Outcomes

In 90 days: Documentation is a first-class part of your job, not an afterthought. You're collaborating with our Product Manager on shaping the brief itself, not just receiving it — then owning scoping, writing documentation clear enough for AI agents (and humans) to build from, coordinating the build, reviewing the output, running QA, and delivering to the estimates your team sets.

In 6 months: You're trusted with real ambiguity — not just bigger tickets, but problems big enough to change the shape of the product. Think something like adding an entirely new primitive to our platform: you'd work across Leadership, Design, CX, and real customers to understand the problem, produce the shaping documents your team builds from, and pull together and lead a small team to execute it.

In 12 months: You're operating like a Product Owner — supported by our Director of Product and Engineering and our PM, but capable of defining initiatives and requirements yourself. This is how we scale our roadmap without needing a 1:1 ratio of product managers to engineers. It's also how you build a career that holds up as AI takes over more of the raw coding work — the skill that doesn't go away is turning an ambiguous problem into something buildable.

What You'll Work With

You'll report directly to our Director of Product and Engineering, and work closely day to day with our Product Manager, our Senior Software Architect, and our Senior UX Designer. You'll pull in other engineers — iOS, Desktop, Web, API — as your initiative requires it.

Linear is where the real work happens: features, requirements, and documentation get built there as you go. Notion and Intercom come in once something ships, to translate your work into what Sales, CX, Channel Partners, and Marketing need to know.

You choose the AI tools that get the job done — frontier models or local ones, whatever fits — and we expect you to contribute back to the shared skills and tooling the team relies on, not just use what's already there.

One honest constraint: we don't have deep QA bench strength. You are the primary quality gate on your own work — covering what you ship with real unit and automation tests, and helping maintain the tooling (like our Cerberus platform) that keeps our test suite running continuously. QA is there to back you up on smoke and confidence testing, not to catch everything for you.

Why This Is Different

We're an AI-first engineering team — not "AI tools are allowed," but actively encouraged, resourced with the hardware, software, and services to stay on the leading edge. If you crush it here, the payoff is more autonomy, bigger and messier problems to own, and real, visible impact on what our customers experience. Not just tickets closed — outcomes that move the business.

What We're Honest About

Priorities shift mid-sprint. We're small, and we don't always have the right answer up front — we build, put it in front of real customers early, and change course if it's not landing. That means shipping things that feel unfinished sometimes, because getting real value in front of customers quickly beats waiting to ship something polished. If that kind of ambiguity makes you uneasy, this isn't the right seat.

Our Culture

Mostly async, mostly Slack day to day. Two meetings you can count on: our company-wide WCB on Mondays and our Engineering Demo on Fridays. Beyond that, you're expected to self-schedule time with peers to work through initiatives or unblock each other.

You'll know you're getting it right within the first month if you're running an initiative end to end with real ownership, staying curious about the parts of our stack you're not yet strong in, and actively working to make the people around you better — not just shipping your own piece and moving on.

The one thing that doesn't work here: working in a silo. If you can't build the relationships to pull the right people in when a feature needs it, this role isn't going to click for you, no matter how strong you are technically.

Product engineer with strong ownership, ability to shape requirements, write documentation for AI agents, coordinate builds, run QA, and deliver features end-to-end.

Key Responsibilities

• shaping product requirements
• owning feature delivery
• coordinating engineering builds

Skills & Tools

Linear, Notion, Intercom, Cerberus

Job Details

• Category: Software Development
• Seniority: Mid Level
• Commitment: Full Time
• Workplace: Remote — Yardley, Pennsylvania, United States
• Languages: English

About Ingage

A software company helping home improvement companies win by improving sales readiness and performance. — Industry: Information Technology