Solutions Engineer

ABOUT PROMPT.IO INC.

Prompt.io Inc. is the winning and influence engine that partners with organizations of all sizes and scale to engage and activate supporters. We are a non-partisan company that helps political campaigns, advocacy organizations, unions, government representatives, nonprofits, and other mission-driven organizations connect with their audiences through texting, and engagement tools.

ABOUT PROMPT.IO INC.

Prompt.io Inc. is the winning and influence engine that partners with organizations of all sizes and scale to engage and activate supporters. We are a non-partisan company that helps political campaigns, advocacy organizations, unions, government representatives, nonprofits, and other mission-driven organizations connect with their audiences through texting, and engagement tools. We're a growing tech company where individual contributions can have an outsized impact. We value people who take ownership, bring ideas, move with purpose, and are excited to help build what comes next. As a result of that growth, we are aggressively adding business lines that deliver unique value for our core markets.

ABOUT THE ROLE

You will own the Prompt.io Inc. solutions repository, a Next.js and Supabase app where we build the things the core platform doesn't cover: special integrations for customers, and internal tooling that keeps our own systems talking to each other. Most of what you build, you'll scope and ship yourself. You'll be part of a small solutions team. Beyond the team, you'll work with almost everyone: customer success and customers most days, sales when a deal needs something built, marketing when they need a demo, and product or engineering whenever a problem turns out to belong to the core platform.

WHAT YOU'LL DO

Intake : Sit with customers to figure out what they actually need. Most requirements come out of conversations with customers and our team members. You'll run those calls and turn what you hear into software that solves their problem.

Triage : Decide what should get built, and who should build it. When a customer problem comes in, the first question is whether it needs custom work at all, or whether the platform already has a workaround they can live with, and what happens if we do nothing. If it does need to be built, you build it. If part of it depends on changes to the core platform, or you believe all customers ought to have it, you write up what product needs to know and hand it off.

Experiment , research, & invent At Prompt.io, Solutions Engineering is often phase 0 of the product pipeline. Your solution to one customer's problem may become the blueprint for a platform feature that solves problems for all customers. Consider it a big win if the product team decides to migrate your work out of solutions, and into the core platform.

Advise : Help people build on top of Prompt.io. Vendors, technical customers, and partners are writing wrappers around our platform. You'll be their technical contact: showing them the MCP server and getting them to use it, and when they'd rather go straight to the API, acting as the person who knows it best and can tell them how to do what they want.

Maintain the Repo : Keep the developer surface current. The portal hosts our MCP server, which needs to track the platform as it changes.

Take Initiative : Notice when a process is broken and fix it, without waiting for someone to assign it. If a team member built an essential operational tracker in Google Sheets, and it should be in solutions; migrate it. If a support team member wrote an ad hoc, yet extremely useful python script that only they know how to use, you should port it over to the solutions environment, so the whole support team can use it. If the product team de-scoped a feature you think could live in solutions, build it yourself

WHAT WE'RE LOOKING FOR

U.S. or Canada based. No international applicants please.

You're comfortable with Next.js, TypeScript, and Postgres, and you've worked with git on a team: branches, pull requests, reviews, a release schedule.

3-5+ years experience in a similar role

Supabase experience helps.

Junior candidates are fine if the fundamentals are there.

You've connected systems before. Webhooks, REST APIs, large CSVs, cron jobs, authentication between services.

You are deeply fluent in Claude Code, Codex, or Cursor (or sim.), and can manage many agents simultaneously, steering them towards quality outputs, with great taste.

You&amp