Viewing entries in
Career Services

GitHub vs. Resume – Which is Better for Aspiring Programmers?

GitHub vs. Resume – Which is Better for Aspiring Programmers?

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge that helps set our students apart. Over the next few weeks, we’ll share our best tips and tricks for junior developers looking for their first jobs.

Searching for full-time job opportunities can be a tedious process for aspiring programmers. The pressure of preparing for interviews isn’t lessened by the many ways to present your professional and academic profile to recruiters. While a solid education in coding helps in finding a programmer job you love, it is also important to use the right tools to showcase your skills and experience.

Over the last few years GitHub – the version control system and code hosting service – has been gaining popularity as a tool to bolster programmers' portfolios.

The question we'll look at in this post is: GitHub vs. resume, which one is better?


Employers and recruiters are increasingly looking toward GitHub to gain an understanding of a potential hire's technical skills. Some consider GitHub a better alternative to the standard resume for several reasons:

  1. GitHub offers the space and freedom to share code while also functioning as a social network. Your projects are rated and can be ranked based on popularity.
  2. GitHub tracks activity. Employers can see how often you're coding, and what code you're pushing.
  3. Some consider resumes to be an old and outdated component of professional portfolios. Since employers and recruiters tend to spend only seconds evaluating a candidate’s resume, there’s a focus on being as brief as possible. This means there isn’t enough space to successfully detail your accomplishments.

Despite its many advantages, using GitHub in place of a resume has also received criticism. Like any new trend in the industry, this has been widely debated among programmers and recruiters.

The primary argument against replacing your resume with GitHub is that GitHub simply doesn't convey your academic and employment experience as effectively as a resume. It's possible to pin specific repositories you want employers to see to the top of your profile; however, there isn’t a dedicated area to convey achievements that may be non-coding related. It is possible to view a programmer’s GitHub profile and gain an insight into his or her projects and skill level, but not much more.

When it comes to building a professional and personal portfolio, the best practice for aspiring developers is to use all tools in the best possible manner. If you can’t decide between GitHub and a standard resume, why not use both? Most employers today ask to see both your GitHub profile and resume. This is also what we recommend to our own students and alumni. Make sure your resume is polished and that it provides a quick peek at your professional and academic accomplishments while ensuring you’re constantly engaged in interesting projects on GitHub.


At Epicodus, we’re focused on ensuring that our programming students derive the greatest value from their education and are able to obtain a programming job or internship of their choice. While you’re here, check out our Career Services to learn more about how you can benefit from an education at Epicodus!

Finding a Junior Dev Job: Negotiating Your Salary

Finding a Junior Dev Job: Negotiating Your Salary

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. Over the past few weeks, we’ve shared our best tips and tricks for junior developers who are looking for their first jobs. You can find all of the posts in this series here.

So you made it through your interview, and your prospective employer has brought up what your salary will be. Congratulations! Negotiating a salary can be a bit terrifying, though, so here are some tips to help you out.

Do your research in the city where you'll be working. Different cities can have drastically different average starting salaries for junior devs. Learn the salary range for the city you're in, and weigh where you think you would fall in that spectrum. If your technical skills are on the weaker side, you're interviewing for a job with tools or languages you haven't used before, and/or you don't have much professional experience, you'll probably make on the lower end of the spectrum; if you are very strong technically and have at least a few years of professional experience, you'll probably make on the higher end.  Use the numbers as a starting point, and even share them with prospective employers when appropriate.

In the long run, though, your first salary really isn't that important. Within a year or two of working as a developer, you'll almost certainly make at least $20k more than wherever you start. The most important thing is to get a job, and if you have options, to take a job where you're more excited about the work you'll be doing.

Though your first salary might not be that important,  it's worth your time to learn how to get a higher offer. In negotiation, you need to know who has more to lose. If you're charming and technically very strong, you have little to lose - you can walk away and probably get another offer somewhere else. If your interview skills aren't great and your technical skills are weaker, the employer has the upper hand.

