The Market Is Different Here
A lot of career advice for software engineers is written for Silicon Valley. The advice isn't wrong, but it doesn't always translate to Southeast Asia, where the industry is younger, the talent pool is growing fast, and the problems are genuinely different.
I've worked in Malaysia and Indonesia, across banking, fintech, and consumer software. Here's what I've observed.
English Is a Professional Multiplier
In the SEA tech market, English is your access card to international collaboration, remote opportunities, and technical literature. Almost all documentation, most conference talks, and most technical writing that matters is in English.
This doesn't mean engineers who struggle with English are less capable — I've worked with brilliant engineers who communicate imperfectly in English and write excellent code. But in terms of career trajectory, investing in written and spoken English has a disproportionate return. The ability to write a clear technical spec, a cogent pull request description, or a thoughtful Stack Overflow answer is underrated.
Breadth Early, Depth Later
Early in my career, I tried to be useful everywhere. Frontend, backend, mobile, database, deployment — I took on whatever came up. This felt scattered at the time, but in retrospect it was invaluable.
Breadth gives you:
- The ability to reason about a system across layers
- Empathy for the engineers you collaborate with
- The vocabulary to communicate with product, design, and infrastructure
- A map of where you want to go deep
After a few years, the engineers who stand out are not the ones who can do everything adequately — they're the ones who can do something exceptionally well and reason about everything else. Build breadth first so you know what to go deep on.
Fintech Is a Great Sector to Start In
If you're early in your career and choosing between sectors in SEA, financial services is worth considering. The reasons:
Code quality expectations are high. A bug in an e-commerce checkout annoys customers. A bug in a payment ledger loses money. This forces rigour.
Scale is real. Malaysian banks and Indonesian fintech companies process millions of transactions daily. The engineering problems — distributed systems, consistency, latency — are genuine at this scale.
The domain knowledge compounds. Understanding financial products, regulations, and compliance takes time but sticks. Engineers who combine technical skill with domain expertise are rare and valuable.
The downside: financial services can move slowly. Regulations, legacy systems, and risk aversion can make shipping frustrating. Know what you're signing up for.
The Craft vs The Career
There's a tension between getting good at the craft and managing your career. The best engineers I've worked with are obsessed with the craft — they read papers, they experiment, they care about correctness and elegance beyond what's required to ship the feature.
But craft alone doesn't advance a career. In most organisations, visibility matters. That means: write things down, explain your decisions, share what you learn, and take on work that exposes you to senior engineers and decision-makers.
The engineers who grow fastest are craft-obsessed AND communicate well. Pick both.
Side Projects and Open Source
Side projects taught me things no day job could. Building something from zero — deciding the architecture, setting up infrastructure, writing all the tests, doing the deployment — gives you a complete picture that working on a slice of a large system doesn't.
Open source contribution has a similar effect, with the added benefit of working with engineers whose priorities and standards might be different from your employer's.
My advice: keep side projects small enough to finish. An abandoned project teaches less than a shipped one. Build something that solves a problem you actually have, with technologies you want to understand better.
Remote Work Changed the Equation
Since COVID, the SEA tech market for remote engineers has matured significantly. You can now realistically work for companies based in Singapore, Malaysia, or Europe from Kuala Lumpur or Jakarta. Remote work has compressed salaries upward in lower-cost markets and opened opportunities that didn't exist before.
To compete for remote roles at international companies, the bar is higher: communication matters more (you're not in the room), autonomy matters more (nobody is watching over your shoulder), and English matters more (your async writing is often the only impression you make).
The One Thing
If I had to distill seven years into one piece of advice: solve real problems and show your work.
Build things that work. Write about what you built. Show the code. Help other engineers with the problems you've solved. Expertise compounds, reputation compounds, and in a market that's growing as fast as SEA's tech sector, the engineers who show up consistently and do good work don't struggle to find opportunities.
The opportunity is real. The market is growing. The problems are interesting. Show up and build.