Austin Coding Academy
February 21, 2019
Share this blog:

If you’re just starting out on your path as a developer without much or any experience to show off in your portfolio, the road ahead may seem daunting. Your portfolio is more than a showcase of projects and work samples. Your portfolio is your digital space that invites hiring managers to learn more about you and how you would be a great fit in their company and culture.

So what makes a great developer portfolio? What are hiring managers looking for when they review one? Let’s take a closer look at the important elements that make up a solid developer portfolio that will land you an interview.

Get started now

Your developer portfolio is an ongoing, evolving project. Don’t wait until you start sending out your resume to start developing your portfolio. Get started as soon as possible so you’re not rushing to get something together before a recruiter takes a look. If you’re still taking classes, add projects to your portfolio as you complete them. Then, continue to update and improve your portfolio with every project you work on or goal you meet.

Show your skills

This is the cornerstone of your portfolio. Not every hiring manager is the same. Some may look at your resume first before moving to your portfolio. Others may want to follow a link to your hosted projects or your Github repository of projects. It’s important that you keep up with each of these elements, so no matter the method of the hiring manager, you’re prepared to show off your work, skills, and technological capabilities and how you solve problems.

Don’t spend too much time trying to build the next great app that does a new thing or solves a different problem but ends up being poorly ‘spec’ed out. You may end up burdened by the amount of decisions and get stalled in your project. Your portfolio doesn’t need to be limited to work someone else commissioned or paid you to do. Find a project or app to clone and show a hiring manager how you would solve the problems with that app to make it better.

Kevin Colten, Chief Technology Officer and Lead Instructor at Austin Coding Academy, says he looks for “a strict following of coding conventions that can span different coding languages, especially if I’m considering hiring them in a language that isn’t their preferred language.”

Depending on the type of role and breadth of technologies used, hiring managers often look for the following skills:


  • Different DOM manipulation technologies (Document API, jQuery)
  • JSON and AJAX requests (current with libraries and frameworks with a willingness to continue learning.)
  • HTML5 and basic understanding of accessibility
  • CSS feature support and organization


  • Model-View-Controller architecture
  • Basic SQL and NoSQL
  • RESTful API

While education and experience is important, don’t forget to show off any ways you’ve been self-taught too. Include any repositories built from tutorials, a developer blog, or completed massive open online courses (MOOC).

Tell a story

The idea of ‘telling a story’ has become ubiquitous in fields like design and branding. We hear it so often it’s nearly lost its meaning. Yet, there is some fundamental importance to telling a story—it’s something we as humans connect with at our core. Displaying your skills and abilities through storytelling is the best way to make that connection and display your value. Every story has the same basic elements: characters and conflict. Your portfolio tells the story about you, the character, and your journey to overcome certain challenges through your work.

“Don’t include sketches and ideation just for the purpose of including artifacts — make sure that they support the story in some way, and demonstrate your creativity in solving the problem,” says Gord Davidson, Senior Design and Studio Manager at IBM Studios Toronto. Davidson has many years of experience working with and hiring designers. He believes every portfolio should follow this storytelling theme—each in its own way, of course.

Design for the hiring manager

Examine your portfolio from the hiring manager’s perspective. They are sorting through dozens of portfolios in a sitting—what will make yours stand out? Do you create a cohesive, memorable experience for the hiring manager, from your cover letter to resume to portfolio? Do you answer questions the hiring manager is asking?

Before you adding something to your portfolio, ask, “Does this contribute to the story I’m telling about my work skills and experience?” If the information you’re adding doesn’t highlight your work, skills, and who you are as an employee, leave it out. Don’t do have the worst portfolio ever. Be sure your portfolio does address these questions:

  • What problem did you solve?
  • How did you get to the final product?
  • Which tools did you use to get there?
  • What challenges did you overcome to reach this?
  • What purpose did this serve for the client?

Try to answer these questions in your portfolio in a concise manner. Keep the projects you display relevant to the role you’re applying. It needs to be memorable, but it also needs to be something they actually look at. You can always have more project examples or case studies available during the interview.

Don’t wait to get paid

If you’re a new developer, you’re probably wondering: how do I show off my experience when I haven’t had a job yet? Remember, no one has to pay you to do a job for it to go in your portfolio. Show off your own work you’ve done for fun, do some pro bono work for a local organization, or show off your skills by ‘cloning’ an existing project. You don’t have to reinvent the wheel and come up with your own startup idea. Try redesigning a major brand’s website as if they hired you. Rebuild an existing app, but make it better by showing how you would solve some specific problem areas in the app and make the program flow better. Don’t be afraid to experiment! This shows hiring managers you can identify and solve problems creatively even without a project brief.

At ACA, we build a project every day of class, and some bigger projects may take several sessions. From there, students can show off their work online or continue building on a project. We also provide our students with updates about freelance and volunteer opportunities to work on projects to help build out their portfolios.

Apply early and often

Often, the biggest hurdle in landing that first job is not the portfolio, experience, or interview skills—it’s the lack of applications job seekers submit. They also tend to delay too long before submitting those applications.

“We cannot stress enough that it’s the sheer number of applications [students] submit to different companies that will get them hired. It should not be uncommon to have 50+ applications out at a time because it surely isn’t uncommon to only hear back from five percent,” says Kevin. “It sounds stressful, but most anxiety experienced by students is the rush they feel to have their portfolio perfect when they should be more concerned with getting those first interviews, knowing that they may even bomb the first few.”

In the tech industry, the interviewing process can take several weeks for one company. You may not hear back from many companies for a while or at all. The more you jobs you apply for, and the earlier you start the process, the better your chances of getting that interview, and ultimately, the job.