Software Engineer · Developer · Builder
I MAKE
COMPUTERS
DO THINGS.
I'm Maximus — a software engineer who turns ideas, designs and unnecessarily complicated requirements into software people can actually use.
// yes, it works on my machine.
So...
who is Maximus?
A little introduction
A software engineer who spends most of his time convincing computers to cooperate.
I build web and mobile experiences with React, React Native, Next.js and TypeScript — and occasionally make things look pretty with Figma.
I've been writing software professionally since 2019, working across frontend development, mobile applications, UI/UX and full-stack systems.
I like taking complicated ideas, breaking them into smaller problems, and turning them into software that people can actually use.
Web
Interfaces that look good, behave properly, and don't require users to read a 40-page manual.
Mobile
Mobile experiences designed to feel natural instead of feeling like a website squeezed into a phone.
UI / UX
Because software can be functional without looking like it was designed in 2007.
My usual workflow
Basically, I turn “someone should build this” into “here, it's done.”
I turn ideas into
working software.
Capability / 01
Connecting frontend, backend, databases and APIs into systems that work together instead of starting an argument with each other.
// Frontend talks. Backend listens. Database remembers.
The short version
Give me an idea, a problem or a “can we build this?” and I'll probably start opening my laptop.
The tools
behind the madness.
Frontend
Mobile
Backend
Database
Design
Tools
Developer + Designer
I don't believe developers should only care about making things work.
I like making them work well and look good too.
// Current status: still learning
// Stack overflow is technically part of the stack.
A few years of
making things.
Software development has never really been one straight line for me. It's been a gradual expansion from interfaces, to mobile, to design, to backend systems — and plenty of debugging along the way.
The Beginning
Professional Software Development
Started the professional journey into software development — learning how to turn ideas into interfaces, features and, eventually, entire systems.
Frontend Development
Building for the Web
Focused heavily on frontend development, creating responsive interfaces and learning that making something work is only half the job.
Web + Mobile
Expanding the Playground
Moved beyond the browser and into mobile development, working with cross-platform technologies and learning to think about experiences across different devices.
UI / UX
Making Things Look Intentional
Design became a bigger part of the process — working with Figma, layouts, responsive behaviour and the small details that make interfaces feel polished.
Full-Stack Development
Going Deeper
Started working more across the entire stack — connecting interfaces with APIs, databases and backend systems instead of stopping at the frontend.
Software Engineer
Still Building
Today, I work across frontend, mobile, UI/UX and full-stack systems — constantly learning, experimenting and occasionally asking the computer why it decided to stop cooperating.
Current status
Still learning.
Still building.
Still debugging.
When I'm not coding,
I'm probably...
Doing something that has absolutely nothing to do with debugging JavaScript.
Mostly.
Fantasy Worlds
Lord of the Rings, Narnia and any universe where the world-building is good enough to make me forget I have work tomorrow.
Gaming
Because apparently spending hours solving problems in code wasn't enough. Sometimes I need to solve completely different problems on a screen.
Design
Figma, Photoshop, Illustrator — basically, if something looks slightly wrong, there is a good chance I'll notice it.
Roads & Mountains
There is something about getting away from the screen, getting on the road and remembering that the world actually has pretty good graphics.
Outside the IDE
I like building things.
Software. Designs. Ideas.
Sometimes unnecessarily complicated things.
// It's probably a feature.
My philosophy
Good software
isn't just code
that works.
It's software that solves the right problem, feels good to use, and doesn't make the next developer wonder what kind of person wrote it.
Make it useful.
Good software solves a real problem. The technology is important, but the reason behind using it matters more.
Make it simple.
Complex problems don't always need complicated solutions. I like removing unnecessary complexity wherever possible.
Make it feel good.
People interact with software. Good experiences should feel intuitive, responsive and intentional.
Keep learning.
Technology changes constantly. Staying curious is part of the job — and honestly, part of the fun.
The simple version
Build things that are useful.
Make them beautiful.
Keep them simple.
// And try not to break production on Friday.
If that sounds like the kind of person you'd want building something with you...
Let's talkHave something interesting in mind?
Let's build
something.
Have an idea, a problem that needs solving, or something that should probably exist but doesn't yet?
I'd love to hear about it.
Drop me a line
hello@itsmaximus.in
Open to interesting problems, ambitious ideas and conversations that start with "Hear me out..."