DENG YI JIN

Kuala Lumpur, Malaysia

Work

Engineered for Production

I build and operate software where failure has a cost: lending, payments, compliance, and the glue between them. Clear boundaries, measurable behavior, and code that survives the next person who touches it.

Work history

Two places that define how I show up.

CurrentFull stack developer

Truestack Technologies

Full stack, with the boring parts taken seriously.

I ship features across UI, services, and the small infra decisions that keep releases calm. The context is production-shaped: move carefully where it matters, move clearly everywhere.

  • Across the stack

    From the shape of data to the shape of screens: one person keeping the thread so nothing hides in the handoff gap.

  • Under constraints

    Correctness and traceability where the domain demands it, not polish swapped for rigor.

  • Through to delivery

    Implementation to release: pairing when it helps, notes when the next reader needs them.

PreviousFull stack developer · Part-time

ELVTD

Client work where the screen had to feel dimensional.

Part-time on a shipped client build: heavy Three.js and motion, inside a team that still had APIs and deadlines. The job was to make the visual layer believable and performant, not just pretty.

  • Three.js & motion

    Scenes that read well without tanking the frame, balancing budget, readability, and what actually goes live.

  • Client rhythm

    Someone else’s brand and timeline: scope you negotiate, then finish.

  • Stack in context

    Frontend with backend in the room. No UI that pretends data and auth aren’t real.

Key systems

Across roles, the shape repeats: products that move money or data under rules, not demos that hope for the best.

SaaS platforms

End-to-end product surfaces with auth, workflows, and real admin needs, not just the happy path.

Payments & money movement

Flows where idempotency, reconciliation, and audit trails are features, not afterthoughts.

Infra & integration

Services, databases, and boundaries that stay legible when load and scope both grow.

High-pressure builds

Clock on, scope tight

Hackathons trained a default: cut scope, keep what works, ship something a judge can click, not a story deck.

  1. 01

    ETH Global

    Global Web3 sprints

  2. 02

    ETH KL

    Local innovation stage

  3. 03

    Alibaba Hackathon

    Enterprise-focused builds

  4. 04

    AmBank Hackathon

    Finance & infrastructure