| You want your side projects to help you get the job. They must demonstrate as achievements instead
of hobbies. For this reason, I'd default to no, don't list side projects, unless you make it a strong argument for the position you're applying to. Are you a major contributor to a tech used in company? Have you written a book about it?
Did you grow a community? Have you reached significant traction or revenue? Any yes to one of the above, if they relate to the position, can hint you into mentioning your side project. Other than that, your side project will be seen as a hobby and not an achievement, and will be disregarded. Note: some nuances may apply, so take this as the generic advice it's meant to be. |
I think you’ve misunderstood the purpose of a side project for engineers. They’re supposed to be hobby projects that demonstrate the developer’s abilities as well as their commitment to following through on projects.
The OP’s projects are perfect for listing as completed side projects on a Senior Engineer resume. I wouldn’t hesitate to include them on a resume and describe the technologies used to build them.
You definitely don’t need to demonstrate significant traction or revenue for an engineering side project, nor do you need to write a book about it or build a significant community around it. These are ridiculously high standards for including a development side project on a senior engineer resume.
Frankly, if someone were to list “side projects” with significant revenue and a large community, I’m going to assume it’s a business and not a side project. We’d have to have a conversation about how much time and energy it’s going to take away from their employment, and how we can cleanly separate it from interfering with their job. Showing employers that you’re running a side business with significant revenue and therefore significant needs isn’t exactly a bonus when it comes to hiring someone. A fun side project that demonstrates their skills is a bonus, however.