When the employer has the upper hand, try to get more information from them. If they ask you for your desired salary, tell them "I haven't worked in this field before, so I'm not completely sure what to expect. What have you paid people in this position before?" Work that angle hard before putting any numbers out of your own. Then, feel free to share the salary ranges above.

If you have the upper hand, you might consider opening with a high salary requirement to set the expectation high. For example, you might say "I made $65k in my last job, so I'm looking for something in that range," and expect to settle somewhere around $60k. If you let them open the negotiation with an offer of $50k, you might have a hard time getting it above $55k. But make sure your expectations are realistic - you are coming in as an entry-level developer, and you will likely be an investment for anybody who hires you. If you have a lot of career experience, you very well may start out making less until you get at least a few months of experience working.

Finding a Junior Dev Job: Decoding the Technical Interview

Finding a Junior Dev Job: Decoding the Technical Interview

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

A technical interview, or technical portion of an interview, will focus on your coding knowledge and problem solving skills. The purpose is to get an idea of how you think, and what strengths you can bring to their company.

A technical interview is, for many, the most stressful part of the job-hunting process. Coding is hard enough on your own or with a pair, but now you're going to be asked to solve coding and pseudo-coding problems in front of potential employers. The key is to practice before the real thing, so you're not too nervous when you're in the real thing.

Job interviews can take many formats. Some employers will conduct a pairing interview, where you'll pair program with your interviewer. Sometimes this will be on a standard problem the employer uses to evaluate candidates; sometimes it will be on real work that the employer has; and occasionally they may ask you to pair on one of your own projects. This is an excellent interview format, as it tests what you'll actually be doing on the job, and doesn't really require any special prep. Unfortunately, only a minority of employers use this format.

Another common format is to send you requirements for a simple program, ask you to solve it on your own time without outside help, and send them back a solution. This could be a full-blown web app or just a simple server-side or JavaScript program. A variation on this format is to ask you to come into their office and build the app on your own, within a couple hours. Again, this format is fairly nice because it tests the way you work, and doesn't really require a whole lot of special preparation.

Whiteboard Questions

The more difficult interviews will involve answering technical questions out loud, or "whiteboarding" a solution to a coding problem - sketching out a visual and/or pseudo-code solution to a problem, and talking out loud about your thought process as you go. This is one of the most common interview formats, and where you should spend a good amount of extra time preparing.

There are three things you should make sure to do when you get an in-person technical question:

  1. Ask clarifying questions. Often, your interviewer will intentionally be vague about something or leave out information. Don't be shy about asking for clarification or more information!
  2. Talk out loud. Even when you have no idea where to go, don't just stand there silently. The interviewer wants to hear your thought process, even if it's just you coming up with ideas and then saying why they won't work or are wrong. You should strive to talk constantly.
  3. Admit when you don’t know something. When you don't know something, it will be obvious to the interviewer. If you try to "BS" your way through a question, you will most likely not get the answer, or the job. Just say "I don't know," or if applicable, "I don't know, but here's how I might figure it out."

An excellent practice method for this type of question is to find a resource for code challenge questions, and practice talking out loud while you solve the problem. You can do this while writing the answer on a sheet of paper, or even with a dry-erase marker on the bathroom mirror. The main practice point is to write the code by hand, and explain what you're doing while you're doing it. You can find some great sample challenges to work on from CoderByte

Open Questions

Another type of question you get in a technical interview may not require you to code at all. These questions may come in addition to a code question, and are open ended discussion questions designed to give you a chance to showcase your knowledge. It's important to take advantage of these opportunities, as you have the freedom to highlight your strongest area of knowledge.

Here are some sample interview questions:

  • Name every database association relationship.
  • What is the difference between POST request and a GET request?
  • What is Git and why would you use it?
  • What happens when a user logs into a website?
  • What is a class?
  • What is an object?
  • What is unit testing?
  • What happens when a user types in a URL?
  • What is a foreign key?
  • What is REST?
  • Pretend I’m another programmer who has never used Drupal/.NET/Rails– explain to me how an app is structured, and why it’s a good framework for web apps.
  • Show me some code you wrote that you're especially proud of.
  • Talk about a time that you solved a difficult coding problem.
  • What is an array?
  • Explain MVC.
  • What is a join table in SQL?
  • What is floating in CSS?
  • What are media queries and how do you use them?
  • You've been working on a site for a couple months here at our company. You come in one day and the site is down. What do you do?

