The question depends upon what type of engineer you are dealing with. EE should know EE things, SE should know softwre things, and CE should know civil engineering things. So you really have to put this question in context.
As a systems engineer, I could answer correctly on a wide range of engineerng topics that are not part of any particular engineering field.
Plus good engineers, are also knowledgable on any engineering discipline that interacts with their field.
In one job interview the interviewer sketched the symbol for a 4-way 2 position valve and asked if I understood what it was. I was able to explain in more detail than he had been expecting. Not bad for an EE? My goal has been to learn a lot about everything related to the work that I do, which has been valuable over the years. I have not figured out the answer about the cream and coffee, but any explanation would be interesting.
Even among EEs, there is so much specialization, it would be easy to stump a "real" engineer with questions that are outside of his area of expertise.
Ask a digital EE, even a very talented one, to explain the difference between S11, S12, S21 and S22 and you may get a vague answer like "I learned about that in school a long time ago but I never had to use them."
Ask an RF guy, or a data converter designer to explain how a cache memory controller works and you may get a similar "huh?" kind of blank stare...
That's the challenge: to find a question that just about any EE would know the answer to--but fakers wouldn't!
I once read a mystery story--don't remember by whom--where the detective figured out the nature of the murderer by a crossword puzzle partially filled in that he left-behind; the detective figured out that the murderer "hung around" with chess players but did not actually play, because he filled in an item about way the game is played, but not one related to board set-up: that the white square is positioned to the right-hand corner of the board--which is something every player knows, but is never spoken about, no need to.
I once read an article about how to make a set of cufflinks from a pair of old blown 2N3055 transistors. The object being that anyone who recognised them would probably start a conversation. But then how many new engineers would know the 2N3055 these days? (And how many would wear cufflinks??)
I remember reading that story and thinking TO-3 cases would be a bit too ostentatious, maybe 2N3054's (TO-66) would be better. The 2N3053 was in the small can (TO-39 for transistors, TO-5 for ICs with 8 leads). I've got a bunch of 709's, 741's and even 555's in the old TO-5 cans if you'd like some?? :-)
Consider asking a EE what the effect on a resistor that temperature has or on a transistor. I do wonder how many EE grads have grounding in the basic physics of the devices. What is the effect on CMOS devices of temp/voltage?
Suggestion for a power engineer:
Draw a standard simple single-phase rectifier bridge comprised of a 4-diode bridge and DC capacitor. The AC feed to this is (lethal) mains supply, and the DC load is a resistor, the capacitor is sized such that voltage ripple is small. Ask them to draw waveforms in correct time relation of: AC voltage, current in the AC lines, current in the capacitor, voltage and current in the load resistor, and voltage and current for ONE diode.
Then tell them: OK, now you have this set-up operating on your test-bench, and you want to look at the voltage across the load resistor. The test bench has a standard scope - show how you would set up the test bench to do this. (You could say "mains-powered scope" but that could be giving too much away, best to see if they ask for clarification first - better yet, prepare the drawing showing a scope with a mains lead attached.)
You would be amazed at how many power engineers think that it is OK to connect the earth of the scope probe directly to the negative output of said rectifier, without considering whether either the rectifier or the scope should be powered from a mains isolation transformer.
Then if they do mention "oh, you need a mains isolation transformer" the next question is: OK, the test bench has one of those; now where is the best (safest) place to put it, on the supply to the rectifier or the scope?"
For those that know their stuff, there is only one answer... and it could mean the difference between life and death....
At one job interview I was asked to the lab to demonstrate I could use a current probe and digital storage scope to measure the startup current surge of a piece of equipment. Did that easily, but still no job.
Another interview I was drawn a diagram of RF amplifiers, attenuators, splitters and was asked to determine the final output with 10 dBm input. The interviewer did not agree with my answer, he had forgotten that a 2 way power splitter is -3 dB, not -6 dB. After we discussed his error he said "Do you realize how many candidates cannot do this?" Got the job.
What about this one:
You like milk and sugar in your coffee.
Should you put milk in your coffee before stirring or after stirring if you want to have the hottest drink?
This system can be described by overwhelming equations but a simple knowledge about heat transfer should be all you need to answer...
I actually think about the answer to this when making coffee :) However, I can't think of an EE or CE job where Newton's Law of Cooling would predispose a candidate to be a better engineer.
On the other hand, engineers with physics degrees aren't too shabby. And I confess bias on this statement!
Should we consider the extra stirring required due to the change in solubility at the lower temperature or is the "correct" answer based solely on the conjecture that the problem is 100% bounded by a simple thermodynamics model? If the candidate does approach the problem outside the bounds of your conjectured correct answer, is he then deemed incompetent?
Any arguments are good as long as the candidate can justify them.
Taking such considerations as the solubility into account tells a lot about the candidates understanding of physical phenomenons. However on the other hand, in engineering it is often much better to simplify a problem as much as possible without significantly change of the result. I.e. in this case ignore the solubility issue and assume same stirring time. After all, how can you tell if the sugar is actually dissolved or not when the coffee is strong - let alone with milk?
But bottom line: any assumption goes if justified by arguments. The arguments tells as much about the candidate as the result.
I would think that you put the milk in first so that the overall liquid temperature is lowered up front, thus lowering the heat loss through the cup surface (for a short time) and conduction through the spoon. I'm geeky enough that I've actually thought about this when fixing my coffee in the morning. I can't even talk to my wife about details like this because she sometimes thinks I'm half-looney. :-]
It took my wife about 5 years to really grok the implications of being married to an engineer. She will still look at me and proclaim "You are a freak of Nature".
but the bright side is I generally don't do things that make her mad. She was a Marine. Helps that I make her laugh.
My Christmas present to her this year is going to be a WizBang Chicken Plucker. She is always mellow after slaughtering 40..50 chickens, but the plucking is the downside.
No, that was called the coffee problem in differential equations. Let the coffee cool first before putting in the milk. The coffee will cool down faster when the temperature difference to the rest of the environment is greater. Then add the milk.
So to have the coldest coffee: Add milk late, and vice-versa.
It assumes that the milk is _colder_ than the coffee!
It's not a caffe-latte for instance, where this assumption would not necessarily be true.
For a embedded systems designer (who should know both analog and digital):
Question: we have several analog signals coming in to an analog MUX, and considering the signal paths and the MUX itself, the effective signal impedance at the output of the MUX is 1kohms. We need to acquire the MUX output with a 10-bit A to D. The input to the sample-and-hold has capacitance of 100pF. What is the fastest sample rate to ensure accuracy of better than 1/2 lsb?
I've had answers like "oh, that's easy, that's just the Nyquist rate, twice the frequency of highest frequency the signal contains", or "There's no limit, just whatever speed the AD can handle".
The right answer can be obtained without a calculator or even pencil and paper.
Then ask them to draw a typical A/D front end, showing analog signals, analog MUX, S+H, A/D, showing how they would connect the analog ground, and digital grounds to the MUX select pins, and ask what effect there would be if some of the current going to the MUX select pins also flowed in part of the analog gnd... the fun really starts then...!
If I understand this correctly its essentially a voltage divider circuit, where you want Vcap to be within 10^2 / 2 of Vsig. Vcap / Vsig = 1 / sqrt(1+(2*pi*f*C)^2).. Seems like a pencil would come in handy.. Unless I'm totally mistaken
Maybe I'm missing something, but I think what Fabio007 is looking for in part is the settling time of an RC system: if your input impedance is R, how long before the voltage across the holding capacitor C stabilizes.
In the instance above, the time constant of the system is R*C = 100ns. An RC system is generally considered settled at 5*tau (98.2% charged - had to look up the percentage).
You would have to wait at least 500ns per sample, plus corrections for 1/2 lsb based on the ADC, plus ADC calculation time. On a per-channel basis, switching and settling time of the MUX comes into play.
Correct PatrickYO, I was looking for the candidates understanding of "settling time"; nothing to do with Nyquist rates... The aim is to tease out the candidates practical understanding of how signals can be acquired accurately, and many engineers simply do not understand the basics - that signals have impedance, that capacitors need time to charge/discharge, and that careful attention to analog signal paths (and a host of other practical issues!) is required before even a 16bit ADCs can be used to its full accuracy with any confidence, let alone these 24-bit wonders...!
For a 10bit ADC, the least sig bit represents 1x10E-03 (actually, 1/1024) of the FSD of the signal. So, the voltage on the 100pF cap must get to 0.999 of its final value. Some basic math shows that this requires a time of about 7 taus (RC time constants), which is 7 x 100ns in this case.
Perhaps one can argue that knowing that a 10bit DAC needs 7 taus of setting time is a bit specialised; I mean, that number is very specific to 10-bit DACs, of course. However, 10-bit ADCs are very common, and I would expect an engineer involved in any form of signal interfacing to know this to within +/- 1 tau.
This discussion no VCC and also the one on anode and cathode brings up something I've dwelled on in the past. Often when one is in school, such terms will be presented but not always explained as to why the word itself is used and what its significance is. This can unfortunately make the study of engineering seem much more mysterious than it really should be. A good engineering education should include the explanation of various words and abbreviations and their origins.
@seaEE: Yes I Completely agree, having an understanding of why certain terms are used makes it clearer, and easier to remember, and actually puts a human story to the learning. The story of how the transistor got its name, for instance: "transistor" comes from "transconductance-varistor", refer here:
Re: VCC: I learned that the "cc" sub-script for positive supply rails meant "collector-collector" rather than "common-collector", for the same reason that negative rails had sub-script "ee" for "emitter-emitter" ie: just for emphasis... maybe others have different views about this..??
Asking the history or makeup of certain terms might be going a bit far. I've never heard of where "ee" or "cc" comes from (at least I can't remember). And, even though I know pretty well how transistors work, I would have never remembered how the word "transistor" evolved.
The problem with 'questions that a real engineer would know the answers to' is this: I'm most emphatically NOT an engineer, damn, I can hardly keep pico, femto, nano and nono farads straight - I'm a hobbyist. But I know the answers (yes, without cheating) to the 'DIP' problem, 0 = 32 and 212 = 100, -40 = -40. So there's some right, right off the bat. The 'high voltage' question I'm guessing is lower current, reduced copper required, lower heat (and I'm hoping that whoever corrects me is polite) and the most important question, the difference between static and dynamic ram? The static ram is dead, the dynamic ram is frolicking with the sheep.
I had an interviewer ask me to picture a cube of wood painted on all sides, cut three times through each face (like a Rubik's Cube). How many of the resulting pieces are painted on two sides? Three sides?
Engineers find it difficult to believe that non-engineers have difficulty visualizing things like this.
I have my standard obscure interview question that candidates answer to varying degrees of accuracy. But, I am more interested in how they answer than what they answer. Are they curious? Do they approach it as a challenge or a threat? Do they ask questions? Are they working the problem or do they go for the quick answer? We can train them in what they need to know but they will be lost if they do not know how to figure it out.
That's a good hardware engineer design question. You could come up with those types of questions for RF, digital and analog engineers. These days, if the board design is no good, it's not going to work.
Another good question for high speed digital guys, got this from Dr Bogatin... Lets say we have a 50 ohm coax cable stretched between earth and the moon. It is open on both ends. If you put a standard ohmmeter between the two conductors at one end what would you measure? This reveals their understanding of transmission lines, and what impedance really is.
Another good one! Um, about 2 seconds reading 50 ohms, then open when the reflected round trip charge returns.
Long ago a customer tried to return a length of RG8 to a Heathkit store (one of my first jobs) because it did not measure 50 ohms on his ohmeter. It took a bit of explaining, just like having to rectify another customer's firm belief that LSB and USB (upper sideband, not universal serial bus) signals were generated by a diode clipping the negative or positive peaks from the RF signal.
It takes all kinds...
Wouldn't it theoretically go up and down a bit while the signal reflects back and forth and eventually attenuates itself down to nothing? I guess that would depend on the impedance of your meter too...?
Ya gotta love those customers....
Right you are, but am conveniently neglecting attenuation and the resistance of the copper and making assumptions of the "ideal lossless" transmission line. So, assume a center superconductor and outer cylindrical superconductor with zero ohms resistance, and assume zero dielectric absorption. And assume the meter has 50 ohms series impedance (cancelled in its reading) to terminate the reflection. But even if the meter looked high impedance, the energy being reflected is from the original pulse, so the meter should not respond. (My head is beginning to hurt...)
All these assumes, u know what that makes me? :)
Also assume the cable is weightless, otherwise could not support its own weight of almost 400 kilometers.
Now to get a bit more serious, I think the meter reading would very quickly rise over time due to the copper resistance of a real cable. I remember seeing that effect with TDR measurements on pcb traces, the longer the length the impedance increased by a few ohms.
Is a very interesting question for a job interview or discussion over pints.
Sorry, but you just described a high voltage power source. A standard ohmmeter would vaporize on contact! Lookup discussions of "Tethers in Space Handbook" (NASA & Smithsonian).
The first cable I designed for a vacuum chamber got laughed at (thought not meanly) because MY design called for standard Cadmium plated backshells on the connectors. How many engineers would know that in a vacuum, Cadmium evaporates, and then plates out on cooler surfaces. In this instance it would have been the cooled IR sensor we were to test.
What toys did you play with as a kid?
If the answer is legos, Erector set (Meccano), or anything else of similar nature - yep, they is an engineer.
I have 35 years in the biz, been an embedded systems engineer for the last 20+, but only play EE on TV. But - I can tell EE's what I need and how I want the device controlled.
Actually, I would ask about their pet peeves - the bad design decisions and why they are bad and why they are unhappy. (I have some choice words about status bits that clear when you read them if I ever meet the guy who designed the 16550. Grrrrr.)
Talking about one's mistakes is a useful thing (if not abused for making the mistake - a separate and long rant).
My point is: as engineers, we have to deal with brain-damaged decisions by other engineers (granted that they are either under pressure from management, or do not understand the person who will be using their design, or the design is mis-applied.)
As someone who has lots of years writing device drivers, I have seen a lot of EE-driven designs that are *very* difficult to control. My simple, personal example is status registers that clear themselves when you read them. See the 16550 UART. I want to be able to *explicitly* clear the status bits. Yes, there is a fairly simple work-around, but there are plenty of examples that cause me to desire that a device should be designed, or at least spec'd, by the poor schmuck that has to write the driver.
Simply put, if you have a good example of a brain-damaged design, you have experience to be a "real engineer".
in the "glory days" of DIP ICs, we would take an unmarked IC, place it on a table, ask the person to look at it, and then close his or her eyes for a few seconds. We'd rotate the package 180°, then ask them to open their eyes and tell us if they saw anything different about it. If they said "no", we knew they weren't a real EE
you can even ask these question which is better than your one:
resistor, color, red green yellow and gold.
capacitor, 104, 101, how much?
How much is this chip's fun out.....
what is fuzzy control:)
here you are.
I once interviewed for a job where one of the questions was "what's two to the twelfth power?" I answered so fast and so matter-of-fact that the interviewer did a double take and paused a second to comprehend what had just happened. Heck, I knew the answer to that as well as I knew my own name. But I'll grant that's a "niche" test, not a universal one.
More generally, I think engineers NOTICE things in their environment: odd mechanical noises, a wobbly chair, a clock that's stopped.
I once was walking across an unfamiliar college campus and a professor happened to walk by in the opposite direction. He stopped and introduced himself - very much the "people person" - and immediately said "you're an engineer, aren't you." I don't know all the clues he used, but I wish I did.
I'm sure the pocket protector with 8 different colored pens + mechanical pencil and separate eraser wasn't a clue :^) ... I was going to lunch with a friend I was working with. As we left the building, he took off his badge to "de-nerd himself." When I pointed out the pocket protector, HP calculator on the belt, etc, he looked abashed, and gave up on the task.
I was in a Costco standing in line at the pharmacy, and lifted the plastic pipe protector (there to guard the corner of the wall). A woman in line said "You must be an engineer", and I asked her what the clue was. She said she was a realtor, and could always spot the engineers, because they looked under the sinks at the plumbing, and no other group (other than plumbers) did so.
Two engineering students meet up on campus. One had a new bike. The other commented on it, and the first recounted how a gal had ridden up on the bike, got off, took off her clothes, and said "You can have anything you want." The other replied "Good choice, the clothes wouldn't fit."
I once interviewed at a company who gave a test with some really basic analog and digital stuff on it. They apologized for insulting my intelligence and said that originally it was their technician test, but they started using it as an engineer weed-out test. I said it was really easy, but I didn't have a clue about the C programming language part (I'm a hardware guy). Proves the assertion that very competent engineers may not know anything about stuff outside their area of specialty. They didn't offer me a job, and later I found out it was a lousy place to work, and I was glad they didn't!
When I was about 6 years old, my father (an EE) asked me to write a description of how a flashlight works. (This was decades before LEDs-- just a tungsten lamp, dry cells, and switch.) He would then ask candidates the same question, and use my paper as the standard by which their replys were graded. Of course, any engineer knows how a flashlight works. But surprisingly few are capable of explaining it coherently and simply, and their ability to do so tells a lot about their engineering skills, of which communication is one of the most important. It proved a quite effective test.
With a Math background (like many in SE) i find the Monty Hall problem (http://en.wikipedia.org/wiki/Monty_Hall_problem) exquisitely sensitive and definitive in identifying technical poseurs. Even if a candidate initially gives the intuitive (wrong) answer, after the correct solution is explained only those incapable of "thinking like an engineer" continue to insist on "going with their gut", and sticking with their original decision.
The link doesn't work, this should with luck:
I find if you put links in the text they go wrong, if you put them on a separate line with blank line above and below, they work. Lets see if I'm right.....
My favorite quiz question is this:
Given two glasses of equal volume, containing different (though miscible) liquids (though it could be fine powders, too): Take a teaspoon of "A" and place it in "B." Stir well. Then take a teaspoon from "B" (which has a little "A" in it), and put it back in "A."
Here's the question: Is there more "A" in glass "B," or more "B" in glass "A"? And why?
There are a number of ways to solve this. Pure algebra, by using coarse examples ("Let's say I have 1,000 colored pebbles in each glass..."), and (my favorite) an elegant logic-based solution.
Again, it's good if they get it right, but it's a way to see how they work through problems.
This one should work with any engineering discipline:
Set an 12 ounce glass containing 6 ounces of water on the table and ask the interviewee to describe it.
The liberal arts optimist will say it is a half-full glass of water.
The liberal arts pessimist will say it is a half-empty glass of water.
The engineer will say that the glass is twice as big as it needs to be.
Not twice, because the required headroom to adequately prevent spillage would be determined by the diameter of the opening and the motion of any movement. Certainly, though, it is overly large for its required task.
On the other hand, the same engineer that would use a 10V capacitor in a 5V circuit might say that the glass is sized exactly at the capacity needed.
Why not just ask them up front what area(s) of engineering they have experience in and/or are best at? Then throw the appropriate questions at them. Also, add a wide range of very easy questions just to see if they remember anything from school or have learned anything outside their (hopefully) strong areas.
My favourite test for techs is a simple diagram of 4-20mA loop between two boxes. One containing the process indicator, the other the transmitter. Between them is a detachable cable. Each box has 24 screws to open. The candidate is asked to determine the fault- the customer is waiting.
His virtual tool box contains anything he/she thinks he/she needs. I provide the results to his virtual tests.
The experienced ones usually jump to ohming the cable because it is the highest probability, but they usually forget to test for shorts.
Some can make a few tests before deciding to undo 24 screws to make a test they could have done from the cable connector.
Many fail to ask if the power is on before tearing the system apart.
Sadly, few have aced the test.
Experience, knowledge, practical sense, and performance under pressure, all revealed from a excercise nearly as simple as a battery and light bulb.
1. The fuse test - A long time ago we used to give rercuits a 20mm glas fuse and ask them which end was the positive and which negative. If the recruit looked to see if it was marked, he failed (you'd be suprised how many...)
2. Draw a wiring diagram of a stairway light that can be switched on or off at either end of the stairway (you'd be suprised how many can't...)
My thought process would be: 'This looks like a fuse, of course, but it might be a recent development in the field and they want to know if I am up-to-date. So I would look at it.'
Engineers specifically do not think like con-men when dealing with people. They do, however, specifically learn not to be naive about trusting stuff that has been made by people. the physical world. In this case I would question my knowledge being current (it ages several times faster than I do). Being trusting with people or taking things literally, are characteristics of engineers (for better or worse) and testing for them isn't a negative.
I also suspect I might look at the fuse anyway as I was thinking, simply because I always would look at something given to me in a test.
My standard analog test is a zener shunt regulator. A few can correctly solve for the ballast resistor, but how much more they can say about what is going on is very revealing.
As a simple embodiment of non-linear resistance behaviour in a practical circuit it takes some beating.
They tell me they never looked at a zener in the same way again.
Next I would ask an candidate to explain what is actually going on in an inductor, and why we should care.
More mechanically, it is always fun to ask how the energy is stored in a spinning flywheel.
The better their maths, the harder it is to get the simple answer.
Greetings from Denmark. As an EE I once had a MEMS course together with a group of physics students. During the lectures on simple electronics I was stumped at how little they actually knew about electrical networks. Filters were way out of their league, and we are talking about master students in their final year. So to identify a true EE I would simly ask for the expression for the 3dB frequency of a simple RC filter. That is something that every EE knows, no matter the specialisation.
Have a small device on the table that isn't screwed together. Se how much time is spent looking inside, how long is spent operating it.
Engineers are more interested in what us inside something than what it does.
This assumes the device is a well-known gadget, not a functioning TriCorder!
For hardware types ask them to draw a full wave bridge rectifier.
At one place a recent-grad systems engineer was hired to do board repair. When asked to identify components, he said "I think those are resistors because they have colours on them."
He lasted about a week.
CATHODE == Cat on a hot tin roof...
If you point the diode where the triangle points up; it looks like a roof. That side is the CATHODE. I always forget stuff too. This is why I use mnemonics and other stuff to help me remember.
Anode is the Arrow end. Both begin with A.
The cathode bar is marked as a band or dot on the diode body. So why are electrolytic capacitors marked on the negative lead and tantalum capacitors marked on the positive lead?
For a real engineer, ask how many soldering irons they own. We tend to upgrade from a simple one when we can afford it, but can't get rid of the old one because it may be useful for something. Then there are high power units for big jobs.
I ask, "What have you built at home recently?" -- most good engineers are always building something, even if it's not technical. Also, "What books have you read recently?" If they give you a blank look, it's a bad sign IMHO. Engineers seem to prefer hard SF.
In my opinion ... there are really no good tests. I have seen real EE-PhD fail miserably doing real projects with real consequences. I have seen technicians with just an AA degree literally pulling our collective buttocks out of the proverbial fire. I have also seen the inverse of this statement too.
In general, I talk to the interviewee about the projects they have worked on. Most of my assessment is in general social in nature ... Things like body language, facial gestures and such.
I can usually determine, within about 10-15 minutes or so whether or not a candidate, (employee or consultant), whether or not they will work our or be in over their heads.
Many times, I remind folks that there are usually many many ways to solve a problem. Solving problems is primarily what we, as engineers are hired to do.
A few more:
Ask if they know what a junkbox is and how big is theirs? REAL engineers NEVER throw anything away (until their managers or wives demand them to).
Ask why the B in dB is always printed in upper case, except on old Winamp skins.
Ask them to correlate colour code to numbers, or at least recite the usual resistor colour code memorization crutch - "Bad Boys ... " etc
Ask how to relate pico nano micro milli Kilo Mega
And for the real old timers who used to smoke, can you light a cigarette from a soldering iron? (answer is yes, but it takes a while)
Maybe the question could be ,what undesirable effects would occur if two paths in a PCB very close to each other carried a
1.High frequency signal
2.A low frequency signal
(I was asked this and I couldnt answer)
The question seems irrelevant. Define the set of skills you look for (technical and social), the level of experience and try to asses those. If you need soldering skills then you can just ask some one to show their skills. Most important is that the candidate can solve problems independently, in this case he will add value to the team.
I have hired quite a few SW engineers. My track record is pretty good. During the interview I try to get these 3 questions answered in this priority:
Do you work hard?
Do you get along with other people?
Can you do the job?
Engineering managers can focus so much on the technical, they hire people who don't work out. A good SW engineer can pick up a new tool or language in short order, but a lazy or obnoxious employee will upset the teamwork needed to get the job done.
Finally a response that I agree with. I don't understand the chest-thumping going on here about trying to stump engineers. The thing I learned the most in university was how to learn. If someone tried to stump me with a riddle or old-school question about resistor colors I would not be interested in working there (too old school for me). EE has moved on. There's a lot more than PIC microcontrollers and color-coded resistors today.
If anything, I would prefer an engineer who can learn something quickly and efficiently versus one that knows old basics.
Seriously...a resistor color code chart question??? I haven't used one in over 10 years and I am in my early 30's. We have multimeters today that can read resistor values. Plus the resistors I have used in products are so small a sneeze would blow hundreds of them away.
Having a good manager is good for morale. I made a caption for this month's Unicycle cartoon referring to a juggler that was inspired by a highly talented previous boss. He had been known as "Le Jongleur" at his previous position because he could juggle many projects at the same time.
I don't suppose your initials happen to be YT by chance?
No, but I've been a card carrying member of the International Juggler's Association for many years. I'm not a serious unicyclist, just enough to juggle on, but I'll have to check out the cartoon. Unfortunately, my company only allows career path progression through management, fortunately excellent engineers who are poor managers are allowed to return to the technical side.
I absolutely agree. Specific skills are easily learned. I look for the ability to learn.
What I find most important is if the interviewee asks lots of probing questions and is not frightened to show their ignorance of specific details. That tells me they won't just sit in the corner stuck for hours.
One of the best embedded software guys I ever hired had done business computing. He was a wizard at Visual basic and databases and had never programmed in C. Within a month he was reading schematics and writing interrupt service routines.
Right... the interviewer has to be intelligent enough to pick out the right person for the position. It's as simple as that. If the interviewer isn't intelligent enough for that, there are other problems within the company.
If you want to know if someone is an engineer ask how there last project went, what was good and what problems did they have.
This is a very fair question for the candidate as they should be an expert in their last project and you won’t get false negatives with good engineers who just happen to have a blind spot on your special question.
If you want to know if they are a good engineer then ask what problems other people on your project had and were they able to help them.
Notice the questions do not use the word technical problems allowing someone to start talking about non-technical issues which may be where their comfort zone is.
In theory someone could fake it by talking about the experiences of an engineer they knew. In practice if they are a real engineer there response should start an interesting conversation.
I once interview someone who in response to these questions got into a rage about how other people on his project would not listen to him and they were doing it a wrong. He was clearly an engineer but not one I wanted to work with.
The test for the new manage is much easier.
Where you get a new manager and a suitable technical problem occurs, go into his office and describe the problem and ask if he has any suggestions.
This is a good question because the problem could be hardware, software or a systems issue and anyone with a technical background should have something to say. If he looks at you with a blank face you’ve got problems.
I'm trying to remember some of the questions I was asked when I was interviewed. One involved two capacitors connected by a switch, with a charge on one of them. What happens when the switch is closed? I believe it was a resistanceless circuit. ;) It was kind of a theoretical question. Another, I believe, involved the gain of a a differential amplifier created with bipolar transistors. Another involved a D flip-flop. I believe there was a simple op-amp question. I remember in the interview mentioning to the interviewer something about a pot-core transformer from our student project, and then wishing I hadn't because it turned out he was a magnetics expert!
I'm not sure what other questions there were. Maybe there was a question regarding a resistor voltage divider.
Toss a small dense object up a few feet. Ask where the point of maximum acceleration is. (while the object is in flight and ignoring air resistance).
Propose a small metal box with two terminals accessible. There is either a 5V voltage source with a 1 ohm resistor in series or a 5A current source with a 1 ohm resistor in parallel inside.
Can the candidate tell which it is?
quote: ignoring air resistance...
Also ignoring distance from the earth (or moon or whatever)? The gravitational pull decreases as the item moves further away from a large mass, so the acceleration would be greatest just before hitting the ground (assuming no gas resistance, of course).
Not sure I agree with the color code as a test--that's more a test of how long they have been around, and how good their memory still is!
I've been in this business a long time, haven't needed to use or know the color code since way back when. So even a good, but newer, engineer would fail the color-code test, IMO.
If you have to make a quiz like that you are uncertain of your own skills rather than the others.
Maybe you should read about the topic and learn.
If you have god skill in a field you know if the other person is real or not.
And you are not afraid to ask him to explain himself.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.