It has been talked about before, but a solution to this would be to have slates stored on-chain, have slates be linked to user accounts, and let users delegate their voting power to a given user account's slate. (Basically an implementation of RDPOS.)
This way, a 'hiring manager' would not even need to be a delegate, just someone who owns a user account that has a slate. He could run for being a delegate as well, of course.
This may lead to something that can be labeled as centralization (everyone just gives their votes to bytemaster), however it is centralization that is approved in a decentralized way, and is easily reversible unlike the locked-in centralization in Bitcoin due to mining.
Ways to help minimize the centralization that occurs:
1. Allow a percentage of your voting power to vote for a particular slate
2. The ability to give your voting power to more than one slate
3. Slates can contain slates
4. The ability to maintain a percentage of your voting power manually
What this means:
Let's say I trust bytemaster, so I give you 40% of my voting power (40 votes). I also love what hpenvy is doing, and I know his votes will be up-to-date with the latest onramp and bizdev developments, so I give him 40% of my voting power as well (40 votes). The remaining 20% (21 votes) I keep to myself and use to vote for my own delegates.
Now, let's look at bytemaster's slate. Since he is very informed of the delegate campaigns overall, he has manually selected 60 delegates to vote for (60% of voting power). Since he cannot keep up with all the marketing efforts, he gives 10% of his votes to MethodX, 10% of his votes to hpenvy. He has left 20% of his voting power unused.
I could go on and describe hpenvy's slate, MethodX's slate, etc, however I think you get the picture here.
There are clearly things that need to be worked out with this model:
1. How to distribute votes among a subset of a user's slate (if I vote for 1% of bytemaster's slate, who in his slate gets the lucky single vote?)
2. How to handle recursive slates (bytemaster gives 20% of his slate to hpenvy, and hpenvy gives 20% of his slate to bytemaster)
3. How to handle incomplete slates (if I give 20% of my voting power to someone with only 10 delegates selected, do they get 2 votes or all 10?)
4. Blockchain bloat, processing overhead?
I do think though, that with some thought that these things can be worked out reasonably. Input appreciated.