Programming Languages
- JavaScript
- TypeScript
About
Open with what you build and where your strengths sit. Two or three sentences is plenty — this is the paragraph most visitors actually read, so it should say something specific rather than list adjectives.
Follow with where your foundation comes from: the languages, the habits, the things you care about underneath the surface. Concrete beats impressive.
Close with what you are looking for, or what a client can expect from working with you. Keep the promises to ones you will keep.

Education
Formal study, plus the professional training that sits alongside it.
2022 – 2026
Your City, Country
Your University
A short description of the programme and what it covered. Mention the parts that are relevant to the work you want, not every module.
2025
Institution or Provider
Professional training, a bootcamp, or a certification. Say what it covered and what you built during it.
Skills
Grouped by where each piece sits in a project, from the language up to the tools around it.
Services
Freelance and collaboration work — from a responsive frontend through to the API and database behind it, built faster with AI in the loop.
Interactive interfaces in React, JavaScript and TypeScript that hold up on every screen size, wired up to your data through APIs.
Server-side logic and REST APIs with Node.js and Express, covering routing, validation and authentication.
Schema design and integration with SQL, PostgreSQL or MongoDB, so your data is stored in a shape that lasts.
Working with AI throughout the build to move faster without cutting corners. Everything it produces is reviewed, tested and understood before it ships.
Finding out why something actually breaks and fixing the cause rather than the symptom.
Describe what happens after handover — how long you stay available and what that covers. Only promise what you will actually do.
Selected work
A selection of things I have built. Each one links to the running site and to the source.
FeaturedWeb App · 2026
One or two sentences on what the project is and who it is for. Lead with the outcome rather than the tech stack — the stack is listed right below.
What the build actually exercised: the hard part, the decision you had to make, or the thing you learned. This is the block that separates a portfolio from a list of links.
Frontend · 2025
Keep summaries a similar length across projects — the cards read better when they are balanced.
Say what was interesting about building it. A project with no story behind it reads as filler.
Practice · 2025
Small projects are fine to include as long as you are honest about their scope.
What you set out to practise, and whether it worked.
More work lives on GitHub.
Achievements
Competitive programming, professional training and academic progress.
Platform or Contest
Something measurable you have actually done — problems solved, a contest rating, a contribution. Only list what is true and verifiable.
Institution or Provider
What the programme covered and what you came out of it able to do.
Your University
A degree in progress or completed, with the detail that is worth stating. Leave this out entirely if it is not a selling point for you.
Articles
I write about backend engineering, problem solving and what I learn building things — the reasoning behind the code, not just the code.
Contact
Open to freelance work and collaboration. Email, phone or WhatsApp — whichever suits you.
Your City, Country
Open to freelance & collaboration.