Nango's remote hiring: what it means for Sri Lankan devs
A YC-backed dev-tools company says fully remote, global team, outcomes over hours. Here's how to read that from Colombo, and what to check before you apply.
Remote developer jobs from Sri Lanka usually come with a catch, and the Hacker News listing for Nango (YC W23) hiring across engineering, product and GTM is a useful case study in reading that catch correctly. Their careers page says three things worth separating: fully remote, global team, and outcomes over hours.
Those three phrases decide whether someone in Colombo can realistically hold the job. The job board itself decides almost nothing.
🔍 What the page commits to, and what it leaves out
I went to the source before writing anything. Here is the honest split between what is stated and what is not:
| Claim on the careers page | Stated? | What it tells a candidate in Sri Lanka |
|---|---|---|
| "Build the future of product integrations" | Yes | The product is integration infrastructure. API plumbing, not an app. |
| Fully remote, global team | Yes | Geography is not a filter on its face |
| Outcomes over hours | Yes | Suggests async tolerance, but says nothing about meeting load |
| Open source, "transparency, community and developer friendliness" | Yes | Your work is publicly inspectable before you apply |
| 11.7k GitHub stars | Yes | Real distribution, real community, real code to read |
| Specific role titles | No — the page links out to an Ashby board | You must click through; do not trust a summary |
| Salary bands or equity ranges | No | Nothing to anchor on. You will have to ask |
| Team size, hiring process steps | No | Unknown. Ask in the first call |
Bottom line: a careers page that says "fully remote" and lists no salary is not hiding anything unusual. Most seed-to-Series-A startups work this way. It just means the burden of asking the right questions sits entirely on you.
⏰ "Fully remote" is a timezone question before it is a location question
The Hacker News headline says SF and remote. That pairing matters more than most Sri Lankan applicants assume, because a company with a San Francisco centre of gravity schedules its meetings in Pacific time even when it calls itself global.
Run the arithmetic. Colombo sits at UTC+5:30 with no daylight saving. Here is the overlap between a 9am–6pm Colombo day and a 9am–5pm workday elsewhere, using September offsets:
| Their hub | Their UTC offset (Sept) | Their 9–5 in Colombo time | Overlap with your 9–6 |
|---|---|---|---|
| San Francisco | UTC−7 | 21:30 – 05:30 | ~0 hours |
| New York | UTC−4 | 18:30 – 02:30 | ~0 hours (2.5h if you work to 21:00) |
| London | UTC+1 | 13:30 – 21:30 | 4.5 hours |
| Berlin | UTC+2 | 12:30 – 20:30 | 5.5 hours |
| Singapore | UTC+8 | 06:30 – 14:30 | 5.5 hours |
Offsets shift when the northern hemisphere leaves daylight saving, so check the exact dates rather than trusting a remembered number. Our timezone converter and meeting planner do this for a specific date if you want the real figure before an interview.
The practical read: a European or Singapore-anchored remote team is compatible with a normal life in Sri Lanka. A Pacific-anchored one is a night shift unless the company is genuinely async. "Outcomes over hours" is the phrase that suggests the latter, and it is exactly the claim to test with a direct question.
🛠️ At an open-source company, the repo is the real application
This is the part most people skip. Nango's page leads with open source and cites 11.7k stars. That is not a vanity metric for a candidate. It means the codebase, the issue tracker, the review standards, and the maintainers' actual tone are all public, right now, for free.
What that lets you do before you ever fill in a form:
- Read the code and decide whether the work is interesting to you.
- Read closed PRs from outside contributors to see how maintainers treat newcomers.
- Ship something small and real — a doc fix, a failing edge case, a new provider config.
- Apply with a link, not a claim. "I wrote PR #1234" outranks any adjective on a CV.
A quick way to find where a project actually wants help, using the GitHub CLI:
gh repo clone NangoHQ/nango && cd nango
gh issue list --label "good first issue" --state open --limit 20
gh pr list --state merged --limit 20 --json author,title
That last command shows you who is getting merged. If the merged list is all core-team logins, outside contributions are decorative. If it has strangers in it, the door is open.
Key takeaway: for a Sri Lankan engineer with no US degree and no famous employer on the CV, a merged pull request in a repo with thousands of stars is the single cheapest credential available. It costs a weekend and it is verifiable by anyone.
💰 Questions to settle before you say yes
Since the page publishes no compensation information, these are the ones I would ask on the first call. Get the answers in writing:
- Employment structure. Direct employee, employer-of-record, or independent contractor? Each has different tax and paperwork consequences in Sri Lanka.
- Currency and payment rail. USD or EUR? Paid to which kind of account?
- Is pay location-adjusted? Some global companies pay one global band; others adjust by country. This can be a 2–3x difference for identical work.
- Core hours. Are there mandatory synchronous hours, and in whose timezone?
- Equity. If offered, what is the strike price, the vesting schedule, and what happens to unexercised options if you leave?
On the money side, a USD figure is not a Sri Lankan figure until you take it through conversion and fees. Our freelancer USD–LKR calculator shows what actually lands in a local account after the transfer service takes its cut, and the outward and inward remittance rules are worth reading once rather than discovering later.
🚀 The signals that separate real remote from remote-in-name
One listing is one data point. The pattern is what you should be filtering on. Companies that genuinely hire globally tend to show most of these:
| Signal | Real remote | Remote in name |
|---|---|---|
| Written culture | Docs, RFCs, public issues | Everything decided in calls |
| Job posts | State the timezone band explicitly | "Remote" with no constraint listed |
| Hiring history | Team page shows many countries | All one metro area |
| Meetings | Recorded, agenda-first | Attendance is the culture |
| Output measure | Shipped work | Hours visible on Slack |
Nango's page ticks the open-source and fully-remote boxes on its face. The rest you verify by reading their public repository and asking direct questions, not by trusting the copy.
💡 What this means for you
If you are in Sri Lanka and want this class of job, the sequence is not "apply and hope."
- Filter by timezone first. European and Asian hubs are livable. US Pacific is a night shift unless async is real.
- Pick two or three open-source dev-tool companies whose product you would actually use, and start reading their repos this week.
- Ship one merged PR before you apply anywhere. It changes the conversation from claims to evidence.
- Ask the money and structure questions early. A company that answers them plainly is telling you something good about itself.
- Do the LKR maths before you negotiate, so you know what a number means where you live.
The listing that prompted this post will be filled or expired soon enough. The method outlived it before I finished writing.