Architecture careers in the metaverse are not about abandoning real buildings. They are about applying spatial judgement, visual communication, computation and user experience to digital environments.
This conversation with Shajay Bhooshan and Andrei Dolnikov is useful because it treats the topic seriously. It links metaverse work to design research, visualisation, digital production and the question of what architecture-trained people can actually contribute.
Watch: architecture and the metaverse
This episode is useful because Shajay Bhooshan and Andrei Dolnikov connect virtual space to real design, computation and visualisation practice.
Listen: the full metaverse architecture discussion
Prefer audio? The full conversation gives more detail on computation, visualisation, virtual environments and the skills that sit behind the metaverse headlines.
You can also open the related Architecture Social podcast page.
Why architecture belongs in the conversation
Virtual spaces still need sequence, scale, atmosphere, narrative, wayfinding and a sense of how people behave. Those are architectural questions, even when the output is not a planning application or a building on site.
That does not mean every architecture candidate should suddenly rebrand as a metaverse designer. It means the skills may be relevant if you can show how your design thinking works in digital space.
What Shajay Bhooshan and Andrei Dolnikov bring to the topic
- Computation and research from the Zaha Hadid Architects CODE context.
- Visualisation and storytelling from Binyan Studios and ASAI.
- A link between experimental digital work and professional design discipline.
- A useful challenge to shallow hype around NFTs, virtual land and digital twins.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Listen next: the business of metaverse architecture
The Sunken Blimp episode is a useful follow-on because it moves from creative possibility into client work, budgets, events and commercial metaverse projects.
You can also open the related Architecture Social podcast page.
What skills matter beyond the hype
The useful career skills are not just software. They include parametric thinking, spatial storytelling, visualisation, game-engine workflows, collaboration with developers and the ability to explain why a digital environment should work a certain way.
If you want to position yourself in this area, your portfolio needs to show process as well as spectacle. Include diagrams, tests, iterations, technical constraints and the user experience problem you were trying to solve.
How to position this in your portfolio
- Show one digital environment or computational project with clear captions.
- Explain the design problem, not just the software used.
- Use the portfolio guide to decide how much process to include.
- Use current architecture jobs to see whether employers are asking for visualisation, computational design or digital delivery skills.
A practical way to judge the opportunity
Ask three questions before chasing any emerging digital role. Who pays for the work? What problem does it solve? What evidence do you have that proves you can do it? If you cannot answer those, the idea may be exciting but not yet a career strategy.
Metaverse career filter
Use this quick filter before putting metaverse work at the centre of your CV or portfolio.
- Can you explain the user or client problem?
- Can you show spatial thinking, not just visuals?
- Can you name the workflow or tools honestly?
- Can you connect the work to a role someone hires for?
- Can you explain what you personally contributed?
Common mistakes
- Using metaverse language without explaining the design problem.
- Showing impressive images with no workflow or authorship context.
- Ignoring commercial reality and who would fund the work.
- Pretending speculative digital work is the same as built project experience.
- Forgetting that architecture title rules still matter in the UK.
Architecture Social view
Stephen’s recruiter view is that emerging specialisms need practical evidence. The more experimental the field, the clearer your explanation has to be.
Next step
Use the Architecture Social portfolio guide to sharpen your digital evidence, then browse architecture jobs for roles asking for visualisation, computational design or digital delivery skills.



Add a comment