Backend Engineer - Claims Automation

Overview

BJAK is creating automation tools that speed up insurance journeys for customers, with a strong focus on the claims experience where trust, transparency and smooth operations matter most. The team is looking for a Backend Engineer to strengthen claims visibility, reduce manual coordination, and automate follow-ups between customers, insurers and internal teams. This position is fully remote and will involve close day-to-day collaboration with engineering and operations teams based in Malaysia.

Mission

Your focus will be to design backend systems that make claim progress easier to track, streamline workflows, and remove operational bottlenecks.

Responsibilities

• Develop backend services that support claims tracking, workflow handling and automated status updates.
• Connect insurer updates, customer claims data and internal operational processes.
• Set up automation for reminders, escalations, follow-up monitoring and workflow changes.
• Strengthen system reliability through improved logging, monitoring and exception management.
• Troubleshoot issues in claims workflows and identify the underlying causes.
• Work with product, claims support, operations, QA, frontend and DevOps stakeholders.
• Create dependable systems that improve customer confidence throughout the claims journey.

Requirements

• Hands-on backend engineering experience in a production environment.
• Strong understanding of APIs, backend process flows and database systems.
• Comfort working on operational systems with complex workflow requirements.
• Solid debugging ability and a structured approach to solving problems.
• Attention to customer-visible status accuracy and operational detail.
• Ability to collaborate effectively with distributed, cross-functional teams.
• Practical mindset, ownership of work and openness to feedback.

What the ideal candidate brings

• A genuine focus on customer trust and operational dependability.
• Ability to reason through complicated multi-party workflows.
• Composure when working through ambiguity and operational complexity.
• Willingness to improve essential systems even when the work is not flashy.
• Interest in building robust backend foundations that can be relied on.

Not a fit for this role

• Engineers who prefer only standalone technical problems.
• Candidates who overlook operational context or the customer journey.
• People who get stuck when external dependencies are unclear.
• Engineers who avoid addressing the root cause of process issues.
• Those who are not comfortable working closely with operations teams.

Success in this role

• Customers get clearer insight into where their claims stand.
• Repeated manual coordination and chasing follow-ups decrease.
• Claims support teams become more effective in daily operations.
• Workflow failures are spotted and fixed more quickly.
• Claims infrastructure becomes more dependable and trusted internally.

Interview process

Candidates will be evaluated on technical strength, working style and the way they approach backend problem-solving. The hiring flow includes application screening, interviews and either a technical discussion or a coding assessment.