Skip to content
Parham Bakhtiari

Hey! It's Me

I’m Parham. VP of engineering by day, and that hungry/learning associate engineer by night. These days I spend most of my time on the shape of systems rather than the syntax of code. This is one of the reasons why I’m starting this website so that I can document my own learnings along the way.

About me

I started programming when I was 14/15. I really started liking it when I started building out some Android apps for myself. Seeing the change made it much more enjoyable than just a terminal application. I tried building myself an SMS app or my own lock screen. Nothing revolutionary - I’d see other apps on the market and try and build my own versions to learn the complexities of them. I went on to a double degree in Electrical Engineering (Computer Systems) and Computer Science at uni.

A lot of what I believe, and what I write about here, comes from how I got to where I am.

Breadth

I took my first job while still at uni. It was a contracting company. As you know with any contracting company, projects were billed by the hour, so “perfect” was never on the table. If the client was happy with the work, then that was good enough. That taught me trade-offs early, and honestly it left me a bit sad at the start of my career since nothing would ever be “the best”. On the other hand, it gave me a lot of opportunities to work with different tech stacks. I was building PHP apps and its templating systems, to (kind of selfishly) pushing the team to adopt new tech like Docker, services, even React so that I could keep pushing my horizon further with bleeding edge technology (it’s funny to think that was bleeding edge back then). Then onto building Chrome extensions that could work with Windows applications between the browser, and iOS apps that could control the stabilisation system of ships over custom network protocols. Or even building resident apps so they could control different appliances or building amenities like lifts and intercoms via their phone.

This job helped me be confident that the stack for the “problem” is not the limiting factor. As an engineer, you should be able to change the stack to solve a problem and shouldn’t limit yourself to a single stack.

Depth

I joined a product company next where they were running at orders of magnitude higher traffic. Most of the changes that affected users needed to consider scale as well as simplicity since change is very hard at that scale. This was a more stable stack system since it’s a product company. On the technical skills, I went much deeper in cloud computing features on AWS, worked with Java (outside of uni) professionally and more professional usage of technology and methodology that I was learning already. On the soft skills, it also taught me a lot about product systems and how to build systems that can work well, solve the problem and are maintainable since the business changes over time. I went from an engineer working on projects with others, to a senior engineer leading those projects to finally an engineering manager that would be responsible for those engineers and their projects. I had a great mentor there, and I believe most of my technical and leadership instincts today trace back to that time. I will also say, I was lucky enough to start at this company at a time where it hadn’t become a full enterprise, so I got a lot of mentorship as well.

This job helped me learn how to build scalable systems not just through code but through actual engineering practices. It also taught me that “perfect” doesn’t mean anything if the problem you’re solving doesn’t solve a problem for the business.

Leverage

At my current company I joined as a senior engineer, going up to an engineering lead and now VP of engineering. I’m responsible for everything the engineering team delivers, and I lead a team of teams plus org-level ICs. I’m no longer on the critical path, as that wouldn’t make sense since I can’t guarantee my time to specific projects anymore. My job is not only designing and approving systems which includes architecture, data models, infrastructure; but also growing the engineers who’ll need to make those same decisions.

This job is still teaching me new perspectives every day, so I can’t summarise it down to a single lesson here. However, my main lesson so far: do not be afraid to make yourself replaceable in the role. Having your team perform so well that you’re no longer needed is the ultimate problem-solving skill. Many think this is a bad outcome, but if you’re good at solving problems, you’ll just move to a different team / role that will require you to solve a different problem.

What I’m thinking about

I left my previous role just as the AI train was arriving. Back then, it was ok for prototypes and pretty weak at writing actual usable code (back in the ChatGPT Chat days). Now I’m watching and learning the move to agentic AI, where code itself is becoming closer to being a commodity as the models, harnesses and systems are becoming increasingly smarter. That being said, I see the massive hype on X around the industry and what works for a weekend micro-SaaS isn’t what keeps a high traffic system running. The barrier of entry into product building is orders of magnitude lower which is a phenomenal thing. However, engineering fundamentals matter more than ever, not less.

What I (want to) write about

Junior to VP

I want to talk about how the next generation of engineers can get into the market and ideally come up. Especially with the new day and age of AI, it might feel rough getting into the market, but it’s still possible. For existing engineers within the industry, I want to be able to talk about my experience of how I’ve got to where I am and maybe help you unblock the next level in your career be it going up into a managerial position or even the individual contributor track.

Systems and AI

I believe the AI train is here and won’t leave. This is going to do to software engineers what the cloud did to network engineers 20 years ago.

I want to build some systems using AI. The aim of it is to see how you can build scalable systems using AI to help speed up the process. This I am very excited about because not only do I get to build systems and get back into hands-on engineering again, but it’s also a platform for me to learn new technologies and AI methods too.

Leading Leaders

If you’re going into management or becoming a senior IC, you need to learn how to not place yourself on the critical path. That mentality alone is what helps you move through your career. That is generally the main piece that I see where people hit a plateau.

Elsewhere

License

Posts on this site are licensed under CC BY 4.0 unless noted otherwise.