全职 Senior Software Engineer 工作, 薪水, HealthMetrics Selangor 公司招聘中 - Ricebowl

About HealthMetrics

HealthMetrics is a leading health and benefits platform in Southeast Asia, serving members across Malaysia, Singapore, and Indonesia. Our Global Member App helps employees access healthcare, navigate benefits, and connect with providers across multiple markets. The Member Experience (MX) Pod owns the end-to-end member journey, from onboarding through everyday use.

About the role

We are hiring a Senior Software Engineer (Backend) to be the backend technical anchor of the MX Pod. You will partner closely with our Mobile Engineer, Pod Lead, and CTO to design, build, and operate the services that power the member experience for hundreds of thousands of users across three countries.

This is a high-ownership role. The pod is small and stream-aligned, which means you will have direct visibility into product decisions, architectural choices, and outcomes. You will not be a cog, you will be one of the people the company looks to when backend complexity needs to be solved well.

While this role is backend-primary, you will also work across the stack, contributing to our member-facing web UI (Angular 18) and our identity and login UI (Blazor WebAssembly). We want someone happy to own a feature from API through to UI, not someone who hands off at the controller.

What you will do

• Design and ship backend services in .NET, hosted on Azure and GCP, that power the Global Member App and our Unified Multi-Country Admin Portal.

• Own services end-to-end — from API design through deployment, observability, and on-call response.

• Solve multi-market complexity — data models, configuration, and integrations that work across MY, SG, and ID without becoming a tangled mess.

• Make architectural calls on feature flagging, eventing, caching, identity, and integrations (WhatsApp, mapping providers, healthcare partners).

• Raise the bar on engineering practice — code review, testing discipline, runbooks, documentation in Outline, and sensible CI/CD.

• Participate fully in the Agile sprint cadence (two-week sprints, refinement, planning, retros) using our Jira project (MA).

• Contribute across the stack — build and maintain web frontend features in Angular 18 (member portal) and Blazor WebAssembly (identity and login), so work ships end-to-end without always waiting on a separate frontend specialist.

• Pair with Mobile Engineering to design clean API contracts and resolve integration issues quickly.

What success looks like at 90 days

• Shipped at least one meaningful backend feature end-to-end.

• Built a clear mental model of the Global Member App service architecture and can answer most “how does X work?” questions for the pod.

• Established backend on-call coverage alongside the team, with documented runbooks for the services you own.

• Identified at least one area of technical debt or fragility and proposed a credible plan.

• Worked as part of the pod, not around it, visibly active in code review, pulled the Mobile Engineer and the Pod Lead into design decisions early rather than presenting finished work, and asked for help when blocked rather than disappearing into individual rabbit holes.

Required experience

• 5+ years of backend engineering experience, with at least 2 years at a senior level in a product company.

• Strong .NET / C# in production, with deep familiarity in RESTful API design, async patterns, and dependency injection.

• Solid database fundamentals — relational modelling, query optimisation, migrations, and operational awareness (read replicas, indexes, contention).

• Cloud experience on Azure and/or GCP — App Services, functions, identity, secrets management, messaging.

• Distributed systems mindset — you have designed for failure, thought about idempotency, and operated systems with real customers.

• Strong written communication. You can write a clear technical proposal, an honest post-mortem, and useful documentation.

• Comfort in a small, fast-moving team where you will be a primary decision-maker, not a junior contributor.

• Comfortable working across the stack. You can build clean, functional web frontend features. We use Angular 18, Blazor WebAssembly. Hands-on Angular experience is ideal, but a strong backend engineer willing to ramp is fine, and Blazor will feel natural given your C# background. You do not need to be a design or CSS specialist: backend depth is what we are optimising for, and we will trade frontend polish for it.

AI proficiency (required, not optional)

We expect every senior engineer at HealthMetrics to be fluent with AI-assisted development. Specifically:

• Active daily use of at least one agentic AI tool (Claude Code, Codex CLI, or equivalent) for non-trivial work — multi-file refactors, debugging, test generation, documentation.

• Comfort with both inline and agentic workflows — you know when an autocomplete suggestion is enough and when to delegate a larger task to an agent.

• Judgement. You can spot when AI output is plausible but subtly wrong, and you verify before trusting. You do not merge code you do not understand.

• Process awareness. You can describe your own AI workflow concretely: how you structure prompts, what you put in your context, how you review agent output, what you have learnt not to delegate.

• Bonus: experience setting up team-level AI infrastructure — custom skills, MCP integrations, repo-level ************* or equivalent, hooks, CI integrations.

We are not looking for “I have tried Copilot.” We are looking for someone who has genuinely changed how they work with AI tools and can teach others.

Nice to have

• Experience in healthcare, insurance, or fintech, especially in regulated multi-jurisdiction environments.

• Familiarity with Flutter or other mobile API consumers (you will be the backend half of the contract).

• Experience with feature flagging systems, A/B testing, or progressive rollouts.

• Experience with mapping APIs, push notifications (FCM), or OAuth providers.

• Hands-on Angular (16+) experience, or familiarity with component-driven frontend architecture and design systems.

• Something you have built and can walk us through in depth, a personal project, an open-source contribution, or a deep dive into past professional work (all equally welcome). We care that you understand and can reason about what you built, not whether it is public.

• Open-source contributions, technical writing, or talks.