Software Engineer Intern Resume.

[SeaPanda]

Hey guys, I'm starting to apply for internships for the summer and fall of 2017 and I have some basic questions that some of you more experienced members could help with.  

First off, can I use these as my resume templates? They look creative and less dull than the typical ones, but I'm not sure if they are professional. The Moo logo won't be there.

[Guest Kloaked]

I think it depends on where you're applying, but I do know that serious employers don't care about how pretty your resume looks. As long as you sell yourself well on it and it's readable (unlike the one on the left) you should be fine.

 

What would actually make your resume stand out is a headshot of yourself rather than the entire thing looking colorful and whatnot.

[Bac_]

If you're trying to look professional use a basic template. Make sure you format it well though (stick to basic serif fonts for body text like Times New Roman). Don't over-complicate things with colours and fancy templates, let the words do all the work.

[GoodBytes]

These "fancy" format resume doesn't help you getting a job from experience (MAYBE unless you are applying in art related degree, GUI level job, etc.)

Ultimately, for an intern, the company wants to see your passion and energy for software development.

 

A strong resume will depends on where you apply.

Some companies only care about your grades (even after you graduate).

Some companies wants to see how much you like developing and/or your creativity. In other words, they want to see: your participation in open source projects, and/or your personal projects. If its a basic calculator or something else basic like this or some class project, they have very little value (depending on where you apply: startup vs...say.. Microsoft), although team class project will bring interview questions to you, especially if you were the team leader. Questions often asks: What challenges did you face? What contribution that you do to the project? Was there any conflicts? If so, how did you deal with them?, etc.

 

School activity related to your passion of software development should be mentioned as well (I mean it shows your passion).

For every project, be sure to include the programming languages you used. For example:

---------------------------------------------------------------------------------

Super Cool Tool eXtreme – Software: MikeRowSoft.com/supercooltoolextreme                                          2016

·         Developed a tool that enhances the gamers experience by allowing the creation of macros using a standard layout keyboard. [C# using WPF and .NET]

---------------------------------------------------------------------------------

 

 

Hope this helps.

[SeaPanda]

2 minutes ago, Kloaked said:

I think it depends on where you're applying, but I do know that serious employers don't care about how pretty your resume looks. As long as you sell yourself well on it and it's readable (unlike the one on the left) you should be fine.

 

What would actually make your resume stand out is a headshot of yourself rather than the entire thing looking colorful and whatnot.

 

Okay, I figured I would use one of these templates because they have the "quick links" to email,phone, and github.

4 minutes ago, GoodBytes said:

These "fancy" format resume, doesn't help you getting a job from experience (unless you are applying in art related degree, GUI level job, etc.)

Ultimately, for an intern, the company wants to see your passion and energy for software development.

 

 

I'm applying for an intern position at some big companies... would you hire a sophomore, becoming a junior in the fall of 2017, with A's in all of his coding classes, network security & encryption, entry level programming  in Java, data structures in C++, and intermediate object programming in C sharp. I also know Python and a tad bit of ruby and I'm comfortable working on any OS. I also can pick up new languages quickly and are willing to learn. 

[GoodBytes]

2 hours ago, Sebastian Kurpiel said:

Okay, I figured I would use one of these templates because they have the "quick links" to email,phone, and github.

You can put these at the top of your resume, or next to the project that you are presenting (see example above in my updated post)

 

Quote

I'm applying for an intern position at some big companies... would you hire a sophomore, becoming a junior in the fall of 2017, with A's in all of his coding classes, network security & encryption, entry level programming  in Java, data structures in C++, and intermediate object programming in C sharp. I also know Python and a tad bit of ruby and I'm comfortable working on any OS. I also can pick up new languages quickly and are willing to learn. 

If you want MY opinion as an engineer.

1. I don't care if you failed half your classes or you got all A's everywhere with Honorary Degree. In fact, I MIGHT prefer someone who failed his/her classes, if he/she has many interested personal projects to compensate, especially if I find them of impressive quality when I'll try them. UNLESS, I am looking for a researcher, where I seek someone with deep understanding of theory, and ready to do academic style research for seeking new software technologies/algorithms to do things. THAT SAID: When I say "I don't care if you failed half your classes", I might ask you questions related to important topics that I see that you have done the class (and passed), to see if you end up getting it. And if you got A's everywhere, I'll ask you, still, questions (no free pass), because it is easy to find past exams, learn by heart the answers, and arrive at the exam and do it, and get an A.
    
2. I want to see your passion, "fire in your eyes", when I read your resume and when I see you at the interview. Thinking outside the box is also a bonus (unique project, or unique approach). I also need to see some relation to where you apply: For example: You want to develop a game if you apply at a game company.
    
3. If I was doing an interview, I will asked programming questions to do on the white board. I'll start with a stupid question (this is more for you to relax, and get used to the white board code writing), then ask you a question to evaluate that you don't B.S on your resume. Example, you say: "I know C#", well I want to see if you really do. Or if you say: "I am an expert in C++", so I'll ask you expert level C++ questions. Then I'll ask a common, 'everyday problem' we/most people face and/or algorithmic related question. As a Junior or bellow, I don't expect you to get the algorithm question right, or close to right, but i want to see how you think. I'll be seeking: What ideas do you bring on the table? Are you pushing the envelop or you just interested in getting a solution, write it down and call it a day? and Are you asking the right questions to solve the problem? For this algorithmic question, I would not ask a specific language (already done with the previous question), I'll say: pick your language or use pseudo code (assuming there is coding involved). As mentioned, the purpose of this algorithmic question is to see your thought process. You may be asked questions on your implementation to see if you really know the solution, or it just happened you learned it by heart before by your luck.
    
4. I'll evaluate you on your questions, when I'll ask: "if you have any questions for me".

Note: The above applies today. My interview process changes over time for various reasons (for example: discovered that not the right questions asks, which results in a poor candidate selection, new interview processes discovered, company policies, time for the interview, resume of candidate, etc.) Also, it depends on where I work. For example, if I worked in a company that likes to train its new employees with its own system, where you actually do classes and have an exam at a later date before actually starting, then what I mentioned above will definitely change. I'll be seeking you candidate with good grades. And things like that/

 

Note 2: I am talking about Canada. In the US, for example, they has different laws which prohibits asking certain interview questions, so the format will/may be different.

 

Note 3: This is ME, MY opinion. Every company and every engineer will have its own format to do things, and its own way to evaluate candidates.