Backend Engineer - Claims Automation (Remote, China)

🏢 Bjak · all Bjak jobs
📍 China
📅 Posted 2026-06-28 · via Himalayas
🏷 Remote-Senior-Backend-Engineer,Insurance-Automation-Engineer,Remote-Backend-Developer
Apply on original site ↗

BJAK is building automation systems that help customers move through insurance journeys faster—from quote to policy issuance, renewals, endorsements and claims.

We're looking for Backend Engineers based in China who can build the core systems that power claims automation. This role focuses on designing and implementing backend services that make claims processing faster, more accurate and less dependent on manual operations.

This is a fully remote position where you'll collaborate closely with our Malaysia-based engineering, product and operations teams to deliver reliable, production-grade systems.
The Mission

Build backend systems that automate insurance claims processing end-to-end, reducing manual handling, improving turnaround time and ensuring accurate, traceable and reliable claims outcomes.
What You’ll Own

-
Build backend services that power claims automation workflows end-to-end.

-
Design and implement logic for claims submission, validation, assessment, approval and payout processes.

-
Integrate with insurer systems, internal workflow engines and external data sources.

-
Manage complex claims rules including eligibility, documentation, fraud checks and approval conditions.

-
Improve APIs, data models, queues, retries and asynchronous processing for claims workflows.

-
Ensure accuracy, traceability and consistency of claims data across systems and states.

-
Debug production issues and perform root cause analysis for claims delays, failures or inconsistencies.

-
Work closely with product, operations, QA, frontend and DevOps teams to deliver end-to-end solutions.

-
Build systems that provide full visibility into claims status and lifecycle tracking.

-
Continuously improve system reliability, performance and scalability under high operational load.

What We're Looking For

-
Experience building backend systems in production environments.

-
Strong understanding of APIs, databases, distributed systems and backend architecture.

-
Ability to design and implement complex workflow or state-based systems.

-
Experience working with transactional, data-sensitive or operational systems.

-
Strong debugging skills for multi-step or data-heavy backend issues.

-
Experience with queues, async processing or event-driven architectures.

-
Strong focus on correctness, edge cases and system reliability.

-
Hands-on ownership mindset from design through production support.

-
Comfortable working with real business operations and constraints.

-
Practical, structured and open to feedback.

Bonus Points

-
Experience building claims systems, insurance platforms or fintech products.

-
Experience with workflow automation, orchestration engines or backend platforms.

-
Experience with event-driven architectures or distributed systems design.

-
Knowledge of Node.js, Python, Java or similar backend technologies.

-
Experience with messaging systems (Kafka, RabbitMQ, SQS or similar).

-
Familiarity with observability tools (logging, metrics, tracing, alerting).

-
Experience with cloud infrastructure and CI/CD pipelines.

-
Experience working in insurance, healthcare or other regulated industries.

-
Contributions to backend system design or high-scale production systems.

The Kind of Builder We Want

-
Deeply focused on correctness and reliability in complex workflows.

-
Hands-on engineer who enjoys solving real operational system problems.

-
Calm and structured when handling production issues and debugging.

-
Strong attention to edge cases, failure paths and data integrity.

-
Driven by real-world operational impact, not just feature delivery.

-
Thinks in systems, workflows and end-to-end process reliability.

-
Builds systems that operations and product teams can trust.

This Role Is Not For

-
Engineers who only want simple feature work without system complexity.

-
People who avoid production responsibility or debugging ownership.

-
Developers who ignore edge cases or transa

← All remote jobs