Use this template
Add your own experience and make this layout yours.
dev-engineering
Entry Level Game Developer
Resume Example
4.5 / 5
Why This Template Works
This resume format works well for an Entry Level Game Developer because it is tailored to highlight relevant skills such as Unity and C#. The use of specific keywords like 'mobile game design' and 'pixel quest', a project mentioned in the summary, helps attract attention from both ATS systems and recruiters. Additionally, including social media links like LinkedIn and GitHub provides additional context about the candidate's professional presence and ongoing projects, which are crucial for an entry-level developer.
Instant Resume Score
Check Your Entry Level Game Developer Resume Score
Upload your resume for an instant ATS score and practical, role-specific improvements.
- No Signup Required
- Private by Default
- Usually under 30 sec
Your resume
One step to your resume score
Add your resume to run a free score and get prioritized fixes.
How to Write This Resume
Expert guidelines and best practices for each section of your resume.
01
Contact
Contact
First Name Last Name City, State, Zip Code Phone Number | Email Address LinkedIn Profile URL | Portfolio URL (Optional)
General Guidelines
Your contact information is the first section recruiters see. Keep it concise and professional. Ensure your email address is appropriate (e.g., [email protected]). Include your LinkedIn profile for a comprehensive view of your professional journey. A portfolio or personal website is recommended for creative, technical, or design roles.
Avoid This
Do not include your full physical address (street number/name) for privacy reasons. Avoid including personal details like marital status, age, photo, or social security number unless specifically required in your country. Do NOT use unprofessional email addresses. For artists and designers, do NOT include GitHub links; instead, use ArtStation, Behance, or portfolio sites.
Real Examples
See clear examples of how to format contact details effectively.
Don't
John Doe 1234 Random St, Apt 56 New York, NY 10001 [email protected] github.com/aliciacode Single, 28 years old
Do
Alicia Chen Los Angeles, CA (555) 123-4567 | [email protected] linkedin.com/in/aliciachen | artstation.com/aliciachen
Quick Tips
- Use a professional email address (firstname.lastname format)
- Ensure your voicemail is set up and professional
- Double-check your phone number and email for typos
- Make your LinkedIn URL custom (linkedin.com/in/yourname)
- Use ArtStation or Behance for artist/designer portfolios
02
Summary
Summary
Professional Title Result-oriented [Role Name] with [Number] years of experience in [Key Skills/Industries]. Proven track record of [Major Achievement]. Skilled in [Key Technologies/Skills]. Committed to delivering [Specific Value] for [Target Industry/Company type].
General Guidelines
A professional summary is your elevator pitch. It should be 3-5 sentences long, summarizing your experience, key skills, and major achievements. Tailor it to the job description by using relevant keywords. Focus on what makes you unique and the value you bring to potential employers.
Avoid This
Avoid generic objectives like 'Looking for a challenging role to grow my skills.' Recruiters want to know what value you bring to them, not what you want from them. Don't use first-person pronouns (I, me, my). Keep it concise and impactful.
Real Examples
Compare a weak objective with a strong professional summary.
Don't
Objective: I am a hard-working individual looking for an Entry Level Game Developer position where I can learn new things and advance my career.
Do
Entry level game developer with hands-on Unity and C# experience from mobile game prototypes, coursework, and portfolio projects. Builds side-scrolling mechanics, UI flows, and basic multiplayer features with attention to playability, performance, and clear documentation. Comfortable using GitHub, Photon Networking, and playtest feedback to iterate on small game systems.
Quick Tips
- Lead with the engine, language, and type of game work you can show.
- Use project evidence instead of broad claims about passion or creativity.
- Mention portfolio, GitHub, or demo links when they help reviewers inspect your work.
- Keep the summary focused on junior-level strengths: prototypes, coursework, iteration, and collaboration.
03
Skills
Skills
Technical Skills - Languages: [List] - Frameworks: [List] - Tools: [List] Soft Skills - [Skill 1], [Skill 2], [Skill 3]
General Guidelines
Group your skills logically (e.g., Languages, Frameworks, Tools). Focus on hard skills relevant to the job. List skills in order of proficiency or relevance. Soft skills are better demonstrated through bullet points in your experience section rather than a bare list.
Avoid This
Do not list skills you are not comfortable using in an interview. Avoid using progress bars or percentages to rate your skills (e.g., "Java: 80%") as they are subjective and often misinterpreted. Don't include outdated technologies unless specifically required.
Real Examples
Practical example showing do's and don'ts for skills
Don't
Languages: Java, C++, Python (70%), JavaScript
Do
Languages: C#, JavaScript
Don't
Frameworks: Unreal Engine 4.26, Unity 3D (5/10), Phaser.js
Do
Frameworks: Unity, Unreal Engine
Quick Tips
- Group technical skills by engine, language, tooling, and workflow.
- List only tools you can discuss or demonstrate in an interview.
- Prioritize Unity, C#, version control, debugging, and portfolio-relevant tools for junior game roles.
- Use soft skills sparingly unless the resume also shows them through project or team examples.
04
Experience
Experience
Job Title | Company Name | Location Month Year – Month Year - Action Verb + Context + Result (Quantified) - Led [Project] resulting in [Outcome]... - Collaborated with [Team] to implement [Feature]...
General Guidelines
This is the core of your resume. Use reverse-chronological order (most recent first). Start each bullet with a strong action verb. Focus on achievements and impact, not just duties. Use numbers to quantify your impact (dollars, percentages, time saved, users affected). Show progression and increasing responsibility.
Avoid This
Avoid passive language like 'Responsible for...' or 'Tasked with...'. Don't list every single daily task; focus on significant contributions and measurable outcomes. Avoid jargon that recruiters outside your field won't understand.
Real Examples
Practical example showing do's and don'ts for experiences
Don't
Responsible for creating game assets using Adobe Photoshop.
Do
Created over 50 vector assets, reducing outsourcing costs by 15%.
Don't
Worked on Photon Networking and implemented real-time multiplayer features.
Do
Integrated Photon Networking into the game engine, enabling real-time multiplayer for up to 50 concurrent users.
Quick Tips
- Use strong action verbs like 'Created', 'Implemented', 'Optimized', or 'Led' to start each bullet point. This makes your experience stand out.
- Quantify your achievements where possible with specific numbers, percentages, or impact metrics. For example: 'Reduced compile times by 40%' instead of just stating an improvement was made.
- Focus on the outcomes of your work rather than just describing the tasks you completed. Emphasize how your contributions impacted user experience, game performance, or project timelines.
- Show progression in responsibilities over time by highlighting more complex and impactful projects as you move down the list.
05
Education
Education
Degree Name | University Name | Location Month Year – Month Year - Relevant Coursework: [Course 1], [Course 2] - Honors/Awards: [Award Name] - GPA: X.X (if above 3.5)
General Guidelines
List your highest degree first. If you have significant work experience, keep the education section brief. Include your GPA only if it is above 3.5 or if you are a recent graduate. Highlight relevant coursework, academic projects, honors, or leadership roles.
Avoid This
Do not include high school details if you have a college degree. Avoid listing every single course you took; select only the most relevant ones. Don't include graduation dates from decades ago if age discrimination is a concern in your field.
Real Examples
Practical example showing do's and don'ts for educations
Don't
Bachelor of Science | Any University Name | Any Location September 2018 – May 2022 - Relevant Coursework: Introduction to Programming, English Composition I, Calculus I, etc. - Honors/Awards: None Listed
Do
Bachelor of Science in Computer Science with a Minor in Game Design | San Francisco State University | San Francisco, CA September 2018 – May 2022 - Relevant Coursework: Mobile App Development, Data Structures and Algorithms, User Experience Design
Quick Tips
- List the most relevant degree that aligns with your career goals.
- Include only pertinent coursework directly related to game development or mobile app design.
- Avoid mentioning honors or awards unless they are significant and add value to your application.
- Omit graduation dates from long ago if age could be a concern in your job market.
06
Projects
Projects
Project Name | Technologies Used - Briefly describe what you built and its purpose - Highlight a specific technical challenge you solved - Link to GitHub or live demo if available
General Guidelines
Projects are excellent for demonstrating practical skills, especially if you lack work experience or are changing careers. Include a link to the GitHub repo or live demo if possible. Focus on projects that show problem-solving skills and relevant technologies for the target role.
Avoid This
Don't include trivial tutorials unless you significantly expanded on them. Avoid projects that are outdated, incomplete, or irrelevant to the role you're applying for. Don't just list technologies—explain what you built and why it matters.
Real Examples
Practical example showing do's and don'ts for projects
Don't
Created a simple calculator app as my first Unity project using C#. This was the initial step in learning basic programming concepts. I followed online tutorials to build this.
Do
Built a Unity side-scrolling prototype with responsive jump controls, collectible logic, and documented scene transitions. Added a GitHub README explaining setup, current features, and planned improvements.
Quick Tips
- Prioritize playable or well-documented projects over tutorial-only exercises.
- Explain the mechanic, system, or technical problem you solved in each project.
- Include GitHub or demo links when the repository is organized and review-ready.
- Show iteration by mentioning playtesting, bug fixes, performance work, or design changes.
Frequently Asked Questions
Common questions about this role and how to best present it on your resume.
Include relevant engines, programming languages, portfolio projects, GitHub links, game jams, coursework, and any shipped or playable prototypes. Focus each bullet on what you built, the tools you used, and the gameplay or technical problem you solved.
Use projects as evidence. Describe mechanics, systems, tools, testing, and iteration instead of saying you are passionate or hardworking. A clear portfolio section can make a junior resume credible even without full-time studio experience.
Yes, if they are playable, documented, or technically relevant. Choose projects that show coding ability, design judgment, collaboration, version control, or an understanding of player experience.
GitHub is useful when repositories are organized and show readable code, commit history, and project documentation. Pair it with a portfolio or demo link when visuals and gameplay matter.
Stand Out to Recruiters & Land Your Dream Job
Join thousands who transformed their careers with AI-powered resumes that pass ATS and impress hiring managers.
Double Your Interview Callbacks
Candidates who tailor their resumes to the job description get 2.5x more interviews. Use our AI to auto-tailor your CV for every single application instantly.