Final Thoughts

Here is some great advice taken from a presentation on technical interviews:

  • Make sure you understand the question. Do not start until you do! Ask for clarification if you're at all unsure.
  • Use the programming language you're most familiar with. It doesn't matter if the interviewer is unfamiliar with that language. They can probably figure it out. They can consult colleagues after with any questions.
  • Verbalize your thought processes. Don't just stand there and do nothing while you think about the problem. Talk about what you're thinking, discuss the pros and cons. Think out loud!
  • If you don't know something, admit it. The interviewer may give you a hint, or move on to another question.

Finding a Junior Dev Job: Nailing the Non-Technical Interview

Finding a Junior Dev Job: Nailing the Non-Technical Interview

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.


Interviewing skills are an important part of a job search. If you're a student at Epicodus, you'll have the opportunity to participate in a mock interview with a member of our staff, and practice answering some typical questions. The more seriously you take it, the more you can learn as you move forward. There are some basics to consider as you prepare for any interview.

  • Dress appropriately for an interview.
  • Conduct yourself in a professional manner
  • Have relevant and appropriate answers for questions.
  • Have relevant questions for your interviewer.
  • Stay relaxed, and enjoy the opportunity to teach someone about yourself, and learn about a company.


During our mock interviews, we use questions that cover a few areas. These are by no means comprehensive, and some interviews may focus on one area or another, but as a general rule these are present in one form or another in just about every interview. 

Personal Questions

These are "get to know you" questions about yourself, and about your previous education, experience and motivations.

  • Tell me about yourself. What's your background?
  • Why did you get into programming?
  • What made you pick code school?
  • Where do you see yourself in the future?

Your goal should be to explain the ways life has been preparing you to become a developer. General biographical information should be kept to a minimum. If you have prior programming experience you can talk about any coding you did as a kid or in school. If you're newer to coding you can emphasize parts of jobs where you worked with computers or spreadsheets, and tell about any computer skills you developed on your own.

Either way, make sure to emphasize the skills that have served you well as a student and developer, for example problem solving skills, critical thinking, organizational skills and so on. You want to show the interviewer you're passionate by illustrating how these skills have come up in different ways throughout your life.

Programming Questions

These are discussion questions which give you a chance to showcase your knowledge about programming tools and concepts. This is different from a technical question.

  • What problems do you see with current web development tools?
  • What do you like about current web development trends?
  • How do you stay active in the tech community?
  • What are your strategies to approach a problem that is initially beyond your capabilities?
  • What frameworks have you used?
  • What testing tools have you used?

Workplace Questions

The interviewer will want to know about your motivations and experiences in the workplace. These questions are a good chance to highlight your communication, teamwork, and work ethic.

  • What kind of culture do you want in your workplace?
  • What are some of the challenges you faced while pairing?
  • Give an example of how you resolved a disagreement with your pair.
  • How would you communicate with team members that are not developers?
  • Tell me about the intern project you worked on.
  • Why do you want to work here?
  • Why should we hire you?

Be well prepared for these interview questions and know how to answer them. These are generally less about your technical skill set and more about your work ethic and ability to collaborate with others. The general format they’re looking for is called S.T.A.R. It means:

  • Situation: (In my job at x company)
  • Task: (I had to accomplish y thing)
  • Action: (To that end I did z thing)
  • Result: (This is what ended up happening or what I learned)

Open Discussion

