Muhammed Anas / Software Engineer

Software Engineer — Backend & Platform

I build web systems, then take responsibility for how they are deployed, automated, and diagnosed.

01

Professional experience

Improving the paths that carry critical work.

Current role / healthcare software

Jul 2026 — Present

Camerin Innovate

Private / internal work

Software Engineer

Backend and data performance, module integration, and delivery improvements within a shared multi-tenant healthcare platform.

78%
fewer database round trips
70%
lower clinical-report latency
89%
smaller initial JavaScript payload
31%
faster CI workflow

Integrated Mortuary, Drug Indenting, CliniGrowth, and LifeGenX using shared platform patterns. Employer-owned implementation details are intentionally private.

02

Selected engineering work

Evidence over surface area.

Case study / 01

Healthcare platform integration and data-path performance

Applied shared platform patterns across four healthcare modules. Diagnosed a reporting bottleneck, used batched retrieval, verified output parity, then used a revert-and-remeasure loop to confirm the result.

NestJS · PostgreSQL · TypeORM · RBAC · tenant isolation

78%fewer database round trips70%lower reporting latencyEmployer-owned / internal implementation
Case study / 02

Delivery performance

Introduced route-level code splitting and deferred heavy PDF and chart dependencies. Parallelized tests, frontend build, and dependency/security checks in GitHub Actions.

Next.js · GitHub Actions · build and dependency checks

89%smaller initial JavaScript payload31%faster CI workflowEmployer-owned / internal implementation
Case study / 03

DevConnect

A shipped web product with application delivery carried through to containerization, reverse-proxy configuration, cloud deployment, storage access, and automated checks.

React · Node.js · Express · MongoDB · Docker · Nginx · AWS EC2 · S3 IAM roles · GitHub Actions

03

How I engineer

A practical method for change.

  1. 01

    Start with the real boundary

    Understand ownership, data flow, tenant boundaries, and failure modes before changing code.

  2. 02

    Measure the path

    Profile the actual request or build path, then make the smallest meaningful change.

  3. 03

    Verify correctness

    Use before/after measurement and output checks so faster does not mean broken.

  4. 04

    Make delivery repeatable

    Use containers, CI checks, and deployment discipline to reduce manual release risk.

04

About

Systems behind the interface.

I’m a software engineer from Kerala with a BCA background. My path moved from web applications toward the systems behind them: APIs, data paths, delivery workflows, deployment, and observability.

05

Contact

Let’s discuss the work that needs to hold up.