The job title says architect. The side project says “why is this Dockerfile 300MB, let me fix this real quick” – three hours later, still shaving layers, completely happy.
Nobody assigns you ops on a side project. Nobody assigns you anything. But there you are, writing monitoring for something with twelve users, eleven of them are you in different browsers.
The role is what someone else decided you were good at. The side project is what your hands reach for when nobody’s directing them. Sometimes they match. Mostly they don’t. The backend engineer with strong opinions about font spacing. The tech lead who’d rather be tailing logs than running standups. The platform architect who writes a blog engine from scratch and tells you with a straight face that the existing ones were fine, just not the way they’d do it.
Side projects don’t have an org chart or “that’s not your area” meetings. What’s left is the part of building you’d do for free. Which is exactly what’s happening, on a Friday evening, while everyone else is somewhere else.
The resume says what you were paid to do. The side project says what you’d do anyway.