Software Engineer, Channels

About the role

Multiplier helps companies employ people anywhere in the world through employer of record and payroll. Channels is the vertical built on top of that: the benefits, insurance, background verification, IT assets and other services an employer needs around each employee. It already contributes substantially to the company's revenue, demand is proven, and engineering investment so far has been small. We are building the team to change that.

You would join an existing small team. The demand is proven and we are entering the rapid expansion phase. However, for us to be successful, we need the best engineers who can engineer their way around various and vivid third party software systems which they have no control over. Today parts of this still run on people, spreadsheets and email, your job is to turn it into software that reaches real clients and real payslips.

Engineering here means building the right foundations so that providing a new benefit, supporting a new catalogue or go-live in a new country is a matter of days and not months.

What you will build

• Eligibility and administration: A global catalog and rules engine decides who is eligible for what, with our own benefits-administration platform built on top.

• Marketplace: It prices and routes orders across suppliers.

• Partner connectivity: Connectors reach insurers and brokers who speak everything from modern APIs, emailed spreadsheets and web portals.

• Money: Billing and payroll deductions must be exact to the cent across currencies.

• AI agents: They take real actions on money and personal data, with permissions, audit trails and human approval.

• Scaling: Each new country and each new product should be mostly configuration, not a rebuild.

• Where it goes next : An employer anywhere adds a benefit, a laptop, insurance or a background check at checkout, and it simply gets fulfilled, with people handling only the exceptions.

• Distributed Systems at Scale : For the above to materialise, we are talking about services with 99.999 availability, near real-time updates,

Seniors carry a squad's feature area. Leads and staff set direction beyond their own code.

What we're looking for

We care more about what you've built and owned than about years or pedigree. Five things matter most:

• You have shipped backend services to production and stayed accountable for them, including on-call.

• You understand distributed-systems basics in practice: idempotency, retries, async processing, and consistency trade-offs.

• You have built or consumed third-party APIs and integrations, and know how they fail.

• You take correctness seriously where money, payroll or personal data is involved.

• You can write a clear design doc and disagree constructively in review.

Nice to have: experience with partner or marketplace platforms, benefits or insurance software, multi-tenant products.

If you meet most of this and are excited by the problem, apply. We would rather talk to you than have you screen yourself out.

Why join us?

• AI with real stakes. Agents that act on money and personal data are among the harder applied-AI problems today, and you will learn to build them reliably.

• Work that moves the numbers. Today we contribute significantly to the company’s revenue and growing, so what you ship shows up in the business results.

• Scope you would not get elsewhere. You will make architecture calls on a new vertical and set the patterns the next hires follow.

• Skills that travel. Ledger-grade correctness, partner integrations at scale, marketplaces and applied AI are valued across fintech, HR tech and insurtech.

• A short loop to the user. The operations teams who use what you build are colleagues, so you see problems and fixes quickly.

Hiring process

Four steps, no puzzle questions. We tell you what each round tests.

1. Intro call with a recruiter about the role, the team and what you want next.

2. AI-assisted coding round (1 hour). You build a small product component with AI tools, then change it live based on the interviewer's input. We look at how you work with AI and how you reason about code. This is not a LeetCode round.

3. Technical discussion (1 hour). Your past systems, plus data structures and algorithm fundamentals.

4. System design with an engineering manager, followed by a conversation with the Director of Engineering.