How Do You Prepare For A Technical Interview? 

I'm glad it was helpful, and I agree that interviewers need to understand this as well.

100 percent correct

I am glad it was so helpful.

Thanks for looking to and trusting Tim

Thanks for watching

I am glad it was so helpful.

Please consider watching Tim's other videos on interviewing - ru-vid.comsearch?query=interview

oh shit same here!!

Best wishes on your interview.

You are welcome.

Awesome! I'm glad you were able to get the job.

Thanks for trusting Tim to help you prep for your interviews.

When I was a job coach, I stressed to my folks to focus on what you know. A good interviewer will ask tough questions to see how you handle it. What is your level of understanding and how to you address a problem when you don't know the answer. Tim's advise on how to handle the "I don't know, BUT..." is perfect in those situations. If you go into the interview knowing that you will get those type questions and knowing how to answer, you will be far more comfortable in the interview.

@@tomthelestaff-iamtimcorey7597 it definitely makes sense to have a sort of work-around without not answering it. I know in the past it has destroyed me if I have to say "I don't know" which isn't always bad but I really like the idea of following that up with showing how you would figure the question out.

Glad to hear it!

You are welcome.

Awesome! I am glad it helped.

I didn’t get the job after two interviews with the company. But you know what? The hiring manager told me I was the #2 candidate in the list, I interviewed well, and he found I would likely have done the job well. It was a great learning experience that I can take to my next opportunity. :)

Glad it was helpful!

Than you need to check out his dozens of other Dev Questions posts.

You've got a lot of other videos to check out then. This is video number 54 in this series. Hopefully there are others in the series that would benefit you.

Best wishes!

Thanks for watching.

Thanks for sharing.

I'm glad. Best wishes!

Please share with us how the interviews go. Also, note the other great tips in the comments below

Awesome! Best wishes!

Great!

Great advice, thanks for sharing.

@Jef You said "They DO expect you to know everything." and I've seen this in job postings for junior developer, or mid-level. They have a long list of technology requirements that even a senior or principal developer might not have encountered! So what advise can you give to applicants that want to send their CVs but lacked the skills on half of those in the list? Just skip and look somewhere else, or try and embarrass themselves for showing to the interview even if they know they're way out of their heads?

@@STUPIDRU-vid_HIDINGMSGS I totally agree. It's gotten out of hand.

@@STUPIDRU-vid_HIDINGMSGS You need to understand something, that posting is considered a wish list. They put everything hoping to get the best mix they can. Also, they need to be able, in today's lawyer driven climate, to have the ability to to justify NOT hiring you or hiring you over someone else. They don't really expect you (or anyone they can afford) to have all of it. So, go after it clearly calling out what skills you have and, as Tim states, show a plan for how you intend to learn the rest.

@@tomthelestaff-iamtimcorey7597 "They don't really expect you (or anyone they can afford) to have all of it." - If this is true, you've boosted my confidence a notch! Have a great day! Here's a sample of skills one company is looking for from a developer, and this is not even mid-level or senior type: Duties & Responsibilities Web Team is using AngularJs, VueJs or React, and Microsoft .net Core, .net Framework. A strong understanding of c# MVC, CSS, javascript, and HTML, SQL is required while experience in a .net based CMS system like Sitecore, Umbraco or similar is an advantage as is experience with MSSQL, PostgreSql, MongoDb. The API team is using Microsoft tech stack C#, MSSQL, .Net Core, and RESTful API. Some desired skills include Postgres, Azure Topic/Subscription/Queues and Kubernetes. The Identity Management team is using .Net Framework 4x, .net , C#, Web API, MSSQL , Azure Blob Storage (Tables & Queues). Familiarity with OAuth 2.0, SAML 2.x, OpenID Connect, JWT (JWS,JWK) , Identity Server 4. Working knowledge in PowerShell scripting. Other desirable skills MySQL , Classic Asp , Asp.Net Web Forms , Active Directory

Yep. Don't just act defeated. Act as you (hopefully) would in the real world - admit where you are at and formulate a plan to get to where you need to be.

I am glad it was helpful.

Unfortunately, you are correct. It is a problem I'm working to change by modeling how it can be different.

It sounds like their screening process is not working. That was not fair to you, but at least you got the experience of that type interview. Every experience helps you build your interviewing skills.

You are welcome.

You are welcome.

I am glad it was helpful.

Things are slowly changing in that regard.

Thanks for the great tips

Yep, you are going to get bad interviewers.

You are welcome.

Yep, actually knowing what you say you know is important. And yes, you will get asked silly questions but if you can address them like you would in the real world, you can at least show off your skills as a developer even if they aren't asking good questions.

You are welcome.

You are welcome.

You are welcome.

You are welcome.

Great!

Thanks for trusting Tim to help you.

Thanks for watching

You are welcome.

You are welcome.

You are welcome.

I'm glad!

Excellent observation. You are correct - rejections should not be taken personally, even though that is really hard to do.

You are welcome.

You are welcome.

@Soy Orbison sure I didn't say you are going to use it in your daily work as you mentioned maybe you never use them, but my point is if you want to pass a coding interview for big tech companies you must know them well, because that's the way they evaluate you. We all know we're not going to reverse a linked list or invert a binary tree in our jobs, but that doesn't mean you shouldn't learn them as I said it's what it's.

You guys are making some valid but sad points. Prepping for an interview, in some situations, has little to do with the real job skills. GlassDoor web site can give valuable insights into how a company interviews, FYI. Great place to help prep you for the interview.

Thanks for sharing your valuable experience.

Thanks!

Let us know how it went, please.

@@tomthelestaff-iamtimcorey7597 Not good unfortunately