Just about every interviewer will close out by asking if you have any questions. You should have at least a couple prepared ahead of time. The most effective ones show an interest in the company and in being a positive addition to it. Questions about the team and culture of the company and where you would fit in are also really good. It's important to have some questions prepared that will help you decide if this is a good fit for you. Make sure to ask about things that haven't been covered in previous conversation.

  • Can you give me an example of a recent challenge or project you've been faced with?
  • What are the priorities for this position evaluated?
  • If I am offered the position, what kinds of opportunities will I have to work with veteran developers?
  • What are the greatest challenges for those in this role?
  • What opportunities will I have to learn new skills/continue my education?

Finding a Junior Dev Job: Researching Companies

Finding a Junior Dev Job: Researching Companies

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

As you apply for jobs, it's important to do proper research on the companies you interview with. These companies are looking for people that will help them solve problems and become more effective in their field. Before we can explain how we will be able to achieve that, we need to have a fairly complete understanding of the company itself.

It's hard to stress enough how important research is. This should really go beyond the technical aspects of the company. The more knowledge and investment you have in them, the more buy-in they’ll have with you. Here are some things you should do before your interview:

  • What do they make/do?
  • Who works there?
  • Find their team page
  • Look them up on LinkedIn
  • Look the developers up on Github
  • Interact with their product and submit feedback if possible
  • Download their app
  • Use their API
  • Browse their client sites
  • Follow the company and employees on Twitter, like the company on Facebook, Instagram, LinkedIn, etc.
  • Glassdoor: Take Glassdoor reviews with a grain of salt. Get an interview with a company and decide for yourself what it will be like to work there.
  • In doing this research ask yourself “why do I want to work here?” as well as “what hesitations might I have about working here?”

Finding a Junior Dev Job: Interviewing Basics

Finding a Junior Dev Job: Interviewing Basics

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

Before you walk into the interview, make a physical or mental list of things you absolutely do not want to leave the interview without them knowing about you. These are not necessarily catch-all things you spout off at every interview. Maybe you did a project that relates to what they’re working on. Maybe you have a lot of enthusiasm for a client they’re working with. As the interview is winding down, make sure you go through that list and that you’ve touched on all those things. Otherwise it can be really easy to walk out of an interview and only realize hours later that there were really important selling points you should have added.

This is not the time to ask about salary, vacation time, or other benefits. If they offer that information you can ask if those things are negotiable, but this is not the time to do the actual negotiating.

Be aware of non verbal cues. It can tell you as much about how an interview is going as what the interviewer is saying. You can usually tell if you’re overstaying your welcome or if an interviewer is receptive to extended conversation by their expression or body language.

Above all else, remember that the employer came to you because they have a problem and they want you to be the solution. They’re investing time in interviewing you because they are in your corner and they want it to be a positive encounter.


Here's a handy checklist that we've created to help you:

  • Dress appropriately for an interview.
  • Conduct yourself in a professional manner.
  • Have an answer for personal questions that highlights your journey to becoming a programmer.
  • Have an answer for programming questions that highlights your knowledge and grasp of programming concepts.
  • Have an answer for workplace questions in the S.T.A.R. format.
  • Have at least one relevant question for your interviewer. 
  • Stay relaxed, and enjoy the opportunity to teach someone about yourself, and learn about a company.

Above all: don't undervalue yourself.  Don't offer up your weaknesses or paint yourself negatively. The interviewer should know where you're coming from and can figure out your weaknesses on their own - it's your job to emphasize your strengths.

Finally, don't forget to send a thank-you email after the interview. Read this article about following up after an interview.

Finding a Junior Dev Job: Sprucing Up GitHub

Finding a Junior Dev Job: Sprucing Up GitHub

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

When you apply for a job or internship, employers will want to see code you've written so that they know what you're capable of doing. Spend some time getting your GitHub profile looking good. Make sure every repository has a README file that:

  • Explains what the project does;
  • Explains how to set everything up, if someone clones it;
  • Provides information about the goals of the project. (What you were working on and what you were trying to learn);
  • Provides a link to the live site (GitHub Pages, Heroku, etc) ; and optionally,
  • Includes any known issues with the code, and a roadmap for features you'd like to build
  • Is well-organized with markdown headers.

Go through all files in each repository and make sure that there aren't large sections of commented-out code, bad indentation, extra line breaks, or anything else that looks less than professional.

