top of page







A non-linear quest and dungeon created for the Buddhist themed souls-like, Samsara. Delve into Amira's ancient temple, only to find her still alive, and terrified of the surrounding monsters. Take multiple interconnecting pathways to rid the monsters and disable statues, which turn out be keeping her alive.
Made for the commercial indie RPG, Samsara, releasing 2026
Included both a training camp/onboarding process, and a freelance contract
Directly enhanced 5+ more levels and the agile process via utilities and admin.
Amira's Plight
Responsibilities
(Hover Over)
Level Design
Level Design
Drawing inspiration from Zelda and Souls-likes to deliver a classic dungeon with an emphasis on verticality and player choice. Greyboxed in UE5 according to metrics, then arranged playtests to gather data and refine layout.
Quest Design
Quest Design
Interweaving the level and quest into one experience. Implementing and debugging quest logic/progression via visual scripting, gameplay tags and blueprints. Importantly, the quest, level and narrative all had to align with the wider experience and goals.
Narrative Design
Narrative Design
Designing a story and NPC with notable twist and morale dilemma told in 10 minutes of gameplay. Went from flowcharts of dialogue in Miro, to visually scripted dialogue trees, along with environmental story telling discussed with artists.
Technical Design
Technical Design
Using blueprints, structs and gameplay tags to implement new reusable actors and utilities used by other designers at the time and later on at least 5+ other levels. Assisted other developers with technical problems, empowering the whole team.
Presenting
Presenting
As well as updating the senior throughout, and engaging in daily standups to communicate progress, I gave a fully prepared presentation on the quest, level and narrative, explaining why they would bring value to Samsara. Afterwards my work was highlight by company seniors for originality and quality of the pitch.
Description
Role(s)
Level Designer, Quest Designer, Narrative Designer.
Employed Freelance.
Team Size
20+
Including a senior designer and 5 other freelance juniors.
The Background
Infinity27 is an indie company that offers government-funded skills bootcamps in game design, to create content for their game, Samsara.
I had to concept, iterate, and pitch an idea to my mentor, that enhances and suits the game, then implement it in engine, with frequent access to feedback and specialised lectures. As a big souls fan, my dungeon was designed to honour the series.
This lasted across September, full-time, and afterwards I received a freelance contract to continue my work, so it could be properly included in the full game.
Genre
Souls-like action game
Duration
September 2024 - February 2025
The Project
A dungeon focussing on non-linear progression, verticality, and interconnectivity. Along 4 individual paths are statues players need to interactive with to open the final door. Each of these paths loops to a different level of the central chamber, before returning to the start. Players who interact with the NPC (Amira) receive a greater reward at the end.
Links & Tools
Further Details

Pre-Production

Production

Post-Production
Reflections
Recapping level design fundamentals
I was reminded of Level Design techniques I had slowly begun to neglect. For instance, shape & colour theory, leading lines, and framing. In every beat of the level I spent time on composition (the arrangement of scene elements to convey emotions or information), finding shots and going through a list of techniques.
Additionally, I had a lot of issues with metrics, as I was still getting used to the camera and controller. Early versions were too narrow, so I would frequently go through with ruler tools to balance out the spaces.
Other techniques I utilised include signposting, beat sheets, flow charts, timelines, teasing, bubble diagrams and "the Jesus Christ effect" as Christopher Totten calls it.
Working in a professional company.
I joined daily stand-ups, watched sprint meetings, learned new software like Perforce and Hansoft, received frequent support, and had access to all of the company's tools and documentation.
I also picked up a number of good practices (Hansoft cards templates, when to submit changelists, efficient stand-up answers), and enhanced ones I already liked (naming conventions, understanding file structures, documentation through Miro).
Self-management
Due to working freelance, with a loose task and deadline, I was able to be flexible and test out the most efficient ways I work. I set aside certain days a week to work on the project, while adjusting depending on progress tracked through hours and tick lists.
bottom of page














