Open to work

Software engineer building
dependable full-stack
web applications.

Muhammad Rienchy Razak Simatupang  ·  Software Engineer

Fifth-semester Informatics student in Depok, currently on the backend track of Maxy Academy’s Digital Career Bootcamp. I care about building software that works the way it should — fast, correct, and easy for the next person to pick up. I enjoy the parts where the hard problems live: keeping data consistent, making systems behave under load, and writing code that is clear enough to trust.

How this page reached you200 OK
01
CLIENT
Your browser requests the route
2 ms
02
ROUTE
Next.js resolves it statically
7 ms
03
POLICY
Row level security filters the rows
11 ms
04
QUERY
Postgres returns published records
18 ms
05
RESPONSE
Rendered and sent back to you
24 ms

Not an illustration. This is the request that served the page you are reading, and the policy step is the reason you cannot see my unpublished drafts.

01 / Selected work

4 projects, 4 different problems.

Curated rather than collected. Each one exists because it taught me something I could not have read.

02 / Stack

What I actually reach for.

Everything listed here appears in a project on this page. Nothing is here because it looks good in a list.

Backend

  • Node.js
  • Express
  • PHP
  • Laravel
  • Python

Database

  • PostgreSQL
  • MySQL
  • Redis
  • Supabase

Frontend

  • JavaScript
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS

Infrastructure

  • BullMQ
  • PWA
  • Vercel

Tooling

  • Jest
  • Git
03 / About

A short version.

I am in my fifth semester of Informatics Engineering at Universitas Pancasila, and I am currently on the backend track of Maxy Academy’s Digital Career Bootcamp.

Software engineering is what I want to do. I like the whole arc of it — turning a messy real problem into something that runs, then making it solid enough that other people can rely on it. The parts that pull me in most are the ones with real consequences: a payment that must not run twice, a request that reaches the right place and nowhere else, data that stays consistent when things happen at once. Getting those right is the craft I enjoy.

I write code to be read. I explain why something is there, I name things for what they do, and if a piece is clever I rewrite it until it is just clear — because the next person on the project (often future me) should not have to reverse-engineer my intent.

I am looking for a backend internship where I can build real systems alongside people who will point out what I got wrong, because that is how I get better fast.

4
Projects, curated
from fifteen
2
Languages shipped
server side
89.9%
Coverage on the
money path
0
Numbers on this site
I cannot defend