| Just based in your initial post and your replies here, putting on my hiring manager hat, you have me a bit confused (and that is not good). For me at least, I want to see work experience first (post-college), then educational experience, then projects, open source, part time stuff. The progression is full time pro work, school, and “other”. Your answers appear to be conflating full time work with school and projects and maybe open source. It makes it very difficult to get a handle on your “true” background. You can deviate from that pattern, but you have to be very clear about it. Because as a hiring manager, if it’s clear we are starting on a good foot and building trust. If it’s not clear, I worry about communications skills, and maybe I worry you are trying to promote a side project as a full time job. Trust wanes a little. Another example of that is single person consulting to various companies. Some people are clear about this on their CVs, and list the roles and companies they consulted to. Very clear, and short tenures are not a problem because that’s the nature of the beast (as long as you’ve had a perm job somewhere and shown some stability). I have seen others with similar backgrounds list themselves as CEO of XYZ LLC and paint themselves as a C suite exec, and you dig and single it’s a sole proprietorship out of Kentucky (or whatever). Not good, I lose trust in the candidate (side note: LinkedIn kind of sucks at showing this clearly). CV’s are very interesting because you do want to sell and market yourself, but at the same time you do want to steer clear of dark patterns that go over the line from selling yourself to over inflating your role too far. Always put yourself in the shoes of a hiring manager truly trying to understand your career and abilities, market yourself well but be accurate and clear. |
It makes a lot of sense to split it up like that. My early experience (throughout college) was some full-time roles (that I quit e.g. to accept a FAANG internship, which I think I would be foolish not to), some project-based work, and I list all of that as regular work experience. It's clear to me now that this causes some confusion.
I really appreciate you taking the time to explain this to me as someone who is on the other side of the process, and I'll incorporate this knowledge in my resume (which, it looks like, I need to fully rework).