<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to get a job as a new electrical engineer grad</title>
	<atom:link href="http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/</link>
	<description>Combining renewable energy, analog design and some real life experience. A delicious stew of engineering!</description>
	<lastBuildDate>Sat, 06 Mar 2010 14:12:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: How to Work a Job Fair as an Engineer &#124; Chris Gammell's Analog Life</title>
		<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/comment-page-1/#comment-1189</link>
		<dc:creator>How to Work a Job Fair as an Engineer &#124; Chris Gammell's Analog Life</dc:creator>
		<pubDate>Thu, 01 Oct 2009 03:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=365#comment-1189</guid>
		<description>[...] amount of preparatory work researching the companies you&#8217;re targeting will let you know what skills a company is looking for. Hell, it&#8217;s in the company&#8217;s interest to be vague when they list what kind of employee [...]</description>
		<content:encoded><![CDATA[<p>[...] amount of preparatory work researching the companies you&#8217;re targeting will let you know what skills a company is looking for. Hell, it&#8217;s in the company&#8217;s interest to be vague when they list what kind of employee [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JG</title>
		<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/comment-page-1/#comment-1020</link>
		<dc:creator>JG</dc:creator>
		<pubDate>Tue, 21 Jul 2009 01:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=365#comment-1020</guid>
		<description>You can never be too good at math for EE also.

It&#039;s also useful to be aware that engineering is about models - all models are approximations at some point where the assumptions made go out the window.  Good engineers know the assumptions and when they can and can not trust a model to be a good enough representation of reality.  

Most engineers have a whole collection of models/intuitions that patch-work cover their understanding of the field.  We used to have an &quot;in joke&quot;: if you want a good laugh, ask a physicist to design a circuit for you; he&#039;ll start with Maxwell&#039;s equations and get back to you in a month.&quot;

The scariest example of not getting the model was when I TA&#039;ed a senior analog design lab and this one student (slated to graduate in a semester) clearly missed the entire point of Small Signal Models and couldn&#039;t wrap his head around why he could not get 100V out of an amplifier with a gain of 100 when he put 1V in and used a 10V power supply.  He never got yet I couldn&#039;t fail him enough to prevent him from getting a degree which he clearly didn&#039;t deserve to hold.  He walked and got a BSEE.</description>
		<content:encoded><![CDATA[<p>You can never be too good at math for EE also.</p>
<p>It&#8217;s also useful to be aware that engineering is about models &#8211; all models are approximations at some point where the assumptions made go out the window.  Good engineers know the assumptions and when they can and can not trust a model to be a good enough representation of reality.  </p>
<p>Most engineers have a whole collection of models/intuitions that patch-work cover their understanding of the field.  We used to have an &#8220;in joke&#8221;: if you want a good laugh, ask a physicist to design a circuit for you; he&#8217;ll start with Maxwell&#8217;s equations and get back to you in a month.&#8221;</p>
<p>The scariest example of not getting the model was when I TA&#8217;ed a senior analog design lab and this one student (slated to graduate in a semester) clearly missed the entire point of Small Signal Models and couldn&#8217;t wrap his head around why he could not get 100V out of an amplifier with a gain of 100 when he put 1V in and used a 10V power supply.  He never got yet I couldn&#8217;t fail him enough to prevent him from getting a degree which he clearly didn&#8217;t deserve to hold.  He walked and got a BSEE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yeni Mezun Bir Elektrik Mühendisi Nasıl İş Bulur? &#171; Bir Öğrenim Görevlisinin Anıları</title>
		<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/comment-page-1/#comment-910</link>
		<dc:creator>Yeni Mezun Bir Elektrik Mühendisi Nasıl İş Bulur? &#171; Bir Öğrenim Görevlisinin Anıları</dc:creator>
		<pubDate>Wed, 29 Apr 2009 00:50:56 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=365#comment-910</guid>
		<description>[...] Yeni bir elektrik mühendisliği mezunu nasıl iş kapar başlıklı yazısını da belirtmeden geçemeyeceğim. [...]</description>
		<content:encoded><![CDATA[<p>[...] Yeni bir elektrik mühendisliği mezunu nasıl iş kapar başlıklı yazısını da belirtmeden geçemeyeceğim. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnie Lerma</title>
		<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/comment-page-1/#comment-884</link>
		<dc:creator>Arnie Lerma</dc:creator>
		<pubDate>Sat, 18 Apr 2009 17:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=365#comment-884</guid>
		<description>Nice article, these ideas allow one to run rough circuit simulations in your mind, which makes fixing the problem, on the spot, which what you happen to have in your toolbox, far easier. For readers who benefited from Chris Gammell&#039;s article, this old analog engineer  would recommend &quot;The Art of Electronics&quot; by Paul Horowitz...</description>
		<content:encoded><![CDATA[<p>Nice article, these ideas allow one to run rough circuit simulations in your mind, which makes fixing the problem, on the spot, which what you happen to have in your toolbox, far easier. For readers who benefited from Chris Gammell&#8217;s article, this old analog engineer  would recommend &#8220;The Art of Electronics&#8221; by Paul Horowitz&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://chrisgammell.com/2008/10/10/how-to-get-job-as-a-new-electrical-engineer-grad/comment-page-1/#comment-534</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Sun, 14 Dec 2008 00:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://chrisgammell.com/?p=365#comment-534</guid>
		<description>That is high praise Kamil. I didn&#039;t really dive into it with the expectation anyone was looking for it, but it doesn&#039;t make it any less true. If you want to be a mechanical engineer, make sure you understand what you&#039;re doing and why.

Most of that post I think deals with the skills and values of a successful engineer, but less to do with &quot;getting a job&quot;.  Having now interviewed several people for jobs (all entry level, so this doesn&#039;t apply as directly if you are looking for your 3rd or 4th), there&#039;s a few points I think are key.

1. Your resume to give potential employers a snapshot at your qualifications. Don&#039;t put non-relevant stuff on your resume, and don&#039;t point out your flaws. This isn&#039;t disengenous so much as it is smart advertising. Marlboro doesn&#039;t construct billboards that say &quot;smoking is totally worth getting lung cancer for&quot; whether they believe it or not. You know you&#039;re not perfect, employers know you&#039;re not perfect, and they aren&#039;t expecting to get perfection. Let them think what they like on that front. If you are an entry level engineer, keep it to one page. When you have 2 pages worth of relevant experience for a job and you want to list your qualifications, go for it. You probably have schooling and a couple internships or class projects that lay out your experience. If you don&#039;t, feel free to stick in a mention about your summer job installing shingles just because it shows you worked with people, and it will help make your resume memorable, but you don&#039;t have to go past that one job if it isn&#039;t relevant.

2. Read your resume before your interview, the interviewer read it, and is probably going to ask you some questions that branch from it and the last thing you want to do is look like you forgot what you wrote on it. I know I submitted a million resumes to places online, and usually made some tweaks to each depending on the position, so I would go back and look so I knew what path I had laid for myself.

3. Some interviewers like to &quot;test&quot; people on stuff. Probably they don&#039;t really care whether you get the right answer so much as whether you handle yourself well or choke. I&#039;m not really a big fan of the &quot;test&quot; but interviews have to start somewhere, and there needs to be a way to draw out the behavior of a person. Basically just be you, if you don&#039;t know something, say so. If you know more, elaborate and throw in an example or whatever. Some interviews take a more technical bent, and you can show off your skill with op-amps or whatever. Some are more behavioral and if you might not mention anything technical after the first sentence. What do you think about Favre playing for the Jets? This gets at the whole communication thing. If you can make some conversation with people you don&#039;t know, it speaks well to your ability to communicate in your job.</description>
		<content:encoded><![CDATA[<p>That is high praise Kamil. I didn&#8217;t really dive into it with the expectation anyone was looking for it, but it doesn&#8217;t make it any less true. If you want to be a mechanical engineer, make sure you understand what you&#8217;re doing and why.</p>
<p>Most of that post I think deals with the skills and values of a successful engineer, but less to do with &#8220;getting a job&#8221;.  Having now interviewed several people for jobs (all entry level, so this doesn&#8217;t apply as directly if you are looking for your 3rd or 4th), there&#8217;s a few points I think are key.</p>
<p>1. Your resume to give potential employers a snapshot at your qualifications. Don&#8217;t put non-relevant stuff on your resume, and don&#8217;t point out your flaws. This isn&#8217;t disengenous so much as it is smart advertising. Marlboro doesn&#8217;t construct billboards that say &#8220;smoking is totally worth getting lung cancer for&#8221; whether they believe it or not. You know you&#8217;re not perfect, employers know you&#8217;re not perfect, and they aren&#8217;t expecting to get perfection. Let them think what they like on that front. If you are an entry level engineer, keep it to one page. When you have 2 pages worth of relevant experience for a job and you want to list your qualifications, go for it. You probably have schooling and a couple internships or class projects that lay out your experience. If you don&#8217;t, feel free to stick in a mention about your summer job installing shingles just because it shows you worked with people, and it will help make your resume memorable, but you don&#8217;t have to go past that one job if it isn&#8217;t relevant.</p>
<p>2. Read your resume before your interview, the interviewer read it, and is probably going to ask you some questions that branch from it and the last thing you want to do is look like you forgot what you wrote on it. I know I submitted a million resumes to places online, and usually made some tweaks to each depending on the position, so I would go back and look so I knew what path I had laid for myself.</p>
<p>3. Some interviewers like to &#8220;test&#8221; people on stuff. Probably they don&#8217;t really care whether you get the right answer so much as whether you handle yourself well or choke. I&#8217;m not really a big fan of the &#8220;test&#8221; but interviews have to start somewhere, and there needs to be a way to draw out the behavior of a person. Basically just be you, if you don&#8217;t know something, say so. If you know more, elaborate and throw in an example or whatever. Some interviews take a more technical bent, and you can show off your skill with op-amps or whatever. Some are more behavioral and if you might not mention anything technical after the first sentence. What do you think about Favre playing for the Jets? This gets at the whole communication thing. If you can make some conversation with people you don&#8217;t know, it speaks well to your ability to communicate in your job.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
