Staff Software Engineer, Product/AI

<p>Hi, I'm Paul, VP of Engineering at <a href="https://jobicy.com/company/customer-io" rel="noopener" target="_blank">Customer.io</a>. We're looking for a staff product engineer — not a generalist who happens to touch frontend and backend, but someone who thinks like a product owner and ships like an engineer.</p> <h3>About <a href="http://Customer.io" rel="nofollow ugc noopener" target="_blank">Customer.io</a></h3> <p>Over 9,000 companies — from scrappy startups to global brands — use our platform to send billions of emails, push notifications, in-app messages, and SMS every day. <a href="http://Customer.io" rel="nofollow ugc noopener" target="_blank">Customer.io</a> powers automated communication that people actually want to receive.</p> <p>We help teams send smarter, more relevant messages using real-time behavioral data. Under the hood: Go, React, and AI help us ship fast and scale with confidence.</p> <h3>What We Value</h3> <p><strong>End-to-end ownership</strong></p> <p>You take on the problems nobody's claimed — the ones that span squads with no obvious owner — and carry them from a fuzzy first conversation to what's actually live. If it touches the customer, it's yours to chase down.</p> <p><strong>Comfort in ambiguity</strong></p> <p>Half-formed problems and conflicting signals are your starting material, not a blocker. You define the problem before you solve it, form a point of view on what's worth building, and move without waiting for someone else to de-risk the call.</p> <p><strong>Customer-first, always</strong></p> <p>You think from the customer's problem backward, not the codebase forward. Every technical call traces back to what it does for the person on the other end of the message — and you can explain that connection to people who don't write code. Given the choice, you ship the thing that changes their experience, not the thing that's merely elegant.</p> <p><strong>A healthy skepticism for "the way things are done"</strong></p> <p>You retire practices that have outlived their usefulness, including ones you helped build. Best practices matter — but never more than forward motion.</p> <p><strong>Force multiplication</strong></p> <p>Shipping your part isn't the bar. You bring in the right people before a problem becomes theirs to clean up, and you leave enough behind — docs, patterns, delegation — that the team keeps moving without you in the room.</p> <h3>What You'll Do</h3> <ul> <li>Own important, ambiguous problems from initial framing through launch and iteration. Set direction, align partners, and stay accountable for the result.</li> <li>Partner with product, design, and data to shape priorities, scope the work, and define how success will be measured.</li> <li>Lead technical decisions across the stack, including architecture, performance, reliability, and maintainability.</li> <li>Lead work across teams and systems. Build alignment, resolve technical disagreements, and keep complex initiatives moving.</li> <li>Improve eng