Onboarding
Set up the development environment, meet the engineering team, and familiarise with the codebase. Daily pairing with the assigned mentor engineer throughout this phase.

Ways in
Paid internship placements of three to six months for students currently enrolled in computer science, software engineering, or adjacent programmes. Real engagement work, supervised by a senior engineer, ending with a shipped feature and a team presentation.
See open rolesA predictable structure with defined checkpoints. The intent is steady increase in scope and autonomy across the placement.
Set up the development environment, meet the engineering team, and familiarise with the codebase. Daily pairing with the assigned mentor engineer throughout this phase.
Take a ticket from the active sprint backlog and deliver it to production. The mentor reviews pull requests and provides context on the system under change.
Take end-to-end responsibility for a feature: design the technical approach, implement, test, and deploy to production. This phase represents the core of the placement.
Present the delivered work to the engineering team. Six-month placements proceed to a second feature with expanded autonomy.
Work on live systems used by paying clients. Internal-only projects, demonstration builds, or disposable exercises are not assigned during the placement.
A senior engineer is assigned as mentor for the full placement duration. Daily contact in the first week, then regular weekly one-to-one sessions.
Access to the same repositories, tooling, and communication channels as permanent engineers. Placements are not segregated from the main engineering organisation.
Internships are paid. Transport costs to the Kuala Lumpur office are reimbursed for on-site attendance.
Currently enrolled in a computer science, software engineering, or related degree programme in Malaysia.
Available for a minimum of three months, with six-month placements preferred.
Practical programming experience in at least one language such as TypeScript, Python, or equivalent.
Demonstrated interest in production software operation, not only academic programming.
A short introduction and a link to something you have built and operated is enough to start a conversation.