I AM Pratik Sahoo

‣ Built a game in a weekend with two friends. We survived each other.

‣ You play as an infection spreading through a city. Wholesome stuff.

‣ Infected humans keep the chain going — it's basically viral marketing, game edition.

‣ Learned a ton about rapid prototyping and what sleep deprivation does to code quality.

‣ Freelanced as dev, built localization and procedural asteroid generation from scratch.

‣ Translated designer dreams into code that actually ran (This line is AI Generated, and I want to keep it).

‣ Project was cancelled before release. The asteroids live on in our hearts.

‣ Unreal practice project, built for fun and to figure out what all the UEC++ fuss is about.

‣ Tried replicating Unity's component system in Unreal. It went okay. Mostly.

‣ Another Unreal learning project, saw it in a tutorial, thought it looked fun, was right.

‣ May expand it someday. (I won't. But I might.)

‣ Udemy course project focused on animations, because making things move properly is harder than it looks.

‣ Simple by name, humbling by nature.

‣ A personal project I can't talk about. Yes, it's actually interesting. No, that's not just something people say.

‣ World-building is in progress. Features are being built. Details are staying classified.

‣ Building gameplay and backend features, basically making sure the game actually works.

‣ Shipped contests, achievements and other things that make players feel accomplished.

‣ Wired up backend services and APIs so the game doesn't fall apart in production (fingers crossed).

‣ Dabbled in shaders, mostly breaking them, occasionally making something pretty. This is still new for me.

‣ Stepped into backend territory with LLM help and management's permission. A true team effort.

‣ Survived a live production environment and learned more in months than years of tutorials.

‣ Worked as a Lead Engineer for Rovio's Battle Bay. 

‣ Managed a team of four. We shipped things. On time, mostly.

‣ Juggled designers, artists, QA and data folks without losing my mind (mostly).

‣ Built a CI/CD pipeline so builds stopped being everyone's least favorite ritual.

‣ Kept AWS instances alive and behaving. It's more exciting than it sounds.

‣ Fixed bugs, shipped features and kept the lights on.

‣ Client-side work for Carry1st, in and out like a professional.

‣ Designed and built a new game mode called "Miner's Escape."

‣ Integrated everything cleanly into the existing codebase. No duct tape.

‣ Worked on gameplay mechanics and core features smooth enough that nobody complained.

‣ Made designer-friendly tools so they could iterate fast and stop bugging engineering.

‣ Led code reviews and mentoring — yes, even the painful ones.

‣ Built client and server for Boom Busters, full stack, full chaos. One of my first projects 

‣ Integrated Photon to make multiplayer work without people rage-quitting (the lag, not the game).

‣ Came out the other side with way more experience than I went in with.

‣ Built a turn-based stealth puzzle game for my final year project. Hitman GO was the vibe.

‣ Teamed up with a batchmate, two devs, one repo, zero merge conflicts (a lie).

‣ Dug deep into turn-based systems, stealth mechanics, and why players never read tutorials.

‣ Built a Unity Editor tool to copy multiple components between GameObjects, because doing it manually is a crime.

‣ Started as a fun side project, ended up being genuinely useful. Surprised me too.