🎁 Antes de postularte, practica esta entrevista. Crea tu cuenta gratis en WorkMundi y recibe un Entrenamiento de Entrevista en HelpsYouSpeak — sin costo, sin tarjeta. Quiero mi entrenamiento →
About Reap Reap is a global financial technology company headquartered in Hong Kong with employees across multiple countries. We enable financial connectivity and access for businesses worldwide by combining traditional finance with stablecoins for efficient money movement. Through our stablecoin-powered corporate cards, payments, and expense management tools, we streamline financial operations and help businesses scale. Our APIs enable businesses to integrate stablecoin-enabled finance into their own products and services—from issuing Visa cards to facilitating cross-border payments. Backed by leading investors including Index Ventures and HashKey Capital, Reap is building the future of borderless, stablecoin-enabled finance. About The Team The Treasury team builds and operates the core infrastructure that moves money across our platform. We’re responsible for handling incoming and outgoing flows—fiat and stablecoins, internal transfers, withdrawals, and payouts. Our systems need to be reliable, observable, and audit-ready by default. We work closely with teams across the company to design systems that meet real-world operational, regulatory, and business needs. What you’ll do As a Senior Software Engineer, you will design and build global, asset-agnostic money movement systems that work seamlessly across regions, currencies, and financial partners. You’ll build flows that handle both fiat and stablecoins in production. You will partner with engineering, product, customer success, and finance teams to build systems with both internal and user-facing impact. Responsibilities Design and operate scalable systems that move and reconcile funds across jurisdictions, channels, and asset types Build observability into every layer; lead incident response and drive long-term reliability improvements Stay current with fintech, tech, and compliance trends, and evolve our systems accordingly What we’re looking for We encourage everyone to apply even if you just meet the minimum requirements. Preferred qualifications are a bonus. Minimum Requirements Experience: Minimum of 6 years of software engineering experience, with a track record of owning and operating business-critical systems (candidates with fewer years of experience may also be considered as Software Engineer). Problem solving: You care deeply about correctness, edge cases, and failure modes. You approach problems methodically, debug with rigor, and prioritize clear, robust solutions over quick fixes. Backend focus: You have experience working on backend systems and enjoy building APIs, services, and infrastructure that power real-world applications. Data modeling and access: You’re comfortable working with relational databases like Postgres and MySQL, and have a solid understanding of transactions, data integrity, and performance tradeoffs. You’ve used ORMs like TypeORM or the equivalent in your stack, but know when to go beyond them. Technical judgment: You balance technical depth with product understanding, and apply sound judgment when making tradeoffs. You build systems that are elegant under the hood, but practical and adaptable in real-world use. Peer collaboration: You hold a high bar for code quality, reliability, and peer review, and value working closely with others who do the same. You communicate clearly, challenge ideas respectfully, and help raise the quality of the whole team. Versatility: You’re comfortable learning new domains, working across the stack, and adapting quickly as priorities shift. You thrive in fast-moving environments and aren’t afraid to dive deep into unfamiliar systems. Our main stack is TypeScript, Node.js, NestJS, and AWS, but we value strong engineering fundamentals over any specific toolset. Preferred Qualifications Domain knowledge: Experience in financial domains—such as payments, disbursements, custody, or cards—is a strong plus, but not required. Technical proficiency: You design systems that are stateless by default, built for scale, and resilient to failure. You’re comfortable with async workflows, distributed services, and cloud infrastructure. AI fluency: You embrace using AI tools to accelerate development and explore ideas, but you apply them with discernment, not as a replacement. You know when to trust outputs and when to go deeper. Full-stack experience: Experience across the stack (backend, frontend, infrastructure, data) is a bonus. High-growth environments: Experience working in high-growth teams is a bonus. After submitting your application, please check your inbox for a confirmation email. If you don't see it, kindly check your spam or junk folder and adjust your settings to ensure future communication reaches your inbox. You can follow the steps here .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.