shlevy:
itsbenedict:
OKAY HOLY SMOKES, I just landed a real interview with a games company that wants to hire me in San Francisco! It’s looking pretty likely that I’ll get it, but first they want to know what my salary requirements are. And… living in the Bay is, from what I’ve heard, incredibly expensive?
So, before I email the guy back- I know a bunch of you live in the Bay Area, so do you have any advice for me? Gamedev salaries aren’t the same as general tech salaries, so I want to give him a pretty small number, but I don’t really know what the cost of living’s like.
Relatedly, there’s rationalist group housing in the Bay, right? I know there’s Volterra, at least- who’s still got space, what kind of options are available, and what’s the rent/cost of living like there? Can I get a crash course in how to live in the Bay?
( @michaelblume @ozymandias271 @luminousalicorn @theunitofcaring and anyone else who’s in the bay (but who i can’t be sure i remembered where they live correctly so i didn’t tag them))
Re: pretty small number: Beware of lowballing yourself. Once you find a number that makes sense to you given comparable roles, cost of living, etc., inflate it a bit.
(This is not specific to game development, general salary negotiation advice for a new hire).
Oh! I have salary negotiation advice since I *just* did this with my new job!
Don’t give them a small number. They already have a salary in mind for you, and they’re trying to see if they can save money by having you accept a lower salary. So, if you name a lower salary than what they were thinking, they will definitely give you the exact salary you named and not any higher. If you quote a higher salary than what they were thinking of, they’ll try to negotiate you down, but (unless the number you mentioned was *waaay* too high to be reasonable), you’re basically not going to lose an offer because the number you gave them was too high.
If you can, avoid naming a number altogether – when they ask you, say something like “it’s hard for me to name an exact number without having a better idea of the full compensation package. I’d be looking for market rate for a game dev of my skill level in the Bay Area, though. Could you tell me what the company is thinking?"
It may sound weird and evasive, but this is a really common thing for candidates to say, so the HR/recruiter person will be expecting it as a possible response.
I evaded the question with the job I just accepted – I asked them what salary they were thinking of – and it turned out the salary they were thinking of was >10% higher than what I’d been expecting / what I’d have been comfortable naming.
I…. actually have a longish email’s worth of salary negotiation advice / accepting-an-offer advice in general, that I could forward to you if you PM me your email address.
@itsbenedict
And congratulations / good luck!!! :D