This is a really interesting question. All of this really depends on YOUR needs, which we cannot know with the details you've provided. So some guiding questions: 

- What will be the sound artist's tasks for working on your game? Will they be implementing the audio itself or just creating the audio? 

- What device(s) and platforms will your game be launched on? Any specific needs or requires those devices/platforms have for audio assets? 

What audio engine do you have in mind for this game? Middleware option or proprietary? Device specific?

- What KIND of audio do you want for the game? Interactive? Linear? Surround/VR/AR type audio? 

- Do you want a sound artist that will do everything (music, sound design, voice over direction/recording/editing, mixing, mastering and implementation)? That's a wide net. Sometimes you're better served getting two people who can divide these tasks up amongst their specialities. 

No offense but it's a bit odd that you're coming to a forum asking what skills a sound artist should know for your own game. It's almost as if you're not sure what audio your game needs. Usually once a game engine is selected, many of the questions above are answered, at least to a degree. And if you're unsure, and that's okay, then you need someone to act as a consultant. For example, is your game in pre-production or production? Regarding your question about what software should they know - that's really up to you. Are they going to use source control at all? Or are they just going to throw sound assets over the fence for implementation? If they're just creating audio for you - it almost doesn't matter what software they know because so many audio programs can do many of the same things.  

When I'm looking for someone to collaborate with I look for several factors:
- quality of their work: does it match the aesthetic I'm after. This is mostly subjective. 
- ease of communication: does the freelancer get back to me in a reasonable amount of time. Do their emails make sense? Does it seem like we can get along? Especially during stressful production periods? 
- ability to take and incorporate feedback well: you want someone who's open to revisions and open to making compromises so their audio ends up being the best for the project. Not someone who's going to say "nope, the audio is done - no changes." (I've heard some people say this before!!) 
- can they do the tasks I need: this goes to an earlier point. A bonus is if they can do all of these tasks and also fulfill a few other extra tasks that I hadn't considered (i.e. maybe they can also program some, or do some light artwork, can write really good dialog, etc).
- their cost: obviously if I cannot afford to pay their rate, how can I hire them? You need to know your budget and know what a person's cost will be. Are they going to charge hourly or per sound asset that is delivered? What is the payment method? Milestones? Monthly? Etc. Lots of details to work out. Or are they salaried? Will you offer benefits? Etc. 

And in the end - the only thing that really matters is that you like the audio this person creates and that it serves your game well. If you meet those two items, you've done a great job. 

1. Name in the credits of released games, and references.

2. I never asked my audio engineers what software they knew. If they had previously done some released games, they clearly knew what they were doing.

3. Know how much you can afford. Don't forget that you get what you pay for; someone who's willing to work for pennies may give you just pennies' worth of end result. 

4. Have a good work for hire agreement ready for the vendor to sign. Make sure it covers the originality of the work and you are indemnified; you don't want somebody using ripped-off assets that can get you sued later.

I,m going in the studio this year for recording sound effects for my game,

[offer of work deleted by moderator]

Ask for hardware only.

Else take the one with the biggest modular wall :

[removed by moderator]

Please note that i dont have such a wall.

Incredible Smoker - You've routinely been posting on people's threads in this forum and asking for exchange of work. This is to be done in the Careers section. You can post as a contractor under audio or you can post in the Hobby Projects section. I've already deleted one of your posts and then you posted again and another mod edited that one. This is your warning. Stop spamming the forum in this way. Feel free to actually respond to people's questions with thoughtful answers and take part in discussions. Advertise your services in the Careers section. 

And responding with a eurorack hardly addresses the questions that the OP is asking. A eurorack is great for certain things but not everything and it isn't a complete, all-in-one audio solution. It's akin to me asking about what steps are needed for renovating my home and getting a response like "all you need is a hammer." For game audio there are lots of tiny details and factors that simply owning a huge eurorack doesn't even begin to address.

On 8/1/2018 at 7:48 AM, JoAndRoPo said:

Hi! 

I need a sound artist for creating bg, sfx, etc for games in a small startup company.

1. What qualification or skills should I search for?
2. What software should he/she know?
3. Is there anything else he/she should know when creating BG music, sfx, etc?
4. Any tips before I start searching?

1 - Look for someone that has a track record of following through with things - people who flake out on your and can't deliver on their commitments are just as big of a problem in this line of work as any. Figure out how to assess their reliability before you pay them a dime is pretty crucial in my opinion.

2 - depends on your needs

3 - Choose your employee based on their base skill set, but also make them prove to you they have the drive and the means to learn these skills. And also ask them something like "Whats the difference between a Sennheiser MK series mic and a Neumann U87". Or "Tell me what a resonance filter does". Or ask them to explain the difference between a reference clock and a word clock in plain English. Forget about games...That's very basic 101 level audio stuff. If they can't tell you that off the top of their head, you probably don't need to be paying them money to do work for you.

Also, make them prove to you that their plugin licenses aren't stollen. That'll weed out 9 of 10 wannabe's. 

4 - I think you need a way better idea of what you're after. If you're looking to start a game design company, it sounds like you have a good ways to go before you're ready to bring a sound designer onboard. If I were you I'd wait until you have at least one working playable game before you even begin talking to a sound designer.

On 8/1/2018 at 9:43 AM, the incredible smoker said:

Ask for hardware only.

Else take the one with the biggest modular wall :

That's gotta be the worst advice I've ever heard.

1 hour ago, jkuehlin said:

3 - Choose your employee based on their base skill set, but also make them prove to you they have the drive and the means to learn these skills. And also ask them something like "Whats the difference between a Sennheiser MK series mic and a Neumann U87". Or "Tell me what a resonance filter does". Or ask them to explain the difference between a reference clock and a word clock in plain English. Forget about games...That's very basic 101 level audio stuff. If they can't tell you that off the top of their head, you probably don't need to be paying them money to do work for you.

Interesting idea but in all of my years of working, I've never had a potential client or employer ask me this question. I've had audio directors ask me what I use and why. They want to know my logic in choosing my tools and how I apply them. Asking very specific questions about audio only works when the interviewer knows about audio themselves. Otherwise, they could quickly be taken by a BS response. 

So in the case of the OP - I wouldn't do this. Instead I would ask a more questions about workflow, collaborating with team members, receiving feedback, examples of how they've resolved conflicts in the past. Etc. If the OP likes the audio they've heard from the interviewee then it's more a matter of do you like the person in front of you? Will they work nicely in a group setting? How do they handle working under pressure and tight deadlines. Stuff like that. 

Having a good answer about different mics doesn't really answer any of that. Nor does it prove how useful and effective a team member they'll end up being. Just my opinion.

1 hour ago, jkuehlin said:

Also, make them prove to you that their plugin licenses aren't stollen. That'll weed out 9 of 10 wannabe's. 

There's a much easier way to handle this, have a clause in the contract that indemnifies the company and puts any legal issues related to misuse of copyrighted audio material back on the audio artist. They could even have a clause saying "To the best of my knowledge, I'm only creating audio content with source materials and software I have a legal license to use." and so on. So if they ever did have an issue, a clear paper trail goes right back to the audio artist and leaves the company blameless. 

Or if it's a in-house position, just provide the needed hardware and software and then you know you're golden. 

4 minutes ago, nsmadsen said:

Interesting idea but in all of my years of working, I've never had a potential client or employer ask me this question. I've had audio directors ask me what I use and why. Asking very specific questions about audio only works when the interviewer knows about audio themselves. Otherwise, they could quickly be taken by a BS response. 

Nate...even apart from JoAndRo's specific scenario, what do you feel is the best way for an employer to gauge the extent of a potentials audio engineers competency level? University of Michigan had people submit a written essay on how they mixed a track or series of tracks explaining what they used and why. The hiring agency at Disney drilled us with some music theory and audio production questions in the initial phone interview to vet out the people who were total hacks. In the instance that the hiring agent has no technical expertise in the audio field, should he have a 3rd party conduct the interview on his behalf? I guess my question is how a game dev is supposed to evaluate an audio engineers actual abilities before hiring them.

16 minutes ago, nsmadsen said:

There's a much easier way to handle this, have a clause in the contract that indemnifies the company and puts any legal issues related to misuse of copyrighted material back on the audio artist. They could even have a clause saying "To the best of my knowledge, I'm only creating audio content with source materials and software I have a legal license to use." and so on. So if they ever did have an issue, a clear paper trail goes right back to the audio artist and leaves the company blameless. 

But is that sufficient? If the sub-contracted studio simply lies and signs the contract anyway, it seems a number of scenarios the contractor would want to avoid would only surface post-facto.

I was sending audio edits out to a guy with an outdated stolen copy of Pro Tools, and couldn't figure out why his files were named inconsistently. Then I realized he had a cracked copy of PTv9 which didn't have the batch export feature, so he was attempting to manual re-type each file name to cover it up. Even if he had signed that contract, he wouldn't have been able to sync to the avid cloud either...because you have to have a valid support contract to access it. So basically the bugs and issues in his stolen copy became a huge issue to our workflow even though legal issues did not. Same issue with a guy who lied about having valid Waves licenses. My plugins wouldn't load in his DAW, and the Mercury 10 bundle has a lot of plugs in it that the Mercury 7 bundle doesn't. I don't know man. It was just a lot of wasted time back-and-forth with these numbsculls. I'm glad to hear this hasn't been an issue for you

17 hours ago, jkuehlin said:

he had a cracked copy of PTv9 which didn't have the batch export feature, so he was attempting to manual re-type each file name to cover it up. Even if he had signed that contract, he wouldn't have been able to sync to the avid cloud either...because you have to have a valid support contract to access it. So basically the bugs and issues in his stolen copy became a huge issue to our workflow even though legal issues did not. Same issue with a guy who lied about having valid Waves licenses. My plugins wouldn't load in his DAW, and the Mercury 10 bundle has a lot of plugs in it that the Mercury 7 bundle doesn't. I don't know man. It was just a lot of wasted time back-and-forth with these numbsculls

Numbskulls who misrepresent in contractual dealings get weeded out. Either their shenanigans get them shunned from the industry, or they wise up and get legal. 

17 hours ago, jkuehlin said:

what do you feel is the best way for an employer to gauge the extent of a potentials audio engineers competency level?

A producer likely isn't expert in all the fields of expertise he's hiring. Producers often have to rely on leads to make such judgments. If I'm in need of a programmer, I look at a candidate's track record, and I call his or her references. If there's to be a technical test of some sort, then I can neither come up with such a test nor judge the test results, so I either have my tech lead drive that, or ask a trusted colleague for some assistance with it. In the case of audio, it's often the case that there is no in-house audio expert to ask about mic differences or best tools, and the producer has to rely on credits and references. And calling producers on the candidate's previous projects. 

By the way, this whole topic is more a Production/Management question than an audio question.

17 hours ago, jkuehlin said:

Nate...even apart from JoAndRo's specific scenario, what do you feel is the best way for an employer to gauge the extent of a potentials audio engineers competency level? In the instance that the hiring agent has no technical expertise in the audio field, should he have a 3rd party conduct the interview on his behalf? I guess my question is how a game dev is supposed to evaluate an audio engineers actual abilities before hiring them.

All I can speak to is my own experiences which include 4 in-house positions as well as 5 years of freelancing full time. (Technically, I've been freelancing for 13 years solid but only 5 years where it was my main, full time gig.) And in all of those experiences, I've had audio directors give me audio tests. Take a chunk of the game or video, score it/sound design it/mix it and submit it for review. Then usually the audio director would chat with me afterwards about my approaches and want to know my reasoning behind it all. 

But let's back up a bit. For larger companies, I'd usually have 1-2 interviews with a more general, HR type person. Then after passing those, I'd get an interview with an audio person (if there was one). For smaller teams, this may not be the case. But even with smaller teams, usually a client wants to hear my audio, may have a very tiny sound test for me to do (but not always) and then wants to know my rate and my timeframe. 

17 hours ago, jkuehlin said:

I was sending audio edits out to a guy with an outdated stolen copy of Pro Tools, and couldn't figure out why his files were named inconsistently. Then I realized he had a cracked copy of PTv9 which didn't have the batch export feature, so he was attempting to manual re-type each file name to cover it up. Even if he had signed that contract, he wouldn't have been able to sync to the avid cloud either...because you have to have a valid support contract to access it. So basically the bugs and issues in his stolen copy became a huge issue to our workflow even though legal issues did not. Same issue with a guy who lied about having valid Waves licenses. My plugins wouldn't load in his DAW, and the Mercury 10 bundle has a lot of plugs in it that the Mercury 7 bundle doesn't. I don't know man. It was just a lot of wasted time back-and-forth with these numbsculls. I'm glad to hear this hasn't been an issue for you

Wow, that does really suck! But this is a special case. Most of the time, unless you're working with a team of audio dudes n gals, you're going to be creating and sending the audio files to the developer directly. So none of these issues you've pointed out would happen in MOST cases. (There are always exceptions of course) Trading audio session files rarely happens when I'm freelancing. Heck, it rarely happens in my current in-house job and we're an audio team of four people! Usually if I need something from someone else they make that track by referencing a mix of my stuff. Even when I'm subcontracting out recording work for pieces I'm doing for a client - my subcontractors are working off a mix I've provided, not sharing my actual session. 

So, what you've cited above doesn't really apply to most of the game dev I've been a part of in the last 13 years. Sometimes in rare cases it does. Like when I did some dialog editing for a film trailer and we were all using Pro Tools. But in most of my work, it's simply not been an issue. Which is why I go back to most devs want to know: 

- how good is your audio?
- how much will it cost? 
- how long will it take for you to make it all?