Sales Engineer

About OncadeOncade is global banking for entrepreneurs. Every tool the best-run companies in the world use to move money. Now yours. Businesses that bill U.
S. clients get a U.
S. account, hold dollars as long as they want, and convert to pesos at a rate they see upfront, landing in seconds, 24/7. Backed by a16z. Oncade is a financial technology company, not a bank. The roleYou're the technical half of every sales conversation, and the person who makes sure what a customer hears on a call becomes something engineering builds. The Sales Engineer already turns call transcripts into a draft list of commitments, requests and gaps. You supply the judgment it can't: being right on the call, telling a real commitment from a polite "we'll look into it," and making sure nothing we promised gets lost between the call and the code.

What you'll do
On calls
• Join discovery and technical calls. Answer integration, payout, wallet and compliance questions accurately, and say "I'll check" when you don't know.
• Map the customer's money flow (who pays whom, in what currency, on which rail, how often) against what we support today.
• Keep what's live, what's partial and what's on the roadmap clearly separate, and don't let anyone on our side blur them. After every call
• Review the transcript and pull out four things:
• Commitments: anything an Oncade person affirmed ("yes, we do that"). These are promises to customers and get handled first.
• Customer requests: things asked about where we deflected or didn't commit.
• Pain points: bugs or failures with us or their current provider, rated critical, important or minor.
• Document requests: API docs, spec sheets, compliance certificates, case studies.
• Check each item against the codebase: exists, partial, missing, or exists but undocumented.
• Check existing GitHub issues so nothing is filed twice.
• File tickets on the Oncade Dev board, each with the customer's quote, the current state in the code, and what's needed. Order them: commitments, critical pain points, requests, then doc gaps.
• Send non-engineering gaps (case studies, compliance documents) to the people who own them. Across deals
• Review the SE agent's work: correct its drafts, approve the final tickets, and improve its instructions when it keeps making the same mistake.
• Spot requests that keep coming up across customers and make the case for them to engineering.
• Keep API docs, integration guides and technical sales material accurate.
• Track every customer commitment until it ships, and tell the customer when it does. What we're looking forMust have
• 3+ years as a sales engineer, solutions engineer, or engineer in a customer-facing technical role.
• Can read a backend codebase well enough to answer "do we support this?" with evidence.
• Can explain REST APIs, webhooks and authentication to both a CTO and a finance lead.
• Clear written English: engineers can build from your tickets without asking follow-up questions.
• Precise about the difference between what a product does and what it will do. Tools: Notion (meeting transcripts, CRM), GitHub (Oncade/gameservice, Oncade Dev project), Slack (#meeting-notes, where the SE agent posts its drafts), Claude Code. Nice to have
• Payments, fintech, payouts or treasury: rails (ACH, SWIFT, SEPA, InstaPay, SPEI), FX, KYC/KYB.
• Stablecoins or wallet infrastructure (USDC, custody providers).
• Experience with the Philippines or Mexico, or Spanish or Filipino.
• Uses AI agents in daily work: reviews what they produce and improves their prompts.
• Comfortable with GitHub issues and projects, Notion, and Slack-based workflows. How you'll be measured
• Every promise made to a customer has a ticket or a documented decision not to build it.
• Time from call to tickets filed.
• How many of your tickets engineering builds without coming back to ask questions.
• Deals where the technical review stopped being the bottleneck.

What we offer
• Competitive base salary of PHP
• Internet and equipment allowance