Interviewee
I would say, when forming a team one should consider the different potential of a team, lets say
you have a team of two where both of them are efficient in backend development and have little
knowledge about frontend, then the frontend of your system will suffer, so your team should be
dynamic and proficient in different areas
I would say, when forming a team one should consider the different potential of a team, lets say
you have a team of two where both of them are efficient in backend development and have little
knowledge about frontend, then the frontend of your system will suffer, so your team should be
dynamic and proficient in different areas
Interviewer
Alright ma next question is:
Could you tell us about the team you’re currently working with and your role within it?
Alright ma next question is:
Could you tell us about the team you’re currently working with and your role within it?
Interviewee
The team we have here is 1 team lead , 1 frontend developer and 1 backend developer, and
one full stack developer, and I work as a full stack developer
The team we have here is 1 team lead , 1 frontend developer and 1 backend developer, and
one full stack developer, and I work as a full stack developer
Interviewer
Good,next question
What are your perspectives on AI? Some people argue that using AI diminishes one’s capacity or ability and doesn’t count as real writing.Additionally, what percentage of your work involves AI?
Good,next question
What are your perspectives on AI? Some people argue that using AI diminishes one’s capacity or ability and doesn’t count as real writing.Additionally, what percentage of your work involves AI?
Interviewee
I see AI as a tool, not a replacement. I use it to accelerate my workflow, whether it’s debugging,
brainstorming solutions, or learning a new framework. It doesn’t take away from your ability; if anything, it enhances it when used wisely. I'd say around 30–40% of my work involves AI in some way, especially when experimenting, generating boilerplate, or learning faster.
I see AI as a tool, not a replacement. I use it to accelerate my workflow, whether it’s debugging,
brainstorming solutions, or learning a new framework. It doesn’t take away from your ability; if anything, it enhances it when used wisely. I'd say around 30–40% of my work involves AI in some way, especially when experimenting, generating boilerplate, or learning faster.
Interviewer
Well,ma next question is:
How do you use or collaborate with AI? How do junior developers learn new languages or frameworks? For instance, I believe it shouldn't take 4 or 5 months to learn a new framework or library; I support using AI effectively to speed up the learning process. What advice do you have on this topic?
Well,ma next question is:
How do you use or collaborate with AI? How do junior developers learn new languages or frameworks? For instance, I believe it shouldn't take 4 or 5 months to learn a new framework or library; I support using AI effectively to speed up the learning process. What advice do you have on this topic?
Interviewee
I often use AI to quickly grasp the basics of a new library or debug faster. For junior devs, AI can be like amentor-on-demand. But to truly learn, you need to build real things. Don’t spend 4–5 months stuck on tutorials, build something small, and learn as you go. That’s how I picked up Flutter, and .NET efficiently.
I often use AI to quickly grasp the basics of a new library or debug faster. For junior devs, AI can be like amentor-on-demand. But to truly learn, you need to build real things. Don’t spend 4–5 months stuck on tutorials, build something small, and learn as you go. That’s how I picked up Flutter, and .NET efficiently.
Interviewer
Alright ma next question:
What is your perspective on soft skills? As we know, technical issues today aren't as challenging as they once were so what do you think about the role of soft skills, and what
would you advise others to focus on?
Alright ma next question:
What is your perspective on soft skills? As we know, technical issues today aren't as challenging as they once were so what do you think about the role of soft skills, and what
would you advise others to focus on?
Interviewee
Soft skills are underrated but crucial. Communication, time management, and empathy are what separate great developers from good ones, especially in team settings. Now that technical challenges are more manageable (thanks to open-source, frameworks, and AI), the ability to work well with others and think clearly matters even more.
Soft skills are underrated but crucial. Communication, time management, and empathy are what separate great developers from good ones, especially in team settings. Now that technical challenges are more manageable (thanks to open-source, frameworks, and AI), the ability to work well with others and think clearly matters even more.
Interviewer
Good ma next question is:
Can you tell us about your first paid job or project? How did you get it, and what was the experience like?
Good ma next question is:
Can you tell us about your first paid job or project? How did you get it, and what was the experience like?
Interviewee
My first paid gig came through an internship.I also found the opportunities through networking
and showcasing my work. The experience was both validating and eye-opening, it showed me
how different real-world expectations are compared to school projects.
My first paid gig came through an internship.I also found the opportunities through networking
and showcasing my work. The experience was both validating and eye-opening, it showed me
how different real-world expectations are compared to school projects.
Interviewer
Good,next question is:What advice do you have for freshman students regarding which department to join and other considerations?
Good,next question is:What advice do you have for freshman students regarding which department to join and other considerations?
Interviewee
Choose based on curiosity, not trends. If you enjoy solving logical problems, building things, and
don’t mind constant learning, Software Engineering or Computer Science is worth it. Also, don’t obsess over grades, balance academics with real-world projects and soft skill development.
Choose based on curiosity, not trends. If you enjoy solving logical problems, building things, and
don’t mind constant learning, Software Engineering or Computer Science is worth it. Also, don’t obsess over grades, balance academics with real-world projects and soft skill development.
Interviewer
Good,Some people in the field say that attending university is a waste of time. What are your thoughts on the value of university education in the field of programming?
Good,Some people in the field say that attending university is a waste of time. What are your thoughts on the value of university education in the field of programming?
Interviewee
It depends on how you use your time there. The degree itself won’t make you a great developer, but the structure, peer environment, and access to resources can be incredibly useful. For me, university helped me explore a wide range of topics and gave me the confidence to pursue tech more seriously.
It depends on how you use your time there. The degree itself won’t make you a great developer, but the structure, peer environment, and access to resources can be incredibly useful. For me, university helped me explore a wide range of topics and gave me the confidence to pursue tech more seriously.
Interviewer
Well,ma next question is:
What did you learn during your 5 years in the Software Engineering department ,both in terms of your field of study and your social life?
Well,ma next question is:
What did you learn during your 5 years in the Software Engineering department ,both in terms of your field of study and your social life?
Interviewee
Technically, I learned the foundations, data structures, system design, algorithms, and how to
approach problems methodically. Socially, I learned how to work with diverse groups, present my ideas, and deal with uncertainty. University isn’t just about what you study, it’s also about learning who you are and how you work best.
Technically, I learned the foundations, data structures, system design, algorithms, and how to
approach problems methodically. Socially, I learned how to work with diverse groups, present my ideas, and deal with uncertainty. University isn’t just about what you study, it’s also about learning who you are and how you work best.
Interviewer
Good,next questions:
Is there anything you regret not doing during university, or something you did that you now wish you hadn't?
Good,next questions:
Is there anything you regret not doing during university, or something you did that you now wish you hadn't?
Interviewee
I sometimes wish I had networked more, attended more tech meetups, joined open source earlier, or built more projects collaboratively. I also might have stressed less about some courses and spent more time exploring things I actually enjoyed building. But overall, every choice taught me something.
I sometimes wish I had networked more, attended more tech meetups, joined open source earlier, or built more projects collaboratively. I also might have stressed less about some courses and spent more time exploring things I actually enjoyed building. But overall, every choice taught me something.
Interviewer
Good. Finally, would you like to share a message with our audience and us that I haven’t brought up?
Good. Finally, would you like to share a message with our audience and us that I haven’t brought up?
Interviewee
Don’t wait to feel “ready” before you start something. You’ll never feel fully prepared, and that’s okay. Just build. Learn. Share. Whether it’s a simple app, a blog post, or a failed attempt, it all adds up.
Also, don’t let comparison steal your pace. Everyone’s journey in tech looks different. Some people start early, some switch later. Some love LeetCode, some don’t. What matters most is staying consistent, being curious, and showing up, even on days you feel stuck.
Lastly, tech is changing fast. AI, tools, frameworks, they’re evolving daily. Instead of fearing it, learn how to adapt. Use them. Play with them. The best developers aren’t the ones who know everything, they’re the ones who know how to learn anything.
Don’t wait to feel “ready” before you start something. You’ll never feel fully prepared, and that’s okay. Just build. Learn. Share. Whether it’s a simple app, a blog post, or a failed attempt, it all adds up.
Also, don’t let comparison steal your pace. Everyone’s journey in tech looks different. Some people start early, some switch later. Some love LeetCode, some don’t. What matters most is staying consistent, being curious, and showing up, even on days you feel stuck.
Lastly, tech is changing fast. AI, tools, frameworks, they’re evolving daily. Instead of fearing it, learn how to adapt. Use them. Play with them. The best developers aren’t the ones who know everything, they’re the ones who know how to learn anything.
❤2