I'm Sami Ullah. For the last three years I've worked as a developer across the whole stack — designing data models and APIs on the back end, and building the interfaces people actually touch on the front end. The thread running through all of it is the same: I care about how a product is built and how it feels to use, and I don't think those two things can be separated.
My work has moved between roles and continents. I started as a web developer building marketing and product sites, spent time as a frontend developer shaping the interface of Portfolyio, a portfolio-builder SaaS, and served as Chief Technology Officer at AI3, a US-based team building AI developer tooling. Today I'm a Python developer at Suvastu Tech, building data pipelines and back-end services, while pursuing an MS in Computer Science at the University of Swat.
What I focus on
End-to-end product engineering. I'm most useful when a project needs one person who can hold the whole picture — someone who can stand up a Postgres schema, wire the REST API, and then build a responsive, accessible interface on top of it without handing off three times in between. I've shipped with Next.js, React, Node, Django and plain PHP, and I'm comfortable moving between them based on what the product needs rather than what's fashionable.
Increasingly that work touches machine learning. Not model research — the practical side: getting data into a shape a model can use, wrapping inference behind an API, and building interfaces that make an AI feature feel trustworthy instead of magical and opaque.
How I work
Problem-solving first, code second. Before I open an editor I want to understand what the user is actually trying to do and where the current experience fails them. That habit came from working on small teams where there was no room for wasted effort — if you built the wrong thing well, you'd still built the wrong thing.
I believe in clean architecture, honest code reviews, and handoffs that don't leave the next person guessing. I try to ship fast without cutting the corners that come back to bite you: the error states, the empty states, the loading behaviour, the thing that breaks on a slow connection. Those details are usually the difference between software that demos well and software that people trust.
Good engineering is mostly the discipline to finish the last ten percent that nobody sees but everybody feels.
Where I've worked
A quick timeline of the roles that shaped how I build:
- Suvastu Tech — Python Developer (Sep 2024 – now), Swat, Pakistan. Building data pipelines and back-end services.
- Portfolyio — Frontend Developer (March 2025 - Jan 2026). Interface work on a portfolio-builder SaaS.
- AI3 — Chief Technology Officer (2023 – 2024), United States. Led engineering on AI developer tooling.
- Zetasoft — Software Developer (2023 – 2024), Peshawar, Pakistan.
- LetsGrowMore · iNeuron.ai — Web Developer (2023), remote / India.
- SILTED — Web Developer (2022 – 2023), Swat, Pakistan.
Outside the work
I write about the things I run into while building — the trade-offs behind picking a stack, the unglamorous work of making an interface fast, what a CTO role actually involves at an early-stage company. You can read those on the blog. If any of it is useful to you, or you have a project that needs someone who can own it end to end, I'd like to hear about it.