Integrations Support Engineer [Remote | EMEA]
Free to start · No card · 5 credits the moment you sign up
Job description
About MoneyHash
MoneyHash is building the future of API-based payment infrastructure. Our easy-install APIs consolidate the revenue cycle across geographies, functions, and use cases. We're saving our clients time and money, boosting product performance, unlocking new business opportunities, and reducing tech debt.
We're one of the fastest-growing payment infrastructure companies in emerging markets, and we know that building the right team is crucial to realizing our potential. At MoneyHash, we champion human empathy as well as work excellence. Join us and let's explore this journey together!
Your Team
Integrations is where MoneyHash's core promise actually gets built. Every merchant who connects once and reaches dozens of providers is standing on a connection that somebody scoped, briefed, tested and shipped. We add providers and payment methods continuously across MENA and beyond (cards, KNET, Mada, STC Pay, Fawry, wallets, BNPL), and each one is its own small project with its own documentation, quirks, sandbox and failure modes.
You'll own that pipeline. Requests arrive from sales, customer success and merchants: a new provider, a new payment method on a provider we already support, or a new capability on a method that's already live. You work out what each one actually involves, write it down precisely enough that other people can build it, and carry it through to go-live.
You will not write code. You will read a great deal of API documentation.
What You'll Be Doing
- Own the intake. Every connection request lands with you. Work out whether it's a new provider, a new method, or a capability extension, and check what we've already built before anything starts.
- Scope at the method level. A provider doesn't "support KWD". It supports KWD on KNET via redirection, with a specific set of operations and no tokenization. Read the provider's documentation and produce that matrix: integration types, currencies, schemes, operations, tokenization, 3DS, webhooks. Mark clearly what the docs don't answer.
- Find what's missing before engineering does. Which merchant requirements the provider genuinely cannot meet, which features the provider has to switch on for our account, what the sandbox won't let us test.
- Write the tickets. A self-contained build brief for the external developer, an engineering story with a QA checklist as its acceptance criteria, an error-code mapping table. Short, specific and correct. Our engineers have built dozens of connections and don't need the basics explained back to them.
- Manage the external developers. Brief them, keep them unblocked, review what comes back, and say no when it isn't right.
- Run the integrations backlog for a dedicated squad. Sequence the work, keep the pipeline moving, and tell the people waiting where their connection stands.
- Get it live. Credentials, testing data, QA, launch.
You’ll Be Great for This Role If You
- Have hands-on experience scoping or delivering payment provider integrations. You've worked through a PSP's API documentation and turned it into something a team could build. This one isn't negotiable.
- Can read API documentation, JSON payloads and webhook specifications and state precisely what a provider does and does not support (you won't write code)
- Write short. Much of this job is compressing a 200-page provider doc into a one-page brief somebody can build from without asking you five follow-up questions.
- Know the difference between authorize, capture, purchase, void and refund, what a webhook can and cannot be trusted for, and why tokenization and recurring are not the same thing
- Are organized under load, with several connections in flight at once, each waiting on a different person
- Have worked with external contractors or vendors and can hold them to a specification
Bonus points:
- MENA/GCC payment methods and local acquiringn
- Payment orchestration, routing, or failover
- Error-code mapping, reconciliation, or QA of payment flows
- Linear, Notion, and writing for engineering audiences
Your First 90 Days
Onboarding here is a designed program, not a stack of documents: structured sessions on how our platform and payments actually work, hands-on sandbox access from day one, and real connections to scope in your first weeks. By the end of it you'll be running the integration pipeline for real.
How We Work at MoneyHash
Beyond your functional responsibilities, everyone at MoneyHash plays a part in shaping our culture and values:
- Respect. We’re a global team and value diversity, empathy, and honest dialogue.
- Humility. We give and receive feedback with openness, leaving egos at the door.
- Flexibility. We adapt quickly, learn constantly, and step up where needed.
- Willingness to Learn. We embrace growth, celebrate iteration, and treat every mistake as a step forward.
Where we work: Remote-first across EMEA time zones, with an annual in-person retreat to bring the team together.
Compensation Package
Competitive salary - stock options - health insurance - professional development stipend - wellness stipend - tech allowance - equipment financing program - annual in-person retreat - team engagement initiatives
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for MoneyHash. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.