Game Design Portfolios: Why Keeping Old Levels and Maps Matters (Lessons from Arc Raiders)

Keep old maps — and the stories behind them. That’s how you win attention from studios hiring in 2026.

If you’re a game design student or early-career designer wondering what to include in your game design portfolio, you’re not alone: employers in 2026 want evidence of iteration, tooling fluency, and live-service awareness — not just a glossy final map. When Embark Studios announced multiple new maps for Arc Raiders in 2026, fans cheered for fresh content. But many players and designers pushed back with the same instinct you should adopt for your portfolio: don’t discard legacy maps. The way a level grows over time tells a hiring manager way more than a single static screenshot.

Why this matters for job-seeking designers

Your core pain points are clear: competition for game dev jobs is stiff, responses after applying are scarce, and interviewers ask for concrete proof of problem-solving. Showing evolution — not just polished endpoints — solves all three. It communicates that you can plan, execute, learn from data, and ship updates: the day-to-day reality of commercial studios, especially for live-service titles like Arc Raiders.

Embark’s 2026 roadmap highlights both smaller experimental maps and larger grand arenas — a reminder that design is iterative and scale is a spectrum, not a single milestone.

The core argument: evolution is an asset

Here’s the thesis: a portfolio that includes initial drafts, mid-iteration adjustments, and final versions demonstrates the designer’s process. It tells hiring teams you can handle constraints, prioritize features, and respond to playtest and telemetry. In short, you’re showing the same skills studios want when they expand a live game’s map pool, like Embark did.

What employers are actually looking for in 2026

• Iterative thinking: Evidence you can pivot based on feedback and data.
• Technical fluency: Clear notes about engines (Unity/Unreal), version control, and asset pipelines.
• Collaboration: Artifacts showing cross-discipline work with level artists, scripters, and UX designers.
• Live-service awareness: How you design for updates, modularity, and retention metrics.

Lessons from the Arc Raiders map update story

In interviews and press coverage around late 2025 and early 2026, Embark’s design lead discussed a deliberate approach: maps across a size spectrum, from compact arenas to grand landscapes. The community’s response — nostalgia for current maps and worry they might be removed — highlights one simple truth for students: legacy design has community and learning value. A studio that keeps old maps gains player trust and a knowledge base for future design. You should do the same in your portfolio.

Concrete takeaways from Arc Raiders

• Keep small and large scales: Show you can design both tight encounters and sprawling navigation challenges.
• Document changes: Side-by-side compare “before” and “after” to show rationale and measurable outcomes.
• Highlight player familiarity: If players gravitate to certain routes or tactics, that’s data — capture and explain it.

How to structure legacy maps inside your game design portfolio

Don’t just upload files. Build a narrative around each map you keep. Below is a practical structure you can reuse for every level or map entry.

1. Title card: Name, engine, build date, your role, team size.
2. Context: Project brief — goals, target audience, constraints (time, polycount, players per match).
3. Evolution reel: Short video (60–90s) showing a timeline from concept sketch to final playtest. GIFs are OK for quick scanning.
4. Before/After gallery: Annotated screenshots showing major changes with one-line reasons (e.g., “opened sightlines to reduce camping”).
5. Assets & docs: Link to an assets list (prefab inventory, LOD usage), design docs, and the level’s README or changelog.
6. Metrics & playtest notes: Heatmaps, average traversal times, retention, or simple playtest quotes.
7. Lessons learned: One-paragraph reflection that ties your decisions to outcomes — what you’d change now and why.

Example folder and naming convention (practical)

Use a predictable structure so technical recruiters and leads can scan quickly.

• MyPortfolio/ArcRaidersLike_MapA/
  • README.md
  • assets_list.csv
  • mapA_v1_2023.unitypackage
  • mapA_v2_2024.unitypackage
  • mapA_final_2025.webm
  • playtest_heatmap_v2.png
  • cover_letter_snippet.txt

What to emphasize in your resume and cover letter

When applying for game dev jobs, recruiters skim. Your resume must surface the evolution narrative in one or two lines; your cover letter should frame it for the role.

Resume bullet examples

• Designed and iterated 4 multiplayer maps (Unity) for a 12-person prototype; reduced average match imbalance by 18% via sightline/spawn adjustments.
• Managed map asset pipeline: created 150+ prefabs, implemented LODs, and cut map load times by 22%.
• Produced playtest reports and heatmaps leading to two A/B changes that increased retention across map rotations.

Cover letter snippet (practical)

“At University X I kept every iteration of my arena maps to document trade-offs. When live playtests showed player bottlenecks, I used heatmaps and a rapid prototyping cycle to reduce choke point dwell time by 30%. I’d bring that same data-led iteration to map development at Studio Y.”

Demo reel and interview prep: show the process, not just the polish

