Idataraya Sdn Bhd

CI/CD Cloud Infrastructure as Code

DevOps Engineer at Idataraya Sdn Bhd in Kuala Lumpur who owns CI/CD pipelines, environments and releases (every 2–4 weeks) for several client systems, working embedded within delivery teams. Core technologies include containers, infrastructure as code, at least one cloud, and maintainable scripting.

Idataraya Sdn Bhd

2 weeks ago

Full Stack Engineer

A full stack engineer in Kuala Lumpur who owns features end to end on smaller systems — from data model and API to interface and release — working directly with the client and operating what they ship. Requires real experience on both sides of the stack and comfort with SQL and schema design.

Senior Backend Engineer

APACSenior

Senior backend engineer in Kuala Lumpur who owns service architecture on a client engagement: designing service boundaries and data models, shipping and reviewing code every 2–4 weeks, and staying responsible for integrations and fixes after go-live. Core stack: a server-side language and a relational database.

Idataraya Sdn Bhd

2 weeks ago

Backend Engineer: APIs, Integrations & Reliable Systems

Idataraya Sdn Bhd is hiring a backend engineer in Kuala Lumpur to build API endpoints and background jobs, integrate with third-party systems, and help shape the data model. The role emphasizes writing tests for a fortnightly release cycle, handling production issues, and reliable, clearly written communication.

Backend Engineer

Backend engineer in Kuala Lumpur building and maintaining the services behind live client systems: APIs, third-party integrations, and background jobs. Requires commercial experience with a server-side language and a relational database, with an emphasis on testing and handling failure cases.

Idataraya Sdn Bhd

2 weeks ago

Senior Backend Engineer: Architect Long-Running Services

APACSenior

On-site senior backend role in Kuala Lumpur: as Senior Backend Architect at Idataraya Sdn Bhd you own service architecture on client engagements — shaping data models, defining service boundaries, and making long-term design decisions, with hands-on coding/review every two to four weeks and post-go-live reliability follow-up.

Sdn