Oh, that boost converter guy, a BSEE, had no clue about opamps either. But it's weird that he put a design on his resume and wasn't prepared to discuss it. He claimed to have designed a boost converter and knows absolutely nothing about boost converters.
We did interview someone who understands voltage dividers and almost understands opamps. She's smart, so we could probably teach her stuff. Potential 3-month intern, to try it out.
ISTM you want the latter, but are so
I only plan to hire design engineers who can design electronics, and who will make us more than they cost. That's not unreasonable.
After reading resumes, we only interview a few people, one a week roughly, and that's not a big burden. It's interesting to meet people and see what's out there anyhow. Our preferred "test" is to whiteboard some circuits with them, including things that they put on their resume. If they can't even remember or understand their own projects, we don't want them.
Student projects are the worst. Practically no applicants can remember how they work.
$10K is cheap. Head hunters typically want 3 months salary. We'll consider them, too, if they can find us a good engineer. Headhunters could be a separate discussion.
The google thing is interesting.
We have tried working with universities, to send us kids who really like electronics. No results so far. Placement offices seem to have become profit centers, rather that operations that help students. Hey, most of academia works like that now.
Our web site should interest people who like to design circuits. Then we invite them in and whiteboard stuff, and let them sit in on our weekly engineering meeting. They can see what we do.
Brainstorming is great, and crappy ideas often inspire good ones. The google thing is interesting: pop an employment ad on a search for a technical item, rather than on an employment search.