So, you're diving into the world of software engineering, eager to land that dream job at your favourite tech company. But wait—do you really need to have a side project (or "pet project," as some - including me - call it) to stand out in the sea of applicants? Let's break it down.

The Case for Pet Projects Demonstrating Skills: Pet projects offer a tangible demonstration of your technical abilities. They provide a platform to showcase your coding prowess, problem-solving skills, and creativity in a real-world context. Passion and Initiative: Employers often look for candidates who are genuinely passionate about software development. Having a pet project underscores your enthusiasm for the field and demonstrates your willingness to go the extra mile. Learning Opportunities: Engaging in a pet project allows you to explore new technologies, tools, and methodologies outside the constraints of a typical work environment. This hands-on experience can significantly enhance your skills and knowledge base. Portfolio Building: Just like artists compile portfolios to showcase their work, software engineers can use pet projects to build a portfolio of their accomplishments. This portfolio can be invaluable when applying for jobs or freelance gigs. The Counterargument Not a One-Size-Fits-All Requirement: While pet projects can certainly bolster your candidacy, they are not an absolute necessity. Some hiring managers prioritize professional experience, educational background, and problem-solving abilities over personal projects. Time and Resources: Not everyone has the luxury of spare time and resources to devote to a pet project. Balancing work, family commitments, and personal interests can be challenging, making it unrealistic for everyone to engage in extracurricular coding activities. Alternative Demonstrations of Skill: There are other ways to demonstrate your skills and passion for software engineering besides pet projects. Contributing to open-source projects, participating in coding competitions and even giving back to the community by blogging or any other forms of sharing knowledge. Finding a Balance Ultimately, whether you need a pet project to get hired as a software engineer depends on various factors, including the company culture, the specific role you're applying for, and your individual circumstances. If you have the time and inclination to work on a pet project, by all means, go for it. It can be a rewarding endeavour that not only enhances your job prospects but also fuels your passion for coding. Heck, it can even become your full-time job. However, if personal projects aren't feasible for you, don't despair. Focus on honing your skills, gaining relevant experience, and finding alternative ways to demonstrate your value to potential employers. In the end, what matters most is your ability to solve problems, collaborate effectively with others, and continuously learn and grow as a software engineer—whether or not you have a pet project to your name. So, while having one can be beneficial, it's not the be-all and end-all of your career prospects in the tech industry. Bonus Part – What to Avoid It's not just about having a pet project; it's about the quality and relevance of the project. A hastily thrown-together application or a clone of an existing project may not impress employers as much as a well-thought-out, original creation. And to be 100% clear – projects you do as a part of a guided online course do not count for pet projects. Believe me when I say it: I have seen hundreds of resumes with exactly the same portfolio. They don't really prove anything, as they were done as guided walks in the park. The pet project's main objective is to showcase that you can build something independently, showing your initiative and creativity in a real-world context.