Quote:
Originally Posted by jjshabado
I think the correct answer is to talk about how you have a lot of experience with the non-technical things like managing people, working with people, getting **** done, whatever specific things you have a lot of experience doing that translate well across positions. Talk about how you would have no problem with this aspect of a senior position.
But then mention that you're worried that since you don't yet have many years of technical experience you're looking for a role where you can get some of that technical experience before taking a senior role. And that you're excited to work for a place where you know you can learn those skills and still have lots of opportunities for advancement.
Seems like solid advice, as always.
I get hung up here because, like any job position to fill, there is always someone else coming in to interview an hour later. What validation does determination, willingness to learn and grow, and a dirty joke offer if I don't have the goods?
I guess there is also the aspect that "senior" may not have the definition I would expect it to have. I'm thinking super-human knowledge, but you seem to be suggesting that softer skills can be used to woo employers into believing that I am worth a long-term investment. Even so, with the years needed to gain respect from coworkers (which is vital for this sort of position, IMO), I'm tacitly promising 5+ years at the company, which should be reasonably met with skepticism at the interview stage.
I have a tough time with titles. At a previous job, I was the "marketing director," although that didn't mean much since I was the only person in the marketing department. The same goes with my current job, which includes the word "manager" or "lead." I don't consider myself a good manager, lead, director, or whatever.
I'm waxing and should be trying to catch up on sleep, but I found this bit funny:
"WHAAAT.... UNIT TEST !!!! I'm a senior programmer... I don`t need to test my code any-more"
Heard that before.... Thus he lets the "Juniors" fix his bugs and test it.
"We are going to hire an architect... no, not Mr X, we want someone that is much more senior, someone that is no longer coding"
later in the interview :
- so what programming languages are you familiar with ?
- ahem... I've used COBOL and FORTRAN but now mostly it`s Ms Word, Excel and Powerpoint.
- Excellent... when can you start ?
Quote:
I wouldn't worry about losing face at the whiteboard. I mean, who cares if you fail, right? Some day I'll talk about how I once blew an interview that was worth many multiples of my current net worth...
Not worried too much. I fully expect to bomb my first few attempts, though I won't do this without giving it my all and preparing beforehand.
"What is the difference between a black-red tree and a b-tree?"
"What are good strategies for preventing collision in a hash table?"
"Does SAT imply NP-Complete?"
Oh, fudge, reading too many blogs.
Quote:
I would worry about not setting expectations properly if you get hired for a role though - so I think you need to stress that your experience right now isn't that technical.
Yes, this does worry me. I'm confused by the reactions that I get.
One time, I applied to a PHP job. I was arranged to have an interview and the guy on the phone said. "So, you don't have experience working with PHP, right?"
Well... I've built websites.
"Have you ever even
seen PHP?"
Of course I have, and surprisingly, I didn't go blind. Go figure.
The other extreme is that I am responded with a thanks for applying to a position that I know I didn't apply to, let's set up a time to talk. I either have a link to the position in the email or I have to search for the position named in the email. The requirements are:
7+ years experience working on a high-scalability, reliable, concurrent network systems.
Experience using Perl, Ruby, and Bash for Linux cluster automation.
Hand-writing optimized, MapReduce jobs on Hadoop -> MongoDB.
3+ years experience with a new-fangled language like Haskell, Clojure, Scala, etc.
A bit over-the-top, but not too far off, tbh. From one time, I can figure that there was a mistake and they meant to write someone else, but after a few times, something is weird.
Quote:
Originally Posted by kazana
Agree with jjshabado.
Tell them you are honoured but why you are hesitant. Another good angle (which I always use in my interviews) is asking which aspects of the job they expect you to struggle most so you can prepare for that.
This is an interesting perspective. Would I also want to ask what is non-negotiable knowledge as well, or am I digging a hole?
Quote:
I cannot fathom a capable, friendly person able to learn and close the gaps quickly ever being fired in such a position. Unless you run into a last-in, first-out situation.
I can. I've had to do it myself. Unfortunately, the business comes first and overrides any emotional investment I have in people. I always try to find another position for them to work in first, but my work experience is at places that I can shift their job to something different.
This also means that I don't fire people because I don't like them. Two pieces of the same pie.