If you've completed a web development internship, also make sure to fork your internship project, so that you have a copy of it on your profile for employers to see.

You might read these articles on the importance of your GitHub profile to employers.

Finding a Junior Dev Job: Writing a Good Cover Letter

Finding a Junior Dev Job: Writing a Good Cover Letter

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

A good cover letter will show your interest in the company, show that you understand their needs, and give examples of what you've done that demonstrate how you can fit those needs. Every company treats cover letters differently, and you may hear lots of conflicting advice about how to write them. Below, we're going to share what we've found works best for most Epicodus students, for most of the jobs and internships they apply to. This advice is based on the experience of many of Epicodus graduates and conversations with dozens of companies.

Because every company is different, and every job has different needs, every cover letter should be different! Before you even start writing your cover letter, you should research the company enough to answer questions like: "Why do you want to work here?" and "What about our company excites you?"

That said, every cover letter you write for jobs after code school should lay its paragraphs more or less as described below. If you're a strong writer, feel free to take some creative license here; if writing isn't your strong suit, you'll probably want to stick closer to these guidelines. The examples below are adapted from actual Epicodus students.

First paragraph: State the position you are applying for, tell why you are interested in the position and/or the company, and give a quick overview of why you are qualified. For example:

I am writing to apply for the Web Developer Intern position. Culture Foundry excites me on many levels. For example: music advocacy is a subject that is near and dear to me, having been a professional musician for a number of years and experiencing the evolution of the music business first hand. The musician pages displayed on your site are simply stunning! I think that the full-stack development skills I've gained in my recent schooling and internship, and my background first working in technical support, would make me a great fit for your internship position.

Second paragraph: Tell your pre-code school story: how you became interested in development, and the non-technical skills you picked up before school. Make sure these non-technical skills match the non-technical skills the job description requests.

Before starting school at Epicodus to become a web developer, I worked in customer service and ended up at two online music tech companies, back-to-back. I quickly became immersed in troubleshooting user interface issues, and even taught myself a bit of code to help improve the company’s site and client experiences. Besides the obvious need to be an effective communicator, I was regularly challenged to think outside of the box. If someone wrote into support it almost always meant they were struggling with something. While working at Bandcamp, a local non-profit music foundation wrote into support feeling very unsure how to go about using our service as a tool to benefit their cause. I set a time to meet with them in person (as a remote email support personnel, this was unusual), show them the ropes, and even provided the foundation with a charity rate earning them even more proceeds. They thanked me profusely for going above and beyond to help, and I was happy knowing that I left them feeling empowered.

Third paragraph: Talk about your experience at code school, and make sure to match the skills you talk about with the skills listed in the job description.

I enjoyed my customer service work, but I often found myself gazing longingly at the developers, imagining a gratifying and stimulating job solving tough problems and building tools that made a lasting difference. This past April, the path became clear for me to pursue a job in coding, and in July, I enrolled in Epicodus's web development program. After dedicating four months of forty plus hours a week learning numerous programming languages and tools, I consider myself a full-stack developer, and am equally comfortable developing Ruby on Rails backends as working with JavaScript and jQuery in the front-end. But the biggest skill I learned since joining the coding world is how to take a brand new tool or language and have it feel like an old friend. For example, at my recent internship at Company X, their client-side was built with an MVC library I had never seen before, but by the third day of my internship, I was comfortable using it and committing code to production.

Fourth paragraph: Close out with a short summary of why you're a good fit, and thank them for reviewing your application.

Between my breadth of experience in the music realm and newly found fervor for programming, and your company’s passions and aesthetics, I believe I am a perfect fit for your Web Developer Intern position. I know we could benefit each other greatly, if given the opportunity. Thank you for reviewing and considering my application. I'm looking forward to hearing from you!

In talking about your experience, the most important thing is to provide examples. In the above example, the author says she's somebody who thinks outside the box, but it's even better that she gives an example of how she took an unusual support request and took the unusual step of meeting in person. And when talking about her development experience, she says she's a able to pick up new languages and tools quickly, and then goes on to provide an example of committing code within a couple days of learning a new MVC library.

