[scarface74]

If someone has completed a certification or course, it becomes a potential topic for discussion. It doesn't matter much to me whether they paid for it, if there's proof it was completed (a code repo or documentation could be an alternative to paying for a certificate).

Any technology that I’m able to discuss intelligently is usually referenced as part of what I did on a job. I leave off any technology that I know but don’t want to be asked about or come up in a recruiter’s keyword search.

For instance, I don’t mention C/C++ even though I did it for 12 years or PHP.

I want my interviews to be focused on my strong areas and technologies that I want to use- which are usually the ones that I have real world experience with.

[thinkmassive]

Do you not consider hobbies to be real world experience?

Personally I appreciate the opportunity to not be stuck taking on new work that depends entirely on my previous employment. I find that people who pursue interests outside the scope of their day job tend to be good at thinking through problems and maintaining a healthy attitude, so I’m glad to discuss hobbies with people.

[scarface74]

Two thoughts:

Every job has “must have” requirements and “nice haves but be willing to learn”. I focus on jobs that will hire me based on the must haves where I can learn the nice to haves.

A lot of times that means the line between “work” and self study gets blurry. I might be “working” 60 hour weeks but producing 40 hours worth of work product and spending the rest of the time learning. That also means now my resume has work experience with the new-to-me technology/framework. It helps to work for small companies. You get more opportunities to learn and do low priority side projects on the job.

If that opportunity doesn’t avail itself, then do a side project and throw it up on GitHub and then we can discuss it.