All remote jobs

Staff Software Engineer, Product/AI

AI Summary
Customer.io is hiring a Staff Software Engineer to lead ambiguous, customer-facing product and AI initiatives across the full stack. The role requires strong backend depth, practical cross-stack leadership, and ownership from problem framing through launch and iteration. The engineer will partner closely with product, design, and data, guide architecture and reliability decisions, and influence teams without formal authority. Regular use of AI in the software development lifecycle, sound evaluation of its outputs, and improving team AI workflows are core expectations. The position also includes participation in an on-call rotation and mentorship through reusable technical patterns and guidance.
Remote from
USA, Canada, LATAM
Salary
USD 200k–280k / yr
Employment
Full Time
Experience
Director
Published
Apply before
8 Dec 2026
Listing views
50
Application actions
3
Application toolkit

Make your next move.

Prepare your resume, explore your fit, and draft a cover letter for this opportunity.

Opportunity details

About this role.

Hi, I’m Paul, VP of Engineering at Customer.io. 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.

About Customer.io

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. Customer.io powers automated communication that people actually want to receive.

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.

What We Value

End-to-end ownership

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.

Comfort in ambiguity

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.

Customer-first, always

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.

A healthy skepticism for “the way things are done”

You retire practices that have outlived their usefulness, including ones you helped build. Best practices matter — but never more than forward motion.

Force multiplication

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.

What You’ll Do

  • Own important, ambiguous problems from initial framing through launch and iteration. Set direction, align partners, and stay accountable for the result.
  • Partner with product, design, and data to shape priorities, scope the work, and define how success will be measured.
  • Lead technical decisions across the stack, including architecture, performance, reliability, and maintainability.
  • Lead work across teams and systems. Build alignment, resolve technical disagreements, and keep complex initiatives moving.
  • Improve engineering practices through mentorship, reusable patterns, and clear technical guidance.
  • Use AI throughout your engineering work, with sound judgment about where it helps, where it falls short, and how its output should be reviewed. Help the team improve by testing new workflows, sharing what works, and identifying useful opportunities for automation.
  • Participate in an on-call rotation as required, supporting the systems the team builds.

What we’re looking for

  • A track record of leading complex work across teams or systems and delivering meaningful customer, business, or engineering outcomes.
  • Strong backend engineering experience, with the ability to work across the stack and lead end-to-end technical decisions.
  • Strong product and technical judgment, especially when the problem or path forward is unclear.
  • The ability to influence experienced peers and align teams without formal authority.
  • Experience using metrics, experimentation, and observability to guide decisions and improve production systems.
  • Regular, hands-on use of AI across the software development lifecycle, with the judgment to adapt as tools change while remaining accountable for quality, security, and outcomes. Experience improving how a broader team uses AI is a strong plus.

Compensation & Benefits

We believe in transparency. Starting salary for this role is $200,000 – $280,000 USD (or equivalent in local currency) depending on experience and subject to market rate adjustment. This role also carries a 10% annual bonus target. In addition to base salary, this role includes an equity grant in the form of stock options, so you share in the success you help build.

We know our people are what make us great, and we’re committed to taking great care of them. Our inclusive benefits package supports your well-being and growth, including 100% coverage of medical, dental, vision, mental health, and supplemental insurance premiums for you and your family. We also offer 16 weeks paid parental leave, unlimited PTO, stipends for remote work and wellness, a professional development budget, and more.

See full benefits here →

Our Process

No gotchas, no trick questions – just a clear, human process designed to help both of us make an informed decision.

  1. Application – We review everyone with care. Tell us why you’re interested.
  2. Recruiter Call (30 mins) – Let’s chat about what you’re looking for and how we work.
  3. Hiring Manager Interview (60 mins) – Talk with one of our hiring managers about your working style and a product you’ve owned end-to-end, plus a short AI-assisted coding exercise.
  4. System Design Interview (60 mins) – A collaborative conversation that moves between product tradeoffs and system design — how you’d scope something ambiguous and how you’d build it.
  5. Take-Home Assignment – Complete a short, realistic task similar to what you’d work on here.
  6. Assignment Review Call (60 mins) – Walk us through your work and discuss tradeoffs, priorities, and how you’d iterate.

