GDDI Guide to Build an Industry Ready Portfolio
This guide was created by the Duke University’s Master of Engineering in Game Design, Development, & Innovation program. These are recommendations based on industry research, however, there is no limitation on how you would like to structure your content.
Creating a portfolio
Recommended structure of contents
- Hero image or video reel to showcase exciting, best work and draw viewer in
- Clear name/branding – Statement of your purpose directed toward your viewer.
- Tagline summarizing skills and experience. Keep it short.
- 8-10 curated projects showcasing range and progression of applied skills.
- Embed images, videos, prototypes to showcase functionality without leaving site.
- Summary “what I did” snapshot including timelines, tools, responsibilities, team size, etc.
- Provide context connecting projects to career goals in the gaming industry.
- Include interpretable code snippets, playable builds, documentation etc. that provides behind-the-scenes evidence of competencies.
- Visual icons representing key competencies with proficiency levels.
- Toggle between technical, creative, and soft skills.
- Connect skills to contributions in upcoming project section.
- Brief background and what sparked your interest in game design.
- Discuss impact of highlighted projects on your development in this trajectory
- Evidence of leadership, problem-solving, passion for gaming industry
- Hobbies/interests showcasing creativity outside of academics/work.
- Links to professional social media and resume
- Email address and contact form.
What to do when creating your portfolio
- Clear and Concise Introduction: Include a brief and clear introduction on the landing page to provide an immediate sense of the individual’s identity and skills.
- Professional Project Presentation: Organize major components such as menu headings, professional projects, and personal projects effectively.
- Simplicity and Digestibility: Keep the design simple and easily digestible, especially for senior roles. Avoid overwhelming content.
- Visual Appeal: Prioritize visually appealing designs that are easy to navigate, providing a positive user experience.
- Project Details: Clearly outline project details, including roles, team size, platforms, tools, and timelines.
- Tagging and Categorization: Use tags and categories under projects for easy navigation and understanding of different facets of contributions.
- Reflection and Context: Include reflections or metacognition on learning experiences, specifying individual contributions to projects.
- Engaging Elements: Use engaging elements such as cinematic intros, video previews, and GIFs to showcase skills and projects dynamically.
- Responsive Design: Ensure the portfolio is visually appealing and responsive, catering to a diverse audience.
- Contextual Information: Provide context on the developer’s specific contributions to the team for a deeper understanding of their role in projects.
- Snapshot Information: Include snapshot information about each project on the homepage for quick insights.
- Resume and Contact Information: Include links to the resume, contact information, and social media at the end of the portfolio.
- Skill Showcase: Use skill sections to highlight technical and soft skills important to the industry.
What NOT to do when creating your portfolio
- Avoid Separate Platforms: Avoid using external platforms for posting content. Instead, opt for a separate, comprehensive site to tell your story.
- Minimize Redundancy: Clean up redundant menu text and portfolio tiles for a more streamlined appearance.
- Overwhelming Detail on Main Page: Avoid overwhelming detail on the main page; prioritize showcasing projects rather than extensive information about the developer.
- Incomplete Project Information: Project pages should not lack depth; provide sufficient information on each project, including skills developed and the design process.
- Inaccessible Navigation: Ensure ease of navigation; portfolios should not be difficult to navigate, especially for UI/UX portfolios.
- Limited Depth on Projects: Avoid having projects with insufficient information; provide details on specific contributions, skills used, and the learning process.
- Broken Links: Ensure all links are functional, and there are no broken links within the portfolio.
- Lack of Security: Ensure the website is secure, avoiding potential accessibility issues.
- Confusing Visual Elements: Steer clear of visually confusing elements, such as skills sections that may distract from the overall presentation.
- Insufficient Project Descriptions: Avoid brief project descriptions; provide enough information for recruiters to understand the significance of each project.
Portfolio examples (with critique)
- Positive: Clear “what I did” summaries, platform/team size context. Easy navigation. Showcases range of technical and design skills.
- Improve: Visual aesthetics need styling/polish. Streamline menus (redundant text). About Me on first page distracts from projects.
- Positive: Visually appealing and creative. Simple navigation to projects.
- Improve: Needs more depth on projects. Lacks specifics on contributions/learning. Clarity on skills developed needed.
- Positive: Snapshot project info on homepage. Tags to categorize projects.
- Improve: Project pages lack detail. Trailers instead of comprehensive details. Personal projects too brief.
- Positive: Responsibilities section clearly outlines role. Showcases progression/range.
- Improve: Only a couple recent projects. Template bio page is bland. Links menus need streamlining.
- Positive: Commercial and demo projects split. Good display of awards.
- Improve: More polished, modern aesthetics needed. Responsive design issues on mobile. Scope context lacking.
guide provided by Duke University’s Master of Engineering in Game Design, Development, & Innovation program