In 2026, recruiters expect short reels (2–3 minutes) that tell a story. A two-minute reel that highlights a single map’s lifecycle beats a five-minute montage of finished shots. For interviews, plan to discuss three artifacts: one legacy map, one mid-iteration pivot, and one final ship-ready piece.

Demo reel checklist

• 0:00–0:15 — Quick intro: name, role header (e.g., Level Designer — Unity/Blueprints), 1-line project context.
• 0:15–0:50 — Evolution montage: rough sketch → greybox → textured → playtest pass.
• 0:50–1:30 — Metrics overlay: heatmaps, retention changes, or a before/after gameplay clip with callouts.
• 1:30–2:00 — Short reflection and tools list (Git, Perforce, Jira, Houdini, Blender).

Interview prep — scripts and stories

Prepare to answer behavioural and technical questions with artifacts. Use the STAR method (Situation, Task, Action, Result) and reference your portfolio entries.

• Situation: “Map X had a camping problem and long queue times on rotation nights.”
• Task: “We needed to reduce camping and balance player flow within three sprints.”
• Action: “I created a greybox variant, added a mid-route objective to split traffic, and adjusted spawn logic.”
• Result: “Average match churn dropped 12%; playtest heatmaps showed more evenly distributed engagement.”

Technical tips: how to keep old maps usable and presentable

Old maps can break in new engine versions. Here’s how to preserve them so they remain valuable portfolio pieces.

• Version snapshots: Export builds and editor packages for the engine version used. Save a WebGL/standalone playtest build where possible.
• Lightweight media: Record short timelapses of edits and export 30–60s compressed videos linked from your portfolio site.
• Readable docs: Maintain a short README with the engine version, dependencies, and a changelog of decisions.
• Annotated source: Include small snippets of scripts or Blueprint screenshots with comments to show how events were triggered.
• Package assets: Export prefab lists and textures separately so reviewers can see scope without loading huge scenes.

Showcasing assets and documentation — what recruiters want to click

Recruiters won’t launch every build. Give them a fast path to assess your work.

• One-page case study: Top-line bullets, one key metric, and a link to the reel.
• Assets index: A clear CSV or table listing prefabs, textures, and scripts with file sizes.
• Quick demos: 30-second clips that show a major change (e.g., “Added connector corridor to solve camping”).
• Playtest log: Raw notes and a summary of action items from the last 3 playtests — demonstrates responsiveness.

Advanced strategies: leverage live-service trends in 2026

Late 2025 and early 2026 saw a surge in studios prioritizing modularity and telemetry-driven map updates. Use that trend in your favor.

• Modular map sections: Show how a single modular piece was reused across three maps to speed iteration.
• Telemetry snapshots: Even basic session timing or engagement charts (can be from small playtests) demonstrate data literacy.
• Feature flags: Document a toggled change (A/B) and the measurable effect it had on player flow.

Turning legacy maps into interview gold

Legacy maps are conversation starters. Use them to tell stories about constraints, team communication, and prioritization. When asked “show me something you’re proud of,” a well-documented legacy map allows you to speak to depth rather than polish.

Sample interview prompt and optimal response

Interviewer: “Tell me about a time you had to undo a major change.”

Optimal response: “On Map B we widened a corridor to improve throughput, but playtests showed it increased camping. My documentation captured both the intention and the failure. We reverted the width, added vertical cover, and introduced a flow objective. Not only did we get better metrics, but preserving the earlier version helped the team understand why the change failed and informed future design choices.”

Final checklist: what to keep from every map

• Concept sketches and greybox images
• Versioned builds (v1, v2, final) and a README
• Annotated before/after screenshots
• Short evolution video (60–90s)
• Assets list and provenance (who made what)
• Playtest notes and simple metrics
• One-paragraph reflection and one lesson learned

Parting advice — be the designer who preserves memory

Studios like Embark are expanding map offerings in 2026, but the community value of older maps remains. For hiring teams, that same value applies to your portfolio: the preserved history of your work is proof you can iterate, learn, and ship. Treat legacy maps as a strategic asset — not clutter to discard.

Actionable next steps: Pick one old map this week, build a 60-second evolution reel, write a one-page case study, and add a single metric or playtest quote. Put that entry at the top of your portfolio for your next application.

Call to action

Ready to turn your legacy maps into interview-winning artifacts? Upload one map entry now, follow our portfolio checklist, and get a free resume bullet template tailored to level designers at jobvacancy.online. Preserve the past, and show studios you’re ready to design the future.

Related Reading

• Keep Takeout Toasty: Hot-Pack Strategies vs. Hot-Water Bottle Hacks
• Marketing + Ops Playbook: Combine CRM Insights with Ad Budgets to Boost Enrollment
• Ingredient Spotlight: What Fragrance and Flavor Science Means for Sensitive Scalp Formulations
• Digital PR + Social Search Keyword Pack: Terms That Build Authority Before Search
• How Sensory Tech Could Create Low-Sugar Cereals That Still Taste Indulgent