All final candidates will be asked to complete a background check and employment verifications as part of our pre-employment process.

Customer.io recognizes the stifling impact of systemic injustice on diverse communities. We commit to using our influence to increase inclusion and equity within the tech industry. We strive to build an inclusive team culture, implement bias-free hiring practices, and develop community partnerships to expand our global impact.

Zoom is the only video conference platform that we use, virtual interviews will be conducted using the video capability (i.e., not via the chat), and offers will be extended in writing on official Customer.io letterhead. Please be vigilant in all of your job search activity, and if you have any questions please contact jobs@customer.io.

Join us!

We believe in empathy, transparency, responsibility, and, yes, a little awkwardness. If you’re excited by what you read and want to build software that makes communication better for everyone—apply now.

Apply now >

This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.

Role DNA

A quick view of the complexity, pace, ownership and collaboration implied by the job description.

Job Complexity

5/5
EasyHard

Pace & Pressure

4/5
RelaxedFast-paced

Autonomy Level

5/5
GuidedFull ownership

Communication Load

5/5
IndependentCollaborative
AI insightThis is a staff-level position centered on ambiguous, cross-team technical and product problems with accountability for strategic outcomes. Success requires advanced engineering judgment, organizational influence, and the ability to make high-impact trade-offs independently.

Salary analysis

Estimated compensation compared with the broader US market for similar roles.

Estimated job median (per year)Market rate
$240,000
US market range (per year)$190k–$300k
AI insightThe yearly pay period is inferred from the job context; it was not explicitly stated by the employer. The employer discloses a base salary range of $200,000–$280,000 USD. The posting does not explicitly state the base-pay cadence, so yearly pay is inferred from the senior US-oriented software engineering compensation level; the separate 10% annual bonus is excluded from base-pay figures. Estimated US market base pay for comparable staff-level product engineering roles is approximately $190,000–$300,000 per year.

Core skills

Skills and capabilities most closely associated with this opportunity.

Sample interview questions
Tell us about an ambiguous product or technical problem you took from initial framing to production.

I would describe how I clarified the customer problem, aligned stakeholders on measurable outcomes, evaluated options and risks, delivered an incremental solution, and used post-launch data to guide iteration.

How do you make architecture decisions when product requirements are incomplete or changing?

I establish the key customer and business constraints, identify reversible versus irreversible decisions, propose a small number of viable options, and document the trade-offs. I favor an approach that supports near-term learning without creating avoidable reliability or maintenance costs.

How have you influenced experienced engineers or multiple teams without formal authority?

I build influence through clear problem framing, evidence-based proposals, active listening, and shared ownership of decisions. I involve affected teams early, make trade-offs explicit, and leave behind documentation or reusable patterns that help the decision scale.

What is your approach to using AI tools in software development responsibly?

I use AI to accelerate research, drafting, test generation, and routine implementation work, but I treat its output as untrusted until it is reviewed and validated. I ensure human accountability for correctness, security, privacy, and operational impact, then share effective workflows with the team.

How would you improve reliability for a high-volume messaging platform while continuing to ship product features?

I would start with service-level objectives, production telemetry, and the highest-impact failure modes. I would prioritize targeted improvements such as capacity safeguards, resilient asynchronous processing, better alerting, and safe rollout mechanisms while planning product work in increments that protect operational stability.

This analysis is generated from the job description. Salary estimates, role characteristics and sample answers are guidance, not employer-provided facts.
Next step

Apply now.

Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.

Did you apply?Let us know, and we’ll help you track your application.

Continue on the employer website

Protect your personal information and never pay to secure an interview or job offer. .

Log in to save
One quick step before you apply

Sign in to continue.

Sign in or create a free account to continue to the employer's application.

Add alert
Jobs Talent AI Tools Salaries
Menu