Should Software Engineers Continue Creating Projects for Their Resumes?

Once you have 1-2 years of work experience in software engineering, the question arises: Should you continue making projects for your resume to impress hiring managers?

Two Motivations for Personal Projects

There are only two genuine reasons to do so:

To Gain Joy and Control: There is a significant amount of satisfaction in creating a project that is entirely under your control and is intrinsically valuable to someone. For example, developing a smartphone app that helps manage a hobby or special interest can be a source of immense joy and can impress potential employers with your dedication and creativity.

To Participate in Open Source: If you have a passion for a specific software solution, contributing to an open source project can immensely boost your profile. Perhaps you have a particular interest in an open source game or a library that aids in your daily work. Engaging in such projects can help build valuable industry contacts in both business and academia, and it will significantly enhance your reputation in the field.

Avoid Making Makework Projects

However, it is explicitly advised against making makework projects, which are technology demos that don’t solve any real-world problems. These are hardly impressing hiring managers and are unlikely to bring long-term benefits to your career.

The Thin Line Between Personal Projects and Makework

Deciding whether a project falls into the realm of joy, open source contribution, or makework can be challenging. Here are some factors to consider:

Relevance: Is the project relevant to the industry you are aiming to enter? Employers are often looking for projects that showcase your ability to address real-world problems and contribute to the tech community.

Achievability: Is the project achievable within a reasonable timeframe and with the resources you have? If a project spans years and requires resources that are scarce, it might not be the best use of your time.

Solution: Is the project solving a genuine problem?

Brevity: Is the project a mere demonstration or a solution to an actual problem? Demonstrations, while impressive, may not add much value if they lack the backing of a tangible solution.

Impact: How will the project impact your career and the industry? Open source contributions, for example, can significantly boost visibility and connections within the tech community.

Conclusion

In summary, software engineers should focus on personal projects that bring joy, are relevant, and contribute to solving real-world problems. However, these projects should not be trivial and should have a tangible impact on both the tech community and your future career prospects.

By carefully choosing and contributing to projects that align with your passion and industry goals, you can create a strong and impressive resume that stands out to hiring managers.