> Other than that, your side project will be seen as a hobby and not an achievement, and will be disregarded.

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.

"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."

Most managers at my company view side projects positively. One of the main reasons is that it shows the person has a creative mind and is at least a little passionate about technology/coding and learning on their own.

I'm not even an engineer but I have some HR training as a Psychologist and this resonates with me.

aye - I don't list inactive projects, but some hobbies/side projects provide a small sense of what kind of person you are like and what it will be to work with you.

I wonder how I would fair in your evaluation of what I'm like if I have Android apps for ballistic energy calculations and a calculator for determining the alcohol needed for a party.

This isn't part of the evaluation, but it's a useful item to include for conversation starters. Whether these are useful conversation starters in a particular company is up to your judgement.

If you are interviewing for an Alcohol friendly company then the calculator might be a fun side project that shows you know Android development. Raytheon would probably love the ballistic energy calculator. If your interviewing with the quaker church then both items will probably have you rejected for culture fit.

Most people chuckle when I demo the alcohol calculator. They especially like the drunkenness slider to select how drunk your guest are expected to get. I make sure to give them the background that it was an idea that I started in college. The ballistic one is extremely simple, but that was my first ever Android app and I chose it for that reason (didn't do a regular calculator because there are sooo many of them out there already).

I might as well add the link. https://play.google.com/store/apps/details?id=com.blogspot.t...

> I think you’ve misunderstood the purpose of a side project for engineers.

Perhaps, but you have to assume that many of those who are hiring will do exactly that. That's the meta-game.

There's a basket of opinions in this thread and they are all valid and informative, even if they are mistaken.

Generally only reading your last few jobs and educational background. Side project is fine to see but it’s not going to be the differentiator. If you’re getting an interview you’re getting an interview.

Side projects help junior candidates without relevant job experience most.

> 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.

I don't agree. A side-project might demonstrate those things, but most of the time, as an interviewer, I'm interested in a candidate's side-project because it shows curiosity and interest. It says something about their character.

I like your answer I just wonder: I used this project to teach myself kubernetes. If someone asks me how I know kubernetes what do I say? I suppose I say it was on a side project I did

Sure, people give me that answer all the time.

If you actually went beyond basic setup and dealt with real enterprise/production level issues then make sure to point it out. I assume that “I learned it for a side project” means mostly happy path stuff.

Then by all means mention the project. To me, what matters in this specific answer is not the side project, but the learning opportunity and associated curiosity.

All bonus points, especially if the company uses k8s or if you can answer aptly "why did you choose k8s?"

FWIW, I'd expect 3 kinds of answers: 1. "This was a right fit because..." 2. "I knew this was NOT a right fit but I wanted to learn" 3. "I thought it was the right fit but I was wrong because..."

When I'm hiring I consider "I learned that on a side-project" to be an extremely strong positive signal.