Skip to main content

January 20, 2026

Ready for Singapore Remote: Notes From Jakarta

I'm based in Jakarta (GMT+7), ready for Singapore remote. Here's how I work, what I've shipped, and why remote work in the same timezone is the goal.

January 20, 2026·3 min read·
careerpositioningreflectionremote-worksingapore
Ready for Singapore Remote: Notes From Jakarta

I'm Alfa, a Fullstack AI Engineer based in Jakarta. Same timezone as Singapore (GMT+7). I've spent the last few years shipping production systems onsite and hybrid; I'm ready for Singapore remote full time, and open to freelance, part time, or contract work when the impact is real.

This is a post about how I work, and why remote work, especially when it's aligned with APAC hours, is the right fit.


Why Remote (and Why Singapore)

The practical reason: the teams and products I want to join aren't all in one city. Singapore remote keeps me in the same working day as the teams I care about, without the geography tax.

The real reason: I think well alone. My best work happens in long, uninterrupted blocks. I communicate more clearly in writing and diagrams than in consecutive meetings. I context switch badly. The office rhythm costs me more than it costs some of my colleagues.

This isn't a complaint about offices. It's an honest read of my own operating system.


What "Ready" Means

I'm not waiting on a vague future version of myself. Ready means concrete evidence:

1. Work that is legible.

Remote hiring is competitive. Your portfolio, your writing, your shipped systems have to do the work a physical presence would do. This site exists for that reason, not as decoration.

2. Writing that holds up asynchronously.

Distributed teams run on clear writing. If you can't explain a technical decision, document a system, or make reasoning visible in a thread, you're a liability remotely. I write here as practice and as proof.

3. Things in production.

Clinic payments at 100+ branches. An AI incident tool that cut diagnosis from ~120 minutes to under 10. Side products with real users. Evidence that I can take something from idea to shipped without a manager over my shoulder.

4. Visual shared understanding.

I sketch first: diagrams, Figma, models the team can see. That habit is how I learn systems fast and keep business context when the stack changes.


The Unglamorous Parts

Getting ready took longer than I wanted.

Years of day job intensity plus nights and weekends on portfolio, writing, and side projects. Months with no visible progress: just maintenance, just showing up, just keeping the writing habit alive.

Progress isn't always visible while it's happening. Then one day the stack of evidence is enough to say: ready.


What I Want People to Infer

Positioning isn't broadcast. It's inference. You want the right people to look at the work and infer the right things without a sales pitch.

The signal I'm aiming for: Fullstack AI Engineer in Jakarta, ready for Singapore remote, ships production systems, learns fast, thinks visually, cares about craft.

Specificity is scarce. Most portfolios are generic. If yours says one clear thing, it stands out.


Where This Goes

Primary goal: full time Singapore remote. Secondary: any paid work with real impact, whether freelance, part time, or contract, that moves a product or a team forward.

The path won't be linear. Some months will be faster. Some will feel still. What I know: the people I respect built positioning slowly, shipped imperfect things, and kept writing.

That's the plan.

Alfa


Discussion

Discussion is unavailable; Giscus is not configured for this build.