Finding a Junior Dev Job: Optimizing Your LinkedIn Profile

Finding a Junior Dev Job: Optimizing Your LinkedIn Profile

Helping our students find great jobs is a huge part of what we do at Epicodus. In fact, it’s our mission. Over the years, we’ve accrued quite a bit of job-hunting knowledge to help set our students apart. In the next few weeks, we’ll be sharing our best tips and tricks for junior developers who are looking for their first jobs.

If you don't already have an up-to-date, professional-looking resume, start by making a LinkedIn profile, which you can later be used to generate a resume. Many employers will even ask for your LinkedIn profile in lieu of a resume. For most people, we suggest you organize your LinkedIn profile as follows:

  • Include a recent photo.
  • Edit your tagline to something like "Junior web developer", or something similar.
  • Create a friendly URL including your name.
  • Write a short summary of what you're doing now (learning to code) and why you decided to become a developer. Keep it under five sentences.
  • Add a link to your Github profile (and optionally your website) to your summary. The link will show up as a large box, this is OK.
  • Move the Projects section just below your summary. Add some projects that you've completed to this section. Include links to the Github code for the project or a live site on Heroku, Github Pages, or another hosting option, if possible. Talk about what the projects do and what technologies were used.
  • Next, list your previous jobs under Experience, with a short description of what you did at each role. Be specific and succinct - use concrete numbers and examples, like "Responsible for on-boarding and training two dozen new employees in 3 months", rather than vague statements, like "Fulfilled management duties beyond expectations." If you have more than 3 or 4 previous jobs, just include the most recent ones (unless earlier ones are relevant to the jobs you're applying for).
  • Break down past experience descriptions into bullet points. You can easily do this by using the Alt-8 shortcut.
  • If you're an Epicodus student, add Epicodus to your Education section, and move that section directly after your Experience section. Write a brief summary of what you're learning and doing at Epicodus. Don't write about what Epicodus is - write about your experience. For example, one student wrote "I'm currently learning how to build web applications with JavaScript, Ruby/Rails, HTML, and CSS. More importantly, I'm learning how to think more like a programmer, write good code, and pick up new languages and technologies." Another wrote: "At Epicodus I've learned how to learn programming languages more than learning any one language for the sake of itself. I've learned how to work towards a programming goal on my own and with others until success happens. I've also learned how quickly I can process a tremendous amount of information that is new and uncomfortable at first, and have it feel comfortable like a worn pair of jeans by the end of a week!" Don't copy these examples - come up with your own that describes your own unique experience.
  • In the Skills section, list skills you've learned, like HTML, CSS, JavaScript, jQuery, Ruby, SQL, Ruby on Rails, AJAX, Git, TDD, pair programming, and more that are specific to your own course track.

Epicodus Internship Report


After conversations with all of the employers who participated in Epicodus’s internship program, we’ve come up with some suggestions we hope anybody hosting interns will consider:

  • Integrate interns as closely as possible with permanent staff.

  • Before interns start, run through a clean installation of the software they will be working on. Fix any issues and document the process.

  • If interns will be working on an existing product with other developers, start flagging bugs and features appropriate for the interns two or three weeks before they start.

  • Informally check with interns as often as once an hour.

  • Have interns sit side by side so that they can easily help each other out.

  • Designate one or two staff developers who interns can first turn to when they are stuck.

  • Hold weekly one-on-one, process-oriented, non-technical checkins with each intern.

  • Organize a weekly social event, such as lunch, to bring interns, their supervisor(s), and other staff together.

Setting up an internship program takes work, but the participating employers were universally happy with the outcome, whether it was getting work done on an open source project they had never gotten around to, hiring an intern into an employee at the end, or just the joy of working with excited new developers. We hope our findings and suggestions from this report will make it easier for any company to start a successful, rewarding internship program.

Click the link to head to the full report:

Michael Kaiser-Nyman, President
Maureen Dugan, Outreach Coordinator

For more information: