Skip to content

I build stuff. Mostly for fun. A horror game in an abandoned asylum. Birthday cards for friends. An alarm clock that runs away when you get close. And a billing engine that refuses to charge anyone twice. That one, I was locked in for.

I build the parts of software nobody screenshots. APIs. Data models. The rules that keep state honest. Then I make the part people do see worth looking at.

Hashim Mohamed grinning, standing with one hand in a pocket

Hashim Mohamed T.A. — full-stack developer, backend first

★ 3× hackathonpodium finishes

See what I’ve made ↓Selected work ↓Résumé (PDF) ↗
(02) AboutKerala, India · IST
Hashim Mohamed sitting on a lakeside wall in sunglasses, grinning, with mountains behind
Fig. 02 — Off duty

About meAbout

Ninety percent of the time, I don’t take stuff seriously. The other ten, I lock in.

There’s a switch for that. Top right. Go on.

Most of the time I keep it light. When it matters, I lock in. You’re reading that mode.

I study computer science at Model Engineering College, Thrikkakara. Class of ’28.

I learned backend on a real codebase: a Spring Boot internship at Linsys, building services for a healthcare platform. Production code. Mildly terrifying.

Then Spaceborn made me Chief System Architect. The whole system was mine: the design, the API contracts, the deploys.

The rest of the time, I’m at a hackathon or knee-deep in a pile of scraps.

Computer science at Model Engineering College, Thrikkakara, graduating 2028.

I started on production code: a Spring Boot internship at Linsys Innovations, building REST APIs and PostgreSQL-backed services for a healthcare platform.

At Spaceborn I was Chief System Architect, responsible for system design, API contracts, technology choices and deployment.

Backend first. Then the frontend, done properly.

Studying
B.Tech, Computer Science · Model Engineering College, Thrikkakara
2024 – 28
Architected
Chief System Architect · Spaceborn
Oct 2025 – Jan 2026
Interned
Software Developer, Spring Boot · Linsys Innovations, Ernakulam
Jun – Oct 2024
Based in
Kerala, India · IST, UTC+5:30
(03) Work2024 – 2026

Stuff I madeSelected work

Four of them. Picked for the decision under each screenshot.

Four projects, chosen for the engineering decision inside each.

  1. STVE

    2026HackathonExpress · PostgreSQL · Prisma · Next.js

    Soil sensors lie. Not on purpose.

    A stuck probe keeps reporting “moist” while the field dries out. The irrigation system believes it, because it believes everyone.

    So STVE believes no one. Every reading gets checked against its own history, its neighbours, and physics. Half the score comes from the neighbours.

    If the whole zone changes, that’s probably the weather. If one sensor does, that’s probably the sensor. It gets flagged, and a maintenance ticket opens itself.

    Problem. Automated irrigation trusts every soil sensor equally. A stuck or drifting probe silently corrupts the decision.

    Decision. A trust layer between ingestion and automation. Each parameter is scored 0 to 1 as 0.3 temporal + 0.5 cross + 0.2 physical. Agreement with the zone carries the most weight.

    Result. Anomalous sensors are isolated and ticketed automatically, except a FIELD_EVENT, where the whole zone moved together and the change is real.

    Code ↗ (STVE, opens in a new tab)

    half the score is peer pressure

    STVE dashboard for sensor s_40: Anomalous, trust score 65%, severity High. Probe reliability bars show temperature at 31%. Root cause analysis lists a frozen sensor probe and a zone mismatch.
    Fig. 3.1 — Sensor s_40, flagged: frozen probe, out of step with its zone
  2. BrightLoop

    2026Odoo HackathonFastify · PostgreSQL · Next.js

    Subscription billing has one job. Charge people once.

    Ours runs on a button. Press it twice, press it ten times. A period still only gets billed once.

    Not because the code remembers to check. Because the database refuses.

    Already billed? The run marks it skipped and moves on. Every status change gets checked by the server too.

    Problem. A billing run can be retried, double-clicked or overlap a scheduled run. None of that may produce a second invoice.

    Decision. A unique index on (subscription_id, period_index) makes a duplicate invoice a constraint violation, not a code path someone has to remember.

    Result. Idempotent billing. A duplicate is caught inside a savepoint and recorded as a skipped item, so one bad row never fails the run. Every lifecycle transition is validated server-side.

    Code ↗ (BrightLoop, opens in a new tab)

    run billing twice. get one invoice.

    BrightLoop billing runs screen: 128 subscriptions due today, expected revenue $18,492, and a table of two billing runs, one completed and one partially failed.
    Fig. 3.2 — Billing runs, on the frontend’s built-in mock data
  3. Tetherverse

    2026Excel PlayPhaser 3 · Matter.js · Next.js · TypeScript

    A physics platformer. You swing, you launch, you fall. A lot.

    The leaderboard was the problem. Scores came straight from the browser. Which means anyone could just… type one.

    Now the server opens every run, hands out the level seed, and checks the score that comes back. It has six different ways of saying no.

    Can someone determined still fool it? Yes. The real fix is replaying the run on the server. Not done yet.

    Problem. The client invented scores and posted them. The leaderboard trusted the browser.

    Decision. Server-managed runs. POST /runs issues a run id and the level seed; a score is only accepted against an open run the caller owns, and every rejection has its own status.

    Limit. The simulation still runs in the browser, so a determined client can compute a plausible score. Deterministic replay on the server, from the seed and the input log, is the real fix.

    Play it ↗ (Tetherverse, opens in a new tab)Code ↗ (Tetherverse, opens in a new tab)

    six ways to say no

    Tetherverse main menu: the title over four painted worlds, Verge, Bloom, Kiln and Null, with a cyan play button and the line Hold to grapple, release to launch.
    Fig. 3.3 — The menu. Four verses: Verge, Bloom, Kiln, Null
  4. StoryWeave

    2025Grab A Pi Hacknight · 1st prizeFastAPI · WebSockets · GPT-2 · React

    A story everyone writes at once. You add a line, your friends add lines.

    Every fifth line, GPT-2 adds one too. It never helps.

    That’s the point. One minute it’s a romance. Then the wedding cake explodes.

    Built in 24 hours. Won first prize.

    Problem. Several writers, one story, live.

    Decision. FastAPI WebSocket rooms broadcast every addition. A per-room counter triggers a GPT-2 plot twist on every fifth one, appended to the story automatically.

    Result. Built in 24 hours. First prize.

    Code ↗ (StoryWeave, opens in a new tab)

    1st prize · 24 hours

    A StoryWeave room. The story reads: Anu opened a tiny bakery in Fort Kochi. Every morning, Rahul came in for one cardamom bun. Meera, who ran the tea stall across the road, noticed he never ate it. He was leaving them on Meera's windowsill. Tonight, he finally left a note with the bun. He opened the note and saw Rahul giving it to his wife.
    Fig. 3.4 — Five lines from three of us. The last one is GPT-2’s
