About Refold AI Refold AI is the AI integration platform built for agents, made for modern SaaS companies that need to ship enterprise integrations at scale. We're reimagining integrations with AI agents that work like business consultants and integration engineers, building them 10x faster, in hours instead of days. The payoff: integrations stop being a bottleneck that costs you deals and burns margin, and become a growth engine. You win the enterprise deals that hinge on them, onboard faster, and scale without an army of consultants. We've grown rapidly, reaching seven-figure ARR and 30+ paying customers, powering the product and professional services teams at modern SaaS companies, from Incorta, Kantata, and Coupa to Highradius, Naehas, and OvationCXM. Refold AI has raised $6.5M from world-class investors including Eniac Ventures (early investors in Airbnb & Uber), Tidal Ventures, and Better Capital. What you'll do: • Where does automation earn trust, and where does a human still need to stay in the loop? • You will draw that line repeatedly, and the answer will keep changing. How do you price outcomes instead of usage, in an industry that has only ever paid for hours? • You will own that question commercially and build the model around it. What does it mean for a platform to get smarter across customers without leaking what any one customer knows? • You will define what learning looks like at the system level. • How do ISV developers think about reliability when their customers depend on • integrations running without anyone watching? You will own that experience end to end. • When something breaks in production for an enterprise customer, who gets told, what do they see, and what can they do about it? You will design that judgment layer. What we're looking for: • You have shipped something on your own. A side project, a tool, anything you took from zero to working. We are building systems with real complexity. We need someone who has felt the difference between a decision made in a doc and a decision made in code. • You are technically grounded. You do not write the code, but you understand the structure, the trade-offs, and the failure modes. When engineering says a change costs 40% more compute, you know what that means downstream. • You think in constraints. When you look at a feature request, the first question is what breaks if we build this, not what we could do with it. Edge cases are not polish. They are often the product. • You write, not deck. Specs, trade-off docs, design decisions. If you cannot write a crisp two-page spec, the feature is not ready to build. • You push back. If the scoping is underspecified, say so. If the deadline is not realistic, say so. Disagree clearly and commit once a decision is made Experience • 5+ years in product in the B2B software industry • At least 2 of those years on a platform, infrastructure, or developer tool. • Comfortable with distributed systems concepts: queues, retries, schema versioning, idempotency • Track record of shipping things that were actually hard, not feature additions on a stable roadmap • Degree from a top-tier institution, or hands-on product experience at a company known for building hard things. One or the other, not neither. Originally posted on Himalayas