Senior Backend Engineer

Idataraya Sdn Bhd; Kuala Lumpur; On-site; MYR 180,000 - 300,000; Full time

Job summary

Idataraya Sdn Bhd in Malaysia is seeking a Senior Backend Architect to own the service architecture on client engagements. You will shape data models, define service boundaries, and make long-term design decisions.

You will write and review code every two to four weeks, and drive integrations to behave like real third parties. After go-live, you stay involved to address root causes and improve reliability.

Qualifications

• Several years building backend services relied on daily.
• Deep expertise in at least one server-side language.
• Strong experience with relational databases.
• Own data models through schema changes.
• Prudent judgement on complexity.

Responsibilities

• Design service boundaries and data models for a system that has to run for years rather than demo well.
• Write and review the code your team ships every two to four weeks.
• Take integrations to the point where they hold against a third party's real behaviour, not their documentation.
• Stay attached after go-live and fix the causes of what goes wrong.

Skills

Backend architecture

Server-side programming

Relational databases

Data modeling

Decision making

Job description

You own the service architecture on a client engagement: the data model, the boundaries between services, and the decisions that are hard to reverse later. Once it is live you are still the one holding it, which tends to change how you design.

What you will do

• Design service boundaries and data models for a system that has to run for years rather than demo well.
• Write and review the code your team ships every two to four weeks.
• Take integrations to the point where they hold against a third party's real behaviour, not their documentation.
• Stay attached after go-live and fix the causes of what goes wrong.

What you will bring

• Several years building backend services other people depend on daily.
• Depth in at least one server-side language and a relational database.
• Experience owning a data model through schema changes, not only consuming one.
• Judgement about when to keep something simple and when the complexity is genuinely needed.