(04) ToolboxIndexed by where it was used

What I useToolbox

No bars. No percentages. Just where each one actually got used.

Each tool, and the projects it was used in.

Services06

Java · Spring Boot
Used in Linsys
Node.js · Express
Used in STVE
Fastify
Used in BrightLoop, Tetherverse
Python · FastAPI
Used in StoryWeave
WebSockets
Used in StoryWeave
TypeScript
Used in BrightLoop, Tetherverse

Data03

PostgreSQL
Used in Linsys, STVE, BrightLoop, Tetherverse
Prisma
Used in STVE, Tetherverse
Supabase
Used in StoryWeave

Postgres is under 3 of the 4

Interface04

React · Next.js
Used in STVE, BrightLoop, Tetherverse, StoryWeave
Tailwind CSS
Used in STVE, BrightLoop, Tetherverse
Phaser · Matter.js
Used in Tetherverse

Delivery04

REST APIs
Used in Linsys, STVE, BrightLoop
JWT · role-based access
Used in BrightLoop
Docker
Used in Tetherverse
Cloudflare Workers
Used in Tetherverse

Also, from older projects not on this page: MySQL, MongoDB, Firebase, AngularJS.

(05) RecordHackathons, 2022 – 2025

Won stuff

Three podiums. Two finals. Every one of these passes says participant. We fixed that.

  1. Hackathon pass2025

    Operation Darknoon

    Participant2nd prize

    A cybersecurity hackathon.

  2. still in school for this one

Record

Three podium finishes and two finals, most recent first.

  1. MecLabs Hackathon

    2025
    1st prizeBridgio. Sign language to text and speech, live from a webcam.Code ↗ (MecLabs Hackathon 2025, opens in a new tab)
  2. Operation Darknoon

    2025
    2nd prizeA cybersecurity hackathon.
  3. Grab A Pi Hacknight

    2025
    1st prizeStoryWeave. The prize was a Raspberry Pi 4.Case study ↑ (Grab A Pi Hacknight 2025)
  4. MecLabs Hackathon

    2024
    FinalistFind Your Vibe. Random video chat for college students.Code ↗ (MecLabs Hackathon 2024, opens in a new tab)
  5. Dr. P. Thevannoor Hackathon

    2022
    FinalistMisFit. A safety app for stray-dog attacks, built in 24 hours.Code ↗ (Dr. P. Thevannoor Hackathon 2022, opens in a new tab)
(06) ContactKerala IST

Say hiContact

No contact form. Pick one of these and say hi. Tell me you came from here.

No form. Reach me on any of these.