They Can Ship the Feature. The Interview Scores Them on a Phrasal Verb Instead.
Startups in Jakarta and Manila screen for English small talk, not code. The filter sorts by school and class, then calls it merit.
A candidate pushes clean code, closes tickets fast, and reads documentation in three languages. The recruiter screen still asks them to "walk me through your journey" and marks them down when the answer comes out stiff. The job needs none of that. The filter does.
English-fluency gates are quietly running hiring at startups across Jakarta and Manila. Not the English you need to read a Stack Overflow thread. The English you absorb from private schools, international curricula, and parents who could pay for it. The kind that sounds effortless on a founder's Zoom call because the founder learned it the same way.
The test measures the applicant pool, not the applicant
Technical screens for engineering roles increasingly run as unstructured chats. Tell me about yourself. What excites you about our mission. Recruiters call this culture fit. In practice it rewards whoever can improvise polished English under pressure, which tracks almost perfectly with where you went to school.
That is the trick. A phrasal verb you missed, a vowel you flattened, a pause that read as uncertainty, and a resume with real shipped work gets a soft no. The rejection email says "communication skills." The reason is an accent that didn't match the room.
Founders rarely do this on purpose. They hire people who feel easy to talk to, and ease feels like competence. The applicant who codes better but small-talks slower loses to the one who went to the same three universities as everyone already inside.
Fluency does the work class used to do out loud
Nobody at a Series A startup will put "must come from money" in a job post. English fluency does that quietly and legally. It sorts for the same people without naming them, then wraps the whole thing in the language of standards.
The irony is that most of these products serve users who don't speak boardroom English at all. The driver on the app, the seller on the marketplace, the merchant swiping the terminal. The team building for them gets picked for a polish those users never asked for.
Meanwhile the actual job runs on written English. Pull requests, async threads, documentation. That's a skill you can check with a take-home, a code sample, a timed task. A conversation about your "journey" checks none of it.
Remote work was supposed to crack this open. A coder in Bekasi or Bacoor could reach a team in another city without their accent entering the room first. Instead the video call put the accent back at the front of the line, and the first ten minutes decide the rest.
There's a fix, and it isn't complicated. Score the take-home. Read the code. Run structured questions everyone answers the same way, in writing if that's how the team works. Strip the open-ended chat that rewards charm over output.
Until then, the candidate who can build the thing keeps losing to the one who can describe building things in the right register. The offer letter goes to whoever sounds like the founder. The commit history belongs to whoever didn't get called back.