@@TheSjoerd Each interview is a learning experience. Think about what you can do better and where you need more practice. You know, for most of my jobs, I walked away from the interview thinking I blew it, but I somehow got a call back. In one interview, I fell on my face. Literally. I sat with my legs crossed and one leg went COMPLETELY numb but I was too nervous to notice. Stood up to leave and BAM. A while later, they called and I still got the job. So, you may still have a chance... 😀

@@tomthelestaff-iamtimcorey7597 yeah it is weird, I know, As an assignment the asked me to build an api and a webclient getting data from the api in a grid. I made a solution following ghe setup from Tims TimCoRetailManager and they still were not satisfied, said I was underskilled. One guy said it didn't matter as long as I fit the team and they said I did. Another guy said they really needed a pro skilled developer no matter if he fit the team or not. I know this: when you are denied the jo , they seldomly tell you the real reason. Anyway I had an offer from two other companies so its their loss :-)

@@TheSjoerd Good choice. Taking that job would have set you up for someone always pointing the finger at you and resenting you. Sadly, I have seen that argument in teams often. Looking back, I think it often was someone fearing having to step into that lead technical role themselves, so they claim "we need a real pro" to keep the pressure off themselves. Bottom line: you did well and congrats on the new job!

I really don't want to hire someone that can only memorize things, they have to be able to apply the concepts to really add value.

You are welcome.

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

Agreed.

There is truth in what you say. The question is, do you want to work for a manager that is that poor of a manager?

Good questions and some that I'll probably address in a future episode. Basically, do a good job and try to do what is right for the solution. That means not throwing every "best practice", "principle", or "design pattern" at it. If you aren't sure what is right for the situation, just keep it simple yet well done and then discuss your decisions with them. Talk through why you did or did not use a certain pattern that might normally apply, etc.

I'm a big fan of honesty. I find that if honesty burns you, it can be a blessing (you probably didn't want to work there anyway). So if you are leaving a role because the pay is poor, say that. Say it well, but be clear about it. Say "I really like where I am at, but I am not being paid what I think I'm worth. I want to provide better for my family, so I am considering a job change." Or, if you are leaving because the work environment is toxic, say that nicely. Something like "While I fit well in my current role, the work environment does not fit me well. I would like to find an environment that is healthier for me where I can thrive." Or you could put the two together. The key here is NOT to bash your previous/current employer. Remember, your prospective employer is trying to see if you fit. They are going to put themselves in your former/current boss's shoes. If you talk bad about your former/current boss, what is to stop you from doing the same to them? If you are going to leave without trying to make a difference, why wouldn't you do the same to them? Show your potential future employer that you are a good employee who is respectful and wants to succeed even in tough circumstances. Show them that you can be trusted and that you aren't going to burn them.

@@IAmTimCorey you're amazing thx again🌹

👍

Tim offers several videos covering deployment with different types of programs. - ru-vid.comsearch?query=deploy

Each interview is a learning experience that you should build on. Hopefully, you get the job and don't need any more.

I hope this is encouraging and not discouraging, but it won't be your last unsuccessful interview. I've been turned down hundreds of times, and not just at the beginning of my career. Remember that this is a bit like dating. You are looking for the right match and so are they. Just because you are a great person doesn't mean that you match up well with the person you are "interviewing". As a developer, they are trying to see if you are the right fit. That's hard to put into words, just like it is hard to put into words who would make a good partner. Keep at it. You can do it. Just do your best and don't take the rejections personally. Remember that if you and I interviewed for the same position and we were both qualified, they would probably turn you down not because you aren't qualified but because you don't have as much experience as I do. That has nothing to do with you. It has to do with the pool of candidates they were working with. You will find the right fit. Just keep working towards it.

@@IAmTimCorey hello Tim and thank you very much. I felt discouraged at first but as I analyzed everything, it got better. Now I actually feel good about that interview, because it indeed was a great experience. And now I know what I should work on.

And how often do you need to do tasks for your job without a computer? Just because an interviewer asks a silly question doesn’t mean you need to play the game. They aren’t hiring you to do math on a whiteboard. They are hiring you to write code.

Nope, no mention of it because it is falling out of favor. Plus, the benefits of doing so will only possibly benefit you in a few specific interviews. I'm trying to maximize your potential success. The answers I give here will allow you to get past some of the answers that "leetcode grinding" might help you "solve" (usually poorly).

@@IAmTimCorey Most of the known tech companies are using leetcode with no signs of slowing~ sure some "IT department" from like a bank or similar might not ask but then they're also the ones more likely to be picky of having experience in a particular framework. Prep will cover lower tier tech companies like IBM all up to the top ones like Google and it is equally useful for all since the same patterns will be relevant in all the interviews

I am sure it is.

I wouldn't say "too few jobs" - there are lots of unfilled jobs out there. The issue is definitely the number of people that apply for jobs that aren't qualified. That leads to a filtering process that can easily filter out good developers. What makes it worse is when good developers don't actually show off their skills well in their resume and portfolio. For instance, when they don't tailor their resume to the job, so there aren't many keyword matches. Or when their portfolio doesn't have anything that relates to what they will be doing.

@@IAmTimCorey You and I will have to agree to disagree on this. I think that other responses here lend credence to what I am saying. "qualified" is a tricky word since the New York Yankees professional baseball team lamented over finding a "qualified" applicant to replace Hall of Famer Derek Jeter. As others have said, companies seem to have similar standards to the Yankees in that their requirements are so high. Anyway, we can agree that you do a great job with your videos. I really appreciate them. Thanks!

It is a podcast. That's a standard intro.

Yeah, they can be really hard.

You are welcome.