As a more experienced dev told me when I was unemployed "Treat finding a job like a job itself. Allocate a good portion of time to it, teach yourself, find realistic problems and solve them."

I feel like this would be a great feature if it were on a type of schedule, whether self imposed or baked into the feature itself.

e.g Check email at 9am, read question, do some research on the domain of the question, write some code, test the code, post it up somewhere for 'peer' review, rinse, repeat.

Writing blog posts about it would also be a solid idea to track your progress, and have something to show potential employers your reasoning, thought process, technical writing abilities. Things that employers/managers look for without actually saying it.

All that would depend on the quality and relevance of the questions though.

e.g "This VM disk image was cloned from a server that, for some reason, crashed due to OOM errors. It includes documentation, code and a snapshot of a 'live' system. Investigate, fix the code and write a post mortem"

and not

"Write a function that reverses a list in log(n()whatever) time, washes the dishes, walks the dog, blah blah blah" university nonsense.

Realistic, domain specific, catered questions that actually pertain to what you will actually be doing as a developer at any given company.