Speculative applications and knowing when not to bother
polycounter lvl 13
Hey guys, I'm in the process of applying to companies throughout the UK for environment art roles; and I've sent out a few speculative application to companies who say they accept them on their site.
But today I was trying to send a speculative application to a company owned by a big publisher, who don't have their own proper website and instead have everything filtered through one careers portal where you sign-up, etc. So the company are hiring (although not any junior positions) but there's no space for speculative applications or any actual general job email address. Is this a sign that the company doesn't want speculative applications, or is it simply large-publisher bureaucracy (okay, not the right word, but you get what I mean)?
My first port of call was the Polycount Job Census, to see if I could PM someone who worked there, but unfortunately no one does. Apart from bugging someone on LinkedIN (I could only find a higher-up) I'm not sure what to do.
Advice?
But today I was trying to send a speculative application to a company owned by a big publisher, who don't have their own proper website and instead have everything filtered through one careers portal where you sign-up, etc. So the company are hiring (although not any junior positions) but there's no space for speculative applications or any actual general job email address. Is this a sign that the company doesn't want speculative applications, or is it simply large-publisher bureaucracy (okay, not the right word, but you get what I mean)?
My first port of call was the Polycount Job Census, to see if I could PM someone who worked there, but unfortunately no one does. Apart from bugging someone on LinkedIN (I could only find a higher-up) I'm not sure what to do.
Advice?
Replies
I live in the South West of the UK with only a hand full of game developers within like 4+ hours of travel, all of which are relatively small handheld/browser based studios.
I sent out a speculative application to a studio which was fairly close and I went in for a talk/interview which went really really well in my opinion. However, they aren't thinking of hiring for another like 3 months and even then there is no guarantee that they actually will. If and when the do I will have to go through the whole application/ interview process again.
I have heard a lot of people say, "If they like you they will make a job for you", but I have found myself being in a similar position to anyone applying there in the future, apart from having the slight advantage of meeting the team before.(although that could also work against me as I wouldn't really have as much to talk about in my 2nd interview haha)
I was just wondering is this was the same for a larger developer or if they would actually 'make' a job for me (if my work is good enough) without having to advertise it and interview people?
I understand that everyone deserves an equal chance etc but I don't really want to spend hundreds of pounds travelling up country, to be in a similar position to someone applying fresh off the bat to a advertised position.
I am just looking for advise as to if I should continue to send out speculative applications, or if I should only do it local companies so that I am not hounded by travel costs?
Thanks PC
A developer will not make a job, unless there is work to do and they need another set of hands to do it. Simple as that. The money has to be on its way into the studio, before they'll consider paying it out for a new hire.
If you happen to hit their radar when this is occurring, and you fit their needs, then they might hire you. If there are no other applicants, like it's especially dry for them, you could just get the job without them interviewing others.
It is very rare to find a single applicant that is a must-have, without needing to compare them against multiple other applicants. You have to really stand out for this to happen, and you have to have a decision-maker in the company that is totally gunning for you.
You should just bite the bullet, and spend those pounds. If you want the job, go get the job. Remember you are usually competing against other applicants. Be the best.
If you honestly think you can bat at the same level as a senior, go for it; even if you've not worked as a senior before. But if you're just chancing your arm, better to save the lead the trouble.
A couple of guys who worked at Weta and ILM said that they would prefer working (ESPECIALLY when under crunch), with people who have some base understanding of how to synchronize themselves with one to another during the pipeline, and that a new comer who has no experience on that side of things could potentially slow them down, as you need to take time to tell them what to do and how to deal certain issues.
I'm not sure how valid that is by today's standards of mutiple year cycles, especially in game dev, but I thought of sharing this little story incase anyone has anything interesting to add to it.