News for hackers. Stuff that matters.
Re:Reviewing Bad Schematics as EE Interview Tactic by fest on Monday December 23, 2019 @06:01PM (#21868260)
Things that come to mind for bad schematic review:

* Linear voltage regulator with high input voltage powering an obviously very power hungry load.

* No ESD protection/current limiting for sensitive pins exposed to outside world.

* Tantalum capacitors with very narrow voltage rating margin

Another tactic I like (something similar is mentioned in sibling comment): a small design problem representative of real life task.

For generic EE position I like the following: "Suppose there is a project using this microcontroller. Project requires this micro to power an externally connected solenoid with this specification."

I find this reveals a lot of the seniority/thought process of the candidate: what (if any) questions candidate is asking to better understand the problem ("Do I need to consider output short circuit? What are the cost/size constraints? Don't we need a internal/external feedback?"), what is their process of component selection (if that is required in job description) and the suitability of this process for the needs of particular company.

Now, if only I could come up with similar strategies for software positions...

Re:Reviewing Bad Schematics as EE Interview Tactic by dws on Monday December 23, 2019 @08:12PM (#21869045)
The same approach works. Under-specify a problem, then see what questions candidate asks, and at what level they jump in. When Windows used to ship with Minesweeper, I'd ask candidates how they'd approach implementing Minesweeper for a touchscreen on an embedded device. Good candidates would get clarity on hardware and constraints first.