Here's how you fix hiring... Have them demonstrate competency.
It's really easy to screen out people when you say "Hey - login to this VM and show me how to import raw data into postgres and run a report."
Or do whatever you're going to do.
My favorite story is from a particular sean who had a candidate that said they'd been using VM for 20 years, and when he went into a document the candidate hit j 200 times to go line 200.
The issue at hand was to define vertexes with relationships and look up and track those. More writes than reads. I wasn't lead on it after the initial review and testing, but if you're doing something super simple, do it on postgress, I'd say. If you're doing something medium complex, use an off the shelf graphDB but beware rough edges and newness bugs. If you're doing something large scale and unique, talk to smarter people than me - I can introduce you :-)