<YC />
CV.pdf

Profile

About Yeremia Chris Saragi

Frontend-heavy software engineer with 4+ years shipping production web apps in health-tech and logistics. I build in React/Next.js and Vue/Nuxt with TypeScript, and I'm most useful on complex, data-dense products: FHIR-based clinic systems, AI-assisted clinical notes, and logistics dashboards comparing live rates from 15+ couriers. Comfortable taking a feature from Figma and API contract to production. I use AI tools daily, and I review every line before it ships. Based in Batam, Indonesia, working remotely.

Get in touch
Open to opportunitiesYCS
Portrait of Yeremia Chris Saragi
Batam, Indonesia · Remote
Role & focusSoftware Engineer · Frontend-Heavy — frontend craft with API and data integration
HealthcarePrimaKu web platform (clinical + catalog)
LogisticsMulti-carrier shipping (KiriminAja)

I'm open to Software Engineer roles (frontend-heavy) — product platforms, clinical systems, or teams that want clean frontend work with real API and data ownership.

My Journey

Full-time roles · overlap is intentional
  1. Before 2022Self-taught

    Web foundations

    I taught myself web development — HTML, CSS, JavaScript, and enough backend context to read APIs and data flow before my first full-time job.
  2. Jan 2022 – May 2023iCreativeLabs · PT Idekreatif Menusa Teknologi

    Consultancy delivery

    I shipped client web apps, admin dashboards, and hybrid mobile UI in React, Next.js, Vue, and React Native.
  3. Jan 2023 – Apr 2024KiriminAja · full-time

    Logistics control room

    I owned Vue/Nuxt UI for multi-carrier shipping — rates, manifests, and high-density ops flows.
  4. Dec 2022 – PresentPrimaKu · full-time

    Pediatric health platform

    I own frontend architecture for PrimaKu's web platform — shared UI, REST, auth, and clinician plus family-facing surfaces.
  5. Jun 2025 – Jul 2026Mazecare · full-time

    Clinic & hospital EMR/HIS

    I built patient-lifecycle UI on an AI-native EMR/HIS with Vue 3, Nuxt 3, GraphQL, and FHIR.

Process

How I work

I work in an AI-era loop: research and plan with AI, track work in Linear or Jira, review agent PRs on Vercel previews, then merge when quality checks pass.

Editor

AI agents

  • Cursor cloud agents
  • Grok Bot
  • Hermes Agent

Planning

  • Linear
  • Jira

Ship

  • GitHub
  • Vercel preview deploys

Quality

  • lint
  • typecheck
  • tests
  • Lighthouse
01

Research and plan with AI

I sketch scope, constraints, and approach with AI before anything hits a backlog — so tickets start with context, not guesswork.

Context before code

02

Capture as a ticket

The plan becomes a Linear or Jira ticket with clear acceptance criteria. That ticket is the source of truth for humans and agents.

Linear · Jira

03

Agent builds the PR

A Cursor cloud agent (or Grok Bot / Hermes Agent when it fits) implements on its own branch and opens a PR with a logic summary — never a direct push to main.

Branch · PR · logic summary

04

Review on the preview

I read the logic summary, exercise the Vercel preview, and request changes until the UX and architecture match what I want.

Vercel preview · I decide

05

Merge and promote

When lint, typecheck, tests, and Lighthouse are green, I merge to development and promote to main for production.

Checks · development → main

AI does

  • Drafting code
  • Refactors
  • Tests
  • Research
  • PR summaries

I do

  • Scope and priorities
  • Architecture and UX decisions
  • Review
  • Merging
The /lab chat redesign went from a phone screenshot to a ticket, an agent-built PR with before/after screenshots, my review, and a merge the same evening.

AI handles repetitive drafting; I focus on scope, architecture, review, and product decisions.