Pixaera
Senior Level Designer

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Mission
Own the playable quality of the experiences you build, end to end, and raise the bar for how the rest of the team builds. What you ship should be clear, engaging, and coachable for frontline workers, grounded in real work and correct procedure. You turn a brief and expert input into a spec others can build from, then build it yourself.
Outcomes you're accountable for
- Playable experience quality, across every module you own primary
- Learners understand goals, consequences, and feedback without confusion, and can connect "what happened" to "what to do on the job".
- Every module you own is readable, well-paced, and tuned, not just the one you touched last.
- Scoring reflects real performance against the objectives, and you notice when what a module rewards and what it teaches have drifted apart.
Procedural fidelity
- Safety-critical detail is correct, checked with subject matter experts early. Necessary adaptations are explicit and documented.
Design direction that is buildable
- The spec, brief, and acceptance criteria are clear enough that another designer can build from them without guessing.
- Design intent survives production constraints through early validation and honest trade-offs, not late heroics.
They ship, and the customer trusts us
- Your modules hit their dates in every language and customer version, and you own release readiness rather than handing over a finished level and hoping.
- Client feedback gets triaged and answered. You know which requests improve the learning and which only cost money.
The team and the pipeline get better
- Other designers know what "done" looks like because you have shown them and reviewed their work against it.
- The authoring pipeline is measurably better because you worked in it, and you can point at what you changed.
Responsibilities
- Design the moment to moment
- Define how the module plays: learner flow, the decision points, the feedback at each one, failure, and recovery, and what good looks like.
- Turn objectives into in-experience success criteria: what the learner must demonstrate, not what they are told.
- Design the decision, not just build it: what the learner chooses between, what makes the wrong choice genuinely tempting, and what the consequence teaches.
- Evaluate existing systems and mechanics critically, and find the changes that improve clarity, engagement, and learning outcomes. Contribute to narrative design as we run more designs in parallel.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
-
Build it, end to end, and agentically
- Build in our authoring pipeline using Claude Code: spec, images, voice, and video, scenes, captions, questions, preview, release.
- Direct the models. Measure before you ask for a change, keep edits surgical, verify the result, and know when to stop looping and do it by hand.
- Build and iterate in Unreal Engine 5 where the module calls for it: greybox, sequences, the state machine that drives the experience, render, and export.
-
Raise the bar
- Review other designers' work, run critiques, and define what "done" means for level design.
- Make prioritisation calls against real deadlines, including what gets full polish and what ships as good enough, early, and in the open.
- Push art, engineering, localisation, and QA to hone the experience rather than accepting the first thing that renders.
- Mentor mid-level designers and onboard contractors, including on how we work with agents.
-
Improve the pipeline
- Own a pipeline or workflow improvement and land it with our engine and platform team. The authoring pipeline is a repo designers commit to, and the people who use it are expected to shape it.
- Bring workflows and tooling we are not using yet, and make the case.
What we're looking for
- AI native, in production. You build with agentic coding tools, Claude Code or equivalent, on real deliverables with real deadlines. Required. Expect to walk us through something you shipped this way, including where the model failed you and what you changed as a result.
- Evidence you have pushed the field forward, at any scale: a workflow you invented, a tool or skill you built for the people around you, a technique you worked out and taught. We weigh this above years.
- Design craft. You can say why a scene is not landing, and you can set that standard for other people.
- Around 6 or more years in game or level design, including owning a shipped product or a significant slice of one, and deep Unreal Engine 5 skills.
- Fundamentals: pacing, readability, feedback loops, consequence, and failure handling, and the judgement to know when a design is not working.
- Strong judgement on generative output, and able to hold others to it.
- Comfortable in a repo: branches, pull requests, reviewing others, and being reviewed.
- Communicates openly and early, including when the news is bad. Moves other functions without needing an escalation.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
Nice to have
- Localisation at volume, VR or web builds, or safety and industrial training content.
- Experience mentoring designers or leading a small pod.
Why Join Pixaera?
- Help redefine how safety training is delivered globally
- Work at the intersection of learning science, AI, gaming, and immersive technology
- Have meaningful ownership over the experiences you create
- Join a high-calibre team focused on building category-defining products
- See your work directly impact the safety and readiness of frontline workers around the world
If you're excited about creating learning experiences that people actually remember—and that can genuinely change behaviour—we'd love to hear from you.
At Pixaera, we’re committed to building a workplace where everyone feels respected, supported, and empowered to thrive. We believe that diverse perspectives fuel creativity and innovation, which is why we celebrate individuality and foster an environment of inclusion and belonging.
We’re proud to be an equal opportunity employer—discrimination of any kind has no place here. No matter your background, identity, or lived experience, you’re welcome at Pixaera.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Skills
Location