About me

My name is Piotr Bień

I help game teams get audio in order so it doesn't come back as a problem during production.

I come into projects as Audio Lead – the person responsible for the decisions, direction, and quality of the audio layer.

Experience

I've worked on 17 game projects

Including:

7 full productions from the ground up.
3 ports.
DLCs and ongoing development of existing projects.
Projects where I came in at the stage of sorting audio out.

My experience covers, among other things:

Creating and implementing audio.
Working with development teams.
Stepping into projects at different stages of production.
Solving problems related to audio implementation.

This is best seen in the projects where an existing system had to be sorted out – the ones where audio had already started to become a problem.

View portfolio

Background

I have over 18 years of experience working with sound and music education, including 3+ years in game projects and audio implementation.

A degree in music for multimedia.
Further specialization (music therapy).
Experience as a multi-instrumentalist.

This is backed up by technical credentials:

A degree in software engineering.
AVID Certified User certification (Pro Tools).
Working knowledge of audio from both the production and implementation sides.

This combination gives me a technical and musical foundation – but above all, a way of thinking about audio as part of the whole project, not an add-on.

How I work

Or: who I am inside a project

I make sure audio doesn't just sound good - but actually works inside the project: technically, in production, and for the player.

In practice, that means:

I understand how audio functions inside a game engine.
I can talk to programmers and the development team.
And I make sure audio decisions don’t come back as a problem during testing.

I don’t come into a project as someone who executes individual tasks. I come in as someone who sorts out how audio is being thought about.

How this looks in practice

In most projects, audio isn't a problem at the start.

It becomes one when:

There’s no agreed approach to implementation.
There’s no single person in charge.
Decisions get made by accident, or too late.

The result?

❌ Audio starts blocking the team’s work.

❌ Problems only surface during testing.

❌ And fixes cost more than they should.

These are things that can be set up earlier -if someone takes ownership of them.

My role in those situations

I come into projects as someone who:

Bridges the creative and the technical perspective.
Helps the team make decisions instead of postponing them.
And makes sure audio stays cohesive from the start of production to the end.

As a result:

✅ Audio doesn’t come back as a problem at later stages.

✅ The team doesn’t lose time putting out fires.

✅ And the game sounds the way it should – and lands that way with players.

Technical setup

I work from a professional, acoustically treated workstation, with the setup needed to operate in more demanding conditions (5.1, VR, and others).

I work across different environments (Pro Tools, Reaper, Nuendo, Logic), so I can adapt to the project’s pipeline instead of blocking it.

That lets me:

Test solutions in real conditions.
Roll out changes faster.
And avoid problems that only surface at the end of production.

If you’re starting a project and want to avoid mistakes at the start, or you can feel that audio is starting to slip out of control,

this is the moment to get it in order.

During the consultation, we walk through how audio is set up in your project. I point out the specific things that can cause problems - and what needs to change so you don't have to come back to them during production.

Book a consultation