An engineering culture built on ownership
A small team that writes things down, owns what it builds and stays with it after go-live. This is how the work runs day to day.
How the work runs
Four habits shape every day here, in every team and at every stage of an engagement.
Written by default
You work mostly in writing: Slack threads, pull requests and Notion documents. Meetings are kept for decisions that need a live conversation. Core overlap hours are 10:00 to 16:00.
Small teams that own the outcome
Each engagement has a small team responsible for the whole result. The engineers who run discovery also build the system, deploy it and stay on to operate it.
Direct access to clients
You talk to clients yourself and visit their sites as part of discovery. You check software against how the work really happens, not against a requirements document.
Decisions where the knowledge is
The engineers closest to a system make the calls on it without escalating. Decisions that cut across teams go through a written proposal and an open review.
What we value in the work
The principles we apply in code review, in design discussions and when we hire.
Correct before complete
A smaller system that behaves correctly under production load beats a bigger one with open questions. You finish features rather than leave them half done.
Explicit before implicit
Behaviour lives in the code, not in conventions. You write down the assumptions the code cannot show, and you handle errors instead of letting them surprise someone.
Readable before clever
Clear code wins over compact code. The test is whether the next engineer can understand and change it without you in the room.
Operable before finished
You design systems to be monitored, diagnosed and recovered in production. Logs, metrics and runbooks are written with the code, not after it.
What the work looks like
What changes when the people who build a system are the ones who run it.
Across the whole stack
You work across the application, data and device layers. One engineer often ships a feature, keeps the pipeline behind it running and fixes the hardware integration it depends on. There is no separate frontend and backend team.
Production is the finish line
Work is done when it runs on client infrastructure and the client has accepted it. Progress is measured by acceptance, not by internal velocity.
You stay with what you build
The team that designs and builds a system stays responsible for it after go-live: incidents, improvements and capacity. There is no handoff to a separate support team.
Built for Malaysia first
FPX, DuitNow QR, Pos Laju integration and Bahasa Malaysia are primary requirements. Payment rails, address formats and local rules live in the data model, not in a localisation layer added later.
Your best work starts here
See the roles open now, or tell us what you do and we will reach out when one fits.