Remitly backend engineering jobs

Remitly has 29 open backend engineering roles: 18 in Seattle, 8 in Burnaby and 2 in Arlington. 23 of them state the pay; the middle half sits between $188k and $218k a year. Roles at Remitly take 42 days to fill at the median.

Read from Remitly's careers boardRebuilt 21 Oct 2026
open backend engineering roles
29
median stated pay
$203k
new in 7 days
0
median time to fill
42 days

Newest backend engineering roles

15 of 29

All open roles at Remitly

Where the roles are

Seattle 18Burnaby 8Arlington 2Kraków 1

By level

LevelOpen rolesMedian stated pay
Mid-level3—
Senior16$203k
Staff and principal6$234k
Lead4$270k

Other teams hiring at Remitly

AI and machine learning 16Finance 14Marketing 14Product management 12Management 11HR and recruiting 10Legal 9Analytics 7Design 4Operations 4Data science 3Security 3Engineering leadership 3

Backend engineering roles at similar companies

Apply to Remitly with a tailored kit

Smart Apply writes the CV and the cover letter for one role in about a minute, from your profile and the job description. 10 credits a kit; new accounts start with 30 free credits.

Questions

How many backend engineering roles is Remitly hiring for?

Remitly has 29 open backend engineering roles as of 21 Oct 2026.

What does Remitly pay for backend engineering roles?

23 of the 29 roles state the pay. The median of the posted ranges is $203k a year and the middle half sits between $188k and $218k (converted to US dollars).

Where are Remitly's backend engineering roles?

Most are in Seattle (18), Burnaby (8) and Arlington (2).

How long do roles stay open at Remitly?

Half of Remitly's roles are filled or closed within 42 days of being posted, measured on the postings that closed on its own careers board.

Are these roles still open?

Every role is read from Remitly's own careers board and re-checked at least every 48 hours. A role that closes leaves this page at the next nightly rebuild.

Source: Remitly's own careers board, re-checked every 48 hoursUpdated 21 Oct 2026MethodologyJSONCC BY-SA 4.0