<p>How much knowledge do companies expect interns to have? (Let's say a software engineering intern) Would the software they want you to develop be difficult? What if you aren't very experienced in a certain language and they expect you to write it?</p>
<p>They expect you to have as much knowledge as a slightly above average person in your grade I would say. You are really there for two reason: cheap labor and to train you for when you graduate and they can grab you then.</p>
<p>Often times companies will have a list of required and desired computer skills on the application. Most interns will be placed working in groups, so even if the task at hand is very difficult, you have help around you.</p>
<p>Tasks I have given our intern recently:</p>
<p>-Please print out the geotech report and put it in a three-ring binder
-Please z-fold all these 11x17s (and I taught him how to z-fold)
-Please take this to the County permit office (and I printed a map)
-Please take these documents downstairs, have them scanned, and put them in the folder I e-mailed to you.</p>
<p>These are the things I expect an intern to be able to do unassisted. </p>
<p>The best interns that I’ve had are the ones who are responsive (like, super-quick to get things done), who ask questions about why we do things a certain way, who admit that they’re a little bit lost and ask what the heck they’re supposed to be doing if given an engineering task, and who, when an engineering task is explained to them in a competent manner, can get the task done with little guidance. We had one intern who was totally open to learning what we do here. She was very responsive. Not only did she get a job offer with our firm for after she graduates, but I also tutored her through a few of her senior-level classes after she left the firm and went back to school full-time, and she’ll always be able to get a glowing recommendation letter from me.</p>
<p>I’d say it’s about the same at most other technical firms.</p>
<p>aibarr pretty much nailed it when it comes to interns.</p>
<p>It’s a nice tradeoff between students and companies. The companies get the benefit of cheap (or even free) labor from somebody that “should” have a decent head on their shoulders. The student gets the benefit of gaining some valuable work experience and the chance to put a nice company name on a resume, while hopefully gaining some good references and/or a job offer in the future.</p>
<p>As an intern you need to a) show up, b)listen up, c) do what you’re told to do, d) perform the tasks to the best of your ability, and e)ask questions and seek help when you don’t know what’s going on. </p>
<p>Companies don’t expect interns to be handling difficult tasks. If they have difficult tasks that can’t be handled by their current full time employees, they go out and hire/contract an expert to complete the task.</p>
<p>When I first started working in traffic engineering as an intern, I typically did the following:</p>
<ul>
<li>Collected data in the field, including but not limited to counting pedestrians, cars, trucks moving / turning in each direction; measuring streets, sidewalks, lanes; collecting data on parking regulations.</li>
<li>Printed and binded reports, including doing the z-folds (haha is that what they actually call it?)</li>
<li>Acting as a messenger, delivering documents to government agencies, clients, etc.</li>
<li>Data entry</li>
<li>CAD drawings</li>
</ul>
<p>As I continued working with the company, I got more and more responsibilities. Towards the end of my stay there, I was essentially acting as the “head intern,” for lack of a better word. For one project, I was charged with organizing the team of interns to collect the required data in the field. For another project, I was partnered with another intern and we essentially did all the work up to the interpretation of data (when the full-time engineer took over). The company began thinking of me as more of an entry-level employee because I essentially had the same training as everyone else by that time. </p>
<p>Companies don’t expect you to know everything when you start. Heck, they won’t expect you to know much at all if the field is somewhat specialized. The important part is being able to learn as you go, absorbing the information.</p>
<p>I started working for a local structural firm during winter break of my freshman year in 1980 and worked there every school break through grad school. At first, I mainly answered the phone, typed specs, and ran errands. Then they had me do some simple drafting. This was long before CAD, so I would do things like print out drawing titles on this nifty little machine, then stick the titles onto the drawings. I also babysat the computer - someone had to make sure the punch cards went through the machine smoothly! </p>
<p>After awhile, I did more complex drawings. Then they let me do engineering calculations, such as figuring out the loads on a 32-story building (that was the tallest building in Austin for many years, but now it looks tiny!). I also designed a lot of beams by hand. I got to know the engineers and draftsmen well, and really enjoyed myself. The firm told me they wanted to hire me, but then oil prices crashed and they had NO work. One of their engineers started his own company and made me an offer, but had to rescind it for the same reason. </p>
<p>At times, I felt a little lost, but the engineers and draftsmen were SO helpful. I found that if I gave it my best effort, they appreciated it and liked helping me. It gave me confidence when I started my first “real” job after I graduated, too.</p>
<p>
Wow, that takes me back!</p>
<p>The students I see are generally lacking knowledge in many areas and often need a good amount of help/OJT. Don’t feel like you’re not going to be able to handle it because you don’t fully understand everything the company/position may want you to understand.</p>