>
>
> A few thoughts:
>
> 1. There are (always) people looking for jobs, and it should be easy
> enough to ignore unqualified applicants.
> 2. The phrase "Embedded Programming" could mean anything from writing
> 10F code to debounce a button, to writing  interface code on a high
> performance quad DSP VME SBC. I've done both, but someone with 2 years
> experience might not know the difference.
>

Ok, so how do I rephrase it to help them understand the difference and
which one I'm looking for?


> 3. Maybe the PhD likes your location and the proposed project. Maybe
> they have the skills to do something different. 4. I'm skeptical that
> a realistic candidate is asking 2-3 times what an engineer who does
> this work would actually get, unless you're trying to pay much too low
> a salary.
>

The one PhD I'm thinking of wanted 300k/year. I managed to end the phone
interview without laughing - barely.



> Which means literally:
> 5. If nobody is biting, you're not offering enough. You want a
> Microchip expert who knows control systems, mechatronics, C++
> application development. Are you offering 90k+?
>
>
There's only been the one that I've completely dismissed for financial
reasons. I'm hoping to start someone in the 50K range. 90k plus is not
unimaginable for someone that comes with exactly the right skillset and can
hit the ground running.

-Denny
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.