Most people assume that the standard tech career timeline goes:
Finish school
Then learn to code
Then get hired
But today I want to share the story of one ZTM student who skipped a step.
You see, he found ZTM back in 8th grade, years before he'd even started his Computer Science degree. Which means that now, while he's still a university student, he's already working as a Software Developer on the side, building tools real business teams rely on.
When I first heard this, I knew we had to share this story, so let’s dive in…
Meet Alif
Hi, I’m Alif Hassan Aunkur:
I’m a sophomore studying Computer Science Engineering at BRAC University in Dhaka, Bangladesh.
Alongside university, I work full-time as a Software Developer at Edutechs, where I build full-stack business applications.
In my role, I mainly work on building a suite of business applications using full-stack technologies. My work involves developing CRM/SaaS-style tools, dashboards, integrations, and internal systems that help real business teams manage their operations more efficiently.
How long have you been in that role?
I’ve been in this role for around three months. Even though it has been a short time, the responsibility grew very quickly. I started by working on proof-of-concept applications and smaller contributions, but soon moved into building and maintaining full-stack business applications used by real teams.
One of the biggest learning experiences has been taking ownership of a CRM/SaaS-style product, where I work on features, integrations, dashboards, onboarding flows, and production improvements. It has been a very fast transition from learning and building projects to working on software with real business impact.
What did you do before you got your current job/new position?
Before my current software developer role, I spent around 5–6 years working in education. I taught robotics, programming, and STEM concepts, and I also tutored students preparing for O Level and A Level exams, which are British curriculum qualifications roughly equivalent to high school and advanced pre-university courses.
That teaching background helped me a lot because it trained me to explain complex ideas clearly, break problems down step by step, and stay patient while solving problems. I was also constantly working with technology through robotics and STEM education, so even before getting a software job, I was already involved in programming, hardware, software, and practical problem-solving.
What was the goal or outcome you were hoping for from ZTM? Did you achieve it?
I found ZTM during COVID when I was in 8th grade. At that time, I was not the most academically focused student, but I was very curious about programming, and came across the ZTM full-stack web development course.
I heard about ZTM through programming communities on Discord and Reddit, where people recommended it as a structured way to learn full-stack development. After that, one of my friends on Discord also vouched for ZTM and told me the curriculum was well-structured and well-paced.
That was important for me because, at that age, I did not just need information. I needed direction, and ZTM gave me a roadmap that made web development feel less overwhelming and helped me start building a proper foundation. Before that I was stuck watching so many tutorials, videos, and random resources online, and I struggled to understand what to learn first and how everything connected.
Looking back, ZTM gave me one of my earliest strong foundations in programming and web development. It helped me understand how different parts of full-stack development connect together, and that foundation continued to help me later in university coursework, personal projects, teaching robotics, and even landing an internship near the end of high school.
So yes, I would say I achieved the outcome, even if I did not fully understand the outcome at the time. ZTM helped me take programming seriously and gave me a base that kept paying off years later.
What other resources, courses, sites did you consider
Since I was still a kid and had a limited budget, I looked at a lot of free resources before joining ZTM. Some of the main ones I considered were freeCodeCamp and The Odin Project. I also watched a lot of programming content on YouTube from creators like CodingWithHarry, who is a popular Indian programming YouTuber, and Fireship.
Those resources were helpful, especially for exploring different topics, but at the time I felt overwhelmed by how scattered everything was. I could learn individual concepts from free resources, but I struggled to understand the full path from beginner to building real full-stack applications.
That was one of the reasons ZTM stood out to me. It felt more structured and easier to follow, especially as someone young who needed a clear roadmap instead of just more random tutorials.
What were the biggest hesitations and doubts you had before deciding to join ZTM?
My biggest hesitation was whether joining a paid course would be worth it, especially because I was still in 8th grade and had a limited budget. There were already many free resources online, so I wondered if I really needed a paid platform.
I also doubted whether I would be able to stay consistent and turn the lessons into actual skills. At that age, I enjoyed programming, but I did not fully understand the discipline required to learn development seriously.
In the end, I decided to join because ZTM felt more structured than the free resources I was using. I needed a clear path, not just more random tutorials.
After you joined, were there any difficulties?
Yes, definitely. At first, I thought learning programming meant watching the lessons and understanding them. But after joining, I realized the real difficulty was applying the concepts without someone guiding every step.
I would understand something during the video, but then get stuck when I tried to build something myself or modify the project. Debugging was frustrating in the beginning, but it taught me how developers actually learn: by making mistakes, searching, testing, and fixing things.
The course gave me direction, but I still had to develop consistency and patience. That was one of the biggest difficulties, but also one of the most useful parts of the journey.
What was your learning experience like?
My learning experience was both exciting and challenging. The early parts were smoother because ZTM gave me a clear path and helped me build confidence with the fundamentals. But when I got into frameworks like React, it honestly broke my brain at first.
At that stage, I was still young, and React introduced a different way of thinking. I had to understand components, state, props, data flow, and how the UI changes based on application logic. It was no longer just writing simple code and seeing an output.
The biggest shift for me was learning how the front-end, back-end, and database connect together. That was difficult in the beginning, but it helped me build the full-stack mindset I still use today. Over time, things started clicking, and I began to understand how real applications are structured.
What do you think differentiates ZTM from other resources you used?
What differentiated ZTM from many other resources I used was that it did not feel like just another video tutorial. The visual explanations, practice problems, and self-assessed assignments made the learning experience much more active.
A lot of free resources online are useful, but they often stop at explaining a concept. ZTM helped me practice those concepts and apply them in a more structured way. The assignments and projects made the learning feel closer to real engineering, where you have to understand the problem, make decisions, debug issues, and build something that actually works.
That combination of clear explanations, structure, and practical assignments made ZTM stand out for me.
What was your previous level of coding/programming experience before joining ZTM?
Before joining ZTM, I had beginner-level experience with JavaScript and Python. I could write basic scripts, manipulate the DOM, and experiment with small backend ideas, but most of my knowledge was isolated.
The main thing I lacked was the ability to connect all the different parts of development together. I did not yet understand how the frontend communicates with the backend, how the backend connects to a database, or how those pieces become a complete application. ZTM helped me build that bigger picture.
What ZTM courses have you taken? How did each course help you with your goals?
The two main ZTM courses I took were the full-stack web development course (which has an intro to React) and the data structures and algorithms course for job interviews:
The web development course helped me build my foundation. It taught me how modern web applications are structured and helped me connect concepts like front-end, back-end, APIs, and databases. Before that, I knew small pieces of programming, but this course helped me understand the bigger picture.
While the data structures and algorithms course helped me with interview preparation and problem-solving. It taught me how to think more systematically about coding problems, recognize patterns, and approach solutions with more structure.
Both courses supported different parts of my goal: one helped me become a better builder, and the other helped me become a better problem solver.
How long did each course take you to complete?
The web development course took me around three months to complete. However, actually polishing those skills to a usable level took much longer. Probably one to two years of practice, building projects, debugging, and applying what I learned in different contexts. (I was still really young at the time!).
After finishing the course, I continued using that knowledge in practical ways. I built my own projects, worked on web applications, and helped others with technical implementation for university-level CS projects. That helped me move from simply understanding the lessons to being able to apply the concepts in real situations.
For the data structures and algorithms course, I used it more as interview preparation rather than something I completed in one fixed timeline. I would study topics when I needed to strengthen my problem-solving skills or prepare for technical assessments.
What has been the biggest challenge in your journey from learning to code to getting hired?
The biggest challenge in my journey from learning to code to getting hired was proving that my skills were real, especially because I am still young and still a student.
Learning through courses and building projects gave me knowledge, but getting hired required me to show that I could apply that knowledge in practical situations. I had to build projects, explain my work, improve my portfolio, and show that I was serious enough to be trusted with real development work.
Another challenge was confidence. I often wondered if I was “ready enough” to apply, because software development can feel endless as there is always another framework, another tool, or another concept to learn. Eventually, I realized that getting hired is not about knowing everything. It is about showing that you can learn quickly, solve problems, communicate clearly, and keep improving.
Teaching robotics and programming also helped me a lot because it gave me communication skills and technical confidence before I formally entered the software industry.
What steps did you take to get hired?
The main steps I took were building projects, publishing them on GitHub, deploying them, and sharing my learning in public. I wanted people to see that I could build complete applications, not just follow tutorials.
I also focused on building in public through Instagram and LinkedIn.
On Instagram, I shared programming-related videos and my learning journey through my page, @leafdoestech
While on LinkedIn, I shared projects, progress, and technical updates
Over time, that visibility helped me connect with recruiters and people already working in the industry, and it even led to opportunities and offers through social media.
What helped me the most was having proof of work such as end-to-end projects, deployed applications, GitHub activity, teaching experience, and public content. My resume mattered, but the projects and online visibility made it much easier for people to trust my skills.
I did apply to opportunities, but the biggest factor was not just the number of applications. It was building enough public proof that when an opportunity came, people could see I had been consistently learning, building, and improving.
Now that you have your new position, how do you feel?
Honestly, it feels surreal. I am still a university student, but I now get to work on software that real people use for real business operations. That shift from building projects for practice to building products with actual users has been a huge moment for me.
I feel proud, but also very aware of how much more I still have to learn. Getting this position gave me confidence that the years I spent learning, teaching, building projects, and sharing my work online were worth it.
More than anything, it made software development feel real to me. It is no longer just something I am studying or practicing. It is something I am actively doing, and that motivates me to keep improving.
Is there a big difference in earnings in this new role from what you made before?
Yes, there has been a meaningful difference. This role has made a big difference in my life because I can now afford my university tuition by myself.
That means a lot to me. As a student, being able to support my own education through software development makes the role feel even more meaningful. It is not just a job for me — it is helping me continue my studies and build my future at the same time.
What advice would you give other students who may have been in your position and are now considering joining the ZTM Academy?
First, I think students should consider ZTM if they want a structured path that turns scattered learning into real progress. There are many free resources online, and they can be useful, but when you are starting out it is easy to feel lost. ZTM helped me because it gave me direction, practical projects, visual explanations, and a foundation I could keep building on for years.
For me, ZTM was not just a course I completed and forgot about. It helped shape the way I understood full-stack development, connected different parts of programming together, and gave me the confidence to keep building beyond the course.
Second, my personal advice is to document everything. Once you start learning and building through ZTM, do not keep that progress hidden. Build projects, deploy them, post about them, share what you struggled with, and show people what you are working on through GitHub, LinkedIn, Instagram, or any platform where you can make your learning visible.
ZTM can give you the structure and foundation, and your public proof of work can help turn that learning into opportunities. Start small, stay consistent, and let your work compound over time.
Best articles. Best resources. Only for ZTM subscribers.
If you enjoyed this post and want to get more like it in the future, subscribe below. By joining the ZTM community of over 100,000 developers you’ll receive Web Developer Monthly (the fastest growing monthly newsletter for developers) and other exclusive ZTM posts, opportunities and offers.
No spam ever, unsubscribe anytime
