Solutions Engineer

Summary

Prompt.io is a non-partisan engagement technology company that helps organizations connect with audiences through texting, voice, and engagement tools. The Solutions Engineer will own and develop the solutions repository, building customer integrations and internal tooling while collaborating with customers, vendors, sales, marketing, product, and engineering. The role will also advise technical users, maintain the developer surface, and identify opportunities to improve processes and migrate solutions into the core platform.

Responsibilities

• **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!

Skills

• 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
• 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're careful with other people's data and credentials. Much of what passes through this role is sensitive: contact lists, customer API keys, access to customer infrastructure
• You're comfortable on calls with customers and their vendors, and ready for a technical conversation
• Applicants must be authorized to work in the United States or Canada and not require sponsorship of a visa, unless otherwise specified in the posting
• Supabase experience helps
• Junior candidates are fine if the fundamentals are there
• Background in messaging, telephony, or CRM tooling is a plus, and so is any exposure to government, political, union, or nonprofit organizations, which make up most of our customer base

Qualifications

Must Haves

• 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
• 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're careful with other people's data and credentials. Much of what passes through this role is sensitive: contact lists, customer API keys, access to customer infrastructure
• You're comfortable on calls with customers and their vendors, and ready for a technical conversation
• Applicants must be authorized to work in the United States or Canada and not require sponsorship of a visa, unless otherwise specified in the posting

Nice to Haves

• Supabase experience helps
• Junior candidates are fine if the fundamentals are there
• Background in messaging, telephony, or CRM tooling is a plus, and so is any exposure to government, political, union, or nonprofit organizations, which make up most of our customer base

Benefits

• 401(k) match
• Health benefits for you and your family
• Unlimited flexible time off
• Annual team gatherings
• Professional development opportunities
• Remote-first work arrangement