Careers
Make travel connectivity boring
The best version of our product is one nobody thinks about. Getting there needs people who care about the unglamorous parts: coverage data, failure paths and the message someone reads at 2am in an unfamiliar airport.
These listings are sample content
They show the format this page will use once we are hiring publicly. They are not real vacancies, so please do not apply to them as though they were.
While that is true, this page is kept out of search engines and publishes no job structured data — we are not putting placeholder roles into job search results.
Who you would work with
A small distributed team: engineers who operate what they build, network operations people who argue with suppliers on our behalf, and support specialists who are the first human a stranded traveller reaches.
- Small enough that you will know everyone
- Working across several time zones
- One product, done properly
What we are building
A travel data product where the coverage list is honest, the validity rule is simple, and the support answer is a real one. That is the whole brief, and it is harder than it sounds.
182 destinations
How it feels to work here
Four things that are true regardless of which team you join.
Write things down
Across time zones, a good written explanation beats a meeting. Decisions live in documents, not in someone’s memory.
Say the inconvenient thing
If a coverage claim is not supportable, we want that raised loudly and early — including when it costs us a sale.
Own the outcome
Small team, wide scope. You will follow your work into production and into the support queue that follows it.
Protect the off switch
We support travellers around the clock as a team, never as an individual. Being permanently reachable is a staffing failure, not dedication.
What we offer
Specifics vary by country and are confirmed in writing before an offer — nothing here is a substitute for a contract.
Remote-first by default
Work from where you are effective. Most roles are not tied to a desk.
Flexible hours
Coverage windows are agreed as a team; the rest of your day is yours to arrange.
Home office budget
A one-off allowance for the desk, chair and screen you actually need.
Learning budget
An annual allowance for courses, conferences or books, no approval theatre.
Paid time off
A real allowance that we expect you to use, plus local public holidays.
Travel data, obviously
A plan on us. It is also the fastest way to find our product’s rough edges.
How remote actually works here
Remote-first means the default is distributed, and the exceptions are named on the role. We do not run a hidden headquarters where the real decisions happen.
- Decisions are made in writing so nobody depends on being in a particular room.
- Some operations roles need to be in Hong Kong for supplier and regulatory reasons — those are labelled on-site or hybrid, never quietly.
- Support rotas are built around traveller time zones, agreed in advance and shared out fairly.
Life at SAIMING
Team photography will appear here
We are not using stock photography of people who do not work here to illustrate a team page.
Open roles
Filter by department, location or work mode.
Narrow these down
Showing 7 of 7 sample roles
About the role
Own the services that turn an order into a working eSIM profile: provisioning, supplier calls, retries and the audit trail behind them.
What you would do
- Build and operate the provisioning pipeline end to end, including failure paths.
- Keep supplier integrations honest — verify what an API actually does before we promise it.
- Make incidents boring: alerting, runbooks and a habit of writing things down.
What we would look for
- Several years building production services in a typed language.
- Comfortable owning correctness in a system that spends real money.
- You write the postmortem nobody asked for.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Build the storefront and account experience — fast, accessible and honest about what a plan does and does not cover.
What you would do
- Ship product surfaces in a modern React codebase with strict typing.
- Treat accessibility and performance as requirements, not a later pass.
- Work directly with support to fix the things travellers actually get stuck on.
What we would look for
- Strong React and TypeScript, with real care for the rendered result.
- You can read a WCAG success criterion and tell whether we meet it.
- You have opinions about loading states and can defend them.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Own the supplier relationship: zone tables, commercial terms, and making sure what we sell matches what the network will actually do.
What you would do
- Hold suppliers to their coverage lists and escalate when reality diverges.
- Turn raw zone data into something the rest of the company can act on.
- Sit in the room when terms are negotiated and say the unpopular thing.
What we would look for
- Experience in mobile, roaming or wholesale connectivity.
- Fluent in spreadsheets and in the politics of a supplier call.
- Based in or able to work from Hong Kong.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Turn supplier tables into the numbers we publish. If a coverage claim is on our site, you can trace it to a row of data.
What you would do
- Reconcile supplier zone tables against our catalogue every time either one changes.
- Flag gaps loudly — including the ones that are commercially inconvenient.
- Keep the pipeline that generates our published coverage figures trustworthy.
What we would look for
- Comfortable with SQL and scripting your way through messy reference data.
- You would rather publish a smaller number than an unverifiable one.
- Detail-obsessed, and able to explain the detail to people who are not.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Own the messages a traveller receives before, during and after a trip — useful ones, at a sensible frequency.
What you would do
- Design lifecycle messaging that helps people install and activate successfully.
- Measure whether a campaign helped, and switch off the ones that did not.
- Keep every claim in outbound copy backed by product reality.
What we would look for
- Hands-on lifecycle or CRM experience in a consumer product.
- You can write plainly and resist the urge to oversell.
- Numerate enough to read your own results honestly.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Be the person who answers when someone has just landed and their phone will not connect.
What you would do
- Handle inbound conversations across chat and phone with real answers.
- Diagnose device and activation problems calmly, across time zones.
- Feed recurring problems back to product instead of re-answering them forever.
What we would look for
- Experience supporting a technical consumer product.
- Patient in writing, clear under pressure.
- Able to work a schedule that overlaps travellers, not just office hours.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
About the role
Build the support function: staffing, quality, tooling, and the escalation path when something is genuinely broken.
What you would do
- Lead and coach a small distributed support team.
- Own response quality and the metrics that describe it truthfully.
- Partner with engineering on the fixes that remove tickets entirely.
What we would look for
- You have led a support team through growth, not just headcount.
- Comfortable saying “we got that wrong” to a customer.
- Fluent English; another language spoken by our travellers is a plus.
How to apply
We do not run an applicant tracking system yet, so introductions come to us directly. Tell us which role interests you and what you have built.
This is a sample listing. The contact details are real, but there is no vacancy behind this card.
How hiring works
Four steps, roughly two to three weeks, with a written answer either way.
Introduction
You tell us what you have worked on. We reply whether or not it is a fit.
Conversation
A call about the role, the team and what the first three months look like.
Practical exercise
A short, paid, realistic piece of work. Not a weekend project, and not a whiteboard puzzle.
Decision
A final conversation, references, then a written offer with the specifics in it.
Nothing here fits?
We hire slowly and irregularly, so the list is often short. If you care about the same problems we do, send an introduction anyway — we keep them and we do read them.
Ready for your next trip?
Choose a plan today and install it before you pack.
Results appear below as you type. Use the up and down arrow keys to review them, Enter to open one, Escape to close.
182 destinations
Apps for iOS and Android
Not published yet. Buy and manage everything on the web in the meantime.
- App StoreComing soon
- Google PlayComing soon