@MaskedMan Your answer here has gotten a number of noise comments focusing on a (perhaps imperfect) analogy instead of requesting real clarification. I was about to delete them but wanted to check with you first if you think they add value or not.
I think it's sufficient to edit part of your comment into your answer and then clean up the comments? (Haven't read through it all in detail)
@Lilienthal Uhm, I am undecided if they add value. They comment on a hastily made-up analogy, which is anyway an add-on, and not the main answer. I will just remove the analogy from the answer, feel free to delete all the comments. I will clean up my comments to save you some trouble. :)
Right then, I have removed the analogy and deleted my comments.
I'll have a interview soon, a face to face one, and I have the job description of such interview, but I haven't been given much information about the steps.
for example, last time was told I would have had a telephone interview. But it wasn't specify it would have been a technical one or not
at last it was a technical one, and so far I did well
So I have to do the last face 2 face interview
but again, I haven't been given much information about it
So I was wondering whether or not I can ask them for giving me some more details about this final step
In that case, probably not. You're going to want to be "the one who's ready for anything". In my experience, the last f2f interview is to get the sign-off from someone higher up than the person you'd be working for
Ok, well it could be anything then. Usually there's stuff like whiteboarding and I've had cases where they give you a computer and a problem to fix. Did they tell you how long the interview should be?
At the minimum, you can ask how long to expect for the interview. You're busy, you have other things to schedule your day around. :) Length often tells a lot.
Yeah, it's also a natural way to ask about it, "Hi, can you let me know what I should expect for the interview format and length so I can plan accordingly?"
Honestly, I wouldn't sweat it. They're going to check your personality and have you meet a few people for certain. Where I've had long phone interviews, they tend not to do extensive technical stuff on the face to face except to verify that you're the one on the phone. :)
Unless it's a huge company, then all bets are off. They tend to do things however they want and often weirdly too.
For instance, Norfolk Southern is known for having a hiring process that takes months, They get away with it because of the size and they're supposedly a good place to work.
If I were to guess then, I'd say it'll probably be a mix of technical and interpersonal. But there's really no telling. I've had interviews last for 2-3 hours because they just passed me from one group to the next.
And who knows, this could also be just the first face to face. They may have another.
I would try to think what you may ahve been weakest on the phone screen and brush up on that, but above all try to exude confidence when you get there. They liked you enough to bring you in so they obviously want to get to know you better.
And remember, you're also interviewing them. It's a two-way street. Even if you really need a job, you need to approach it somewhat like a relationship. They have to be good for you too, not just you being good for them.
I've found that 2 things make the most difference, when technical ability is no longer a question. Confidence in your abilities and passion for the the work.
@user8469759 interviews are for both the candidate and the employer, it's bad for either if the wrong person gets hired
2
as an interviewer, I want any candidate I interview to be fully confident of what working for us would be like if they get an offer - allowing them plenty of time to ask questions is important to that
I've asked about the hardware that developers use, I've asked "I understand that sometimes a team has to work over, can you tell me about the last time the whole team had to do that?"
But I can't stress enough to try to show passion for your work, assuming you have it. If you love what you do, let them see that. It's ok to get a little excited when describing something you've done that you're proud of.
Eye contact, without staring. (don't be creepy in other words). Lean forward and hang on every word.
And believe it or not, smile. I have to force myself to do that one. literally force it. I've got "resting jerk face" where if I don't look at least amused, I look pissed off.
I'll often ask them something semi-personal (but job related) like "What brought you here?" or "How long have you been with the company?"
No, but there are generics that you can ask anyone like "what do you like most about working here?" That gives them a chance to brag on their company a bit. and same with the ones I just mentioned "how long" etc.
And the most open ended generic question of all. "How would you describe the company culture?" can be asked of anyone.
I personally wouldn't ask for algos in the phone screen beyond "How does quicksort / bubblesort / heapsort work?" and "What is the best/worst case complexity of $ridiculouslypopularalgo"
awesome! I suuuuuuck at those kinds of things. My recall isn't great and I'm not very encyclopedic. Yet I'm very skilled so technical interviews can go either way depending how they approach it with me.
The sad part is I'm still better at many of those than most of the students we have interviewed for internships/graduation who are in CS/Computer Engineering programs >.>
@user8469759 one of the things I always tell people I interview is it's their thought process I want to see, not necessarily the "right" answer -- I know an interview is stressful
I mean, sure, but that knowledge is next to useless unless you have to re-implement them yourself, and even then you can look online about how they work.
Depending on how badly I want the job, I'll ask a silly question right back. I loathe them and don't appreciate being put under pressure to see how I'll react.
There are a lot of reasons to ask these types of questions. Many will say "cultural fit" or "see how think on your feet" or even "get insight as to how you think and give you a chance to explain why to see your thought process.
I'm sure there are some who will disagree but I see this as a psycho...
@Magisch yeah, that would be a sweaty moment I'll bet.
Yeah, it's also a natural way to ask about it, "Hi, can you let me know what I should expect for the interview format and length so I can plan accordingly?"
@user8469759 they won't call it that, but it's where you "meet the team" possibly some internal clients (people who'll affect the work you do) and your prospective boss and possibly his boss. That sort of thing. Mostly a personality compatibility interview.
I probably wouldn't do a 2 day long marathon either unless i was convinced it was a really great place to work. But that alone would probably convince me otherwise
In which case, I'd only do it if I were desperate.
When something says "casual" I wear a button down shirt and bring a tie that I haven't put on yet.
They didn't say anything, I assumed as long as I'm dressing decently (I don't have any tattoos neither I was wearing short sleeves t shirt or stuff like that)
@user8469759 That was dumb of them. I always wear a jacket and tie unless they specifically tell me don't. If they say "wow, you're way overdressed for what we wear here" I simply say "nobody specified casual so I consider it a sign of how seriously I'm taking this position. I can take off a jacket and tie, but I can't undo jeans and a polo."
If true, they'll probably sit you down and have you complete a task for them, or debug for them. I've had both. I hate that crap because it's like a "gotcha" question. They're looking for something specific and if you don't do it that way, it can be held against you.
how long was the phone interview where you're looking?
There's a possibility they'll count that as their technical interview. If it were me, I'd expect a "does he fit" type of interview as the face to face with some light technical stuff. Could be wrong, but that's been my experience with long phone screens.
I'd rather be corrected than wrong, so it's all good. Yeah, "really sucking" seems more visceral but my thinking was that it's ongoing and not likely to stop sucking. :)