
Hi there, I'm
Ishrat Pinky
Full-stack developer. I care most about the part people actually touch.
What I actually do
Full-stack, but the frontend is where I'm opinionated. I build interfaces that hold up under real users, real data and real deadlines.

A fairly accurate depiction of the setup.
Languages
Frontend & mobile
Backend
Data
Ops & tools
Six years of shipping
Currently a full-stack engineer at Princess Cruise Lines.
Full Stack Engineer
Princess Cruise Lines
Building and maintaining full-stack features end to end — Java, Spring Boot and Hibernate on the server, React on the screen.
Remote work & personal projects
Independent
Remote client engagements and my own builds, deployed and live rather than sitting in a repo. Most of what's in the next section came out of this.
Full Stack Software Developer
Quad Theory Ltd & others
Full-stack web apps in React, Node.js and TypeScript. WCAG-compliant e-commerce, payment gateways, and MarTech plumbing (Google Analytics, Tag Manager).
Full Stack Developer
TS360 Test Automation
Chrome extensions and automation frameworks with Node.js, React and Selenium. Wired up CI/CD on GitHub Actions.
Software Developer
EON Group of Industries
HR management systems used by 1000+ employees, plus e-commerce modules with secure payments and real-time syncing.
Things I've shipped
Real builds, not mockups. Most are live — click through.
Nexus Dashboard
Admin template with an AI assistant and a charting system. The one that nearly broke me — and the reason I now respect virtualised tables.
Meridian Travel
Travel booking platform with live Leaflet mapping and dynamic pricing.
Juicy Fruits Merge
Physics merge game built on Matter.js. CrazyGames turned down v1, so I went back and rebuilt the mechanic rather than polishing the version they rejected.
Hulu 2.0 Clone
Streaming catalogue wired to the live TMDB API.
LinkedIn Clone
Pixel-accurate rebuild of the feed and profile mechanics.
Button Studio
A pile of hover states and micro-interactions, built purely because I enjoy it.
How I got here
Four stops, in order. The interesting part of each one is what went wrong.
The div that would not centre
HTML and CSS, learned the slow way. Three days on a layout I could now write in three minutes — but I have never once forgotten how the box model works.
Making it move
JavaScript, the DOM, and the first time I shipped something that broke in a browser I had not tested. Learned to read a stack trace instead of guessing.
Learning to think in components
React rewired how I break problems apart. Also where I learned that state in the wrong place will follow you around for months.
Shipping things people use
Next.js, full-stack, real users. WCAG-compliant e-commerce, payment gateways, analytics plumbing. The work got less glamorous and much more satisfying.
I write things down
Mostly so I stop making the same mistake twice. Some of it ends up published.
Everyone calls me Pinky
The CV stops here. This is the rest of it — the things I make when nothing has to ship.

Cooking
The pot on the fire. I cook when a deploy goes badly — something slow, with too many steps, where the only thing that can go wrong is me.
Social Journal
The unedited version — days off, cooking, wandering about

Mochi, mid-contribution.
A small Flappy Bird I built. Fly through the pipes, collect the panels.
Entirely optional. It is here because I enjoyed making it.
That's the whole trail.
Need someone to build the part people actually touch? Or just want to argue about whether the cat counts as a contributor?
