Junior Developer Interview Guide | Kasra Khosravi | Skillshare

Playback Speed


  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Junior Developer Interview Guide

teacher avatar Kasra Khosravi, Software Developer

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

8 Lessons (45m)
    • 1. Welcome

      0:46
    • 2. Get-To-Know Meeting

      4:53
    • 3. Technical Interview

      7:05
    • 4. Technical Interview: Exercise

      11:46
    • 5. Coding Challenge

      5:01
    • 6. Coding Challenge: Exercise

      8:46
    • 7. Coding Challenge Review

      6:14
    • 8. Conclusion

      0:49
  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.

13

Students

--

Projects

About This Class

Welcome to the “Junior Developer Interview Guide” Course.


My name is Kasra and I am a software developer that has been a junior developer in the past. I completely understand that software interviews can be a bit scary, so my hope is to give you clear ideas about the interview process and offer you practical advice on how to do well at each step.


This course can be very helpful for you to get an overview of all the common interview steps that companies go through to hire a developer. Join me in this journey.

Meet Your Teacher

Teacher Profile Image

Kasra Khosravi

Software Developer

Teacher

A software developer with a passion for maintainability and scalability design patterns.

See full profile

Class Ratings

Expectations Met?
  • Exceeded!
    0%
  • Yes
    0%
  • Somewhat
    0%
  • Not really
    0%
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.

Transcripts

1. Welcome: hi and welcome to the junior developer interview guy. Of course, my name is Castro, and I am a software developer that has been in junior developer in the past. I completely understand that suffer interviews can be a bit scary sometimes. So my hope is to give you clear ideas about the interview process on offer you practical advice, how to do well at each step. This course can be very helpful for you to get an overview off all the common interview steps that companies go through toe. Hire a developer. Join me in this journey. In the next lecture, people get familiar with the first interview, which you'll be get to know or initial meeting. 2. Get-To-Know Meeting: in this lecture, we discussed the first step in your developer interview process, which is they get to know or initial meeting. Usually, the company arranges an initial meeting to get to know you and offer you a chance to get to know them. Is meeting can happen with telephone online or in their own office. The best option is if you are invited to their office for this meeting, since you will have a chance to see behind the scenes, maybe meet the other team members and get a glimpse behind the company's culture, things like, does the company have a formal or casual atmosphere? Or how good is their coffee? There are things you can do to better prepare for this meeting. First, do your homework. It is common that the company will check your online presence, such as social media or personal sites. Have an initial impression off you. There is no reason why you shouldn't do something similar. Check the website and social media and pay attention to the warding off their services on description off their team. Are they explicitly saying what they value in their future team members or order clues about this in block posts and articles published by them. Make sure to write them down and have it in the back of your mind when entering the first in area. The point here is not to memorize a bunch of key wars and just repeat them in the meeting to make a good impression. You can use it intelligently to your advantage, but this has to be genuine and come from a good place. But once you are able to show the value they care about or also on your topless, they will see you in a more positive way. Second, learn from past candidates If you have been approached by a more well known company chances , or you can find past experiences off other candidates published on the Internet, there are excellent sources like lengthen or glass store, where you can read the feedback from other candidates for possibly the same position you want to apply for. This is a great chance for you to see how your future interview meeting will look like. For example, a certain company might have a tendency to do algorithmic based white board in areas. This enables you to focus more on those objects on maybe practice that type of interview with a friend. So what is the main purpose off the get to know? Meeting this meeting is not very difficult. Comfort to the other meetings on is mostly supposed to be a conversation. They might have already checked your background and previous technical competence. So in this meeting they are trying to see if your background is a good match for their type of work on culture. It is later in the interview process, where they give you more concrete tests to check your true technical at personality skills . The purpose off this meeting for the recruiter is to get the initial signs. If if you can be a good match for their team and work well with others, if you can truly care about the technology and coding and can grow as a developer on person , if you have trace a problem solving and in general being smart, and if you can communicate your points of view easily off course, they are not going to ask you these questions directly, so they will do their best to ask approx questions that get them toe Answer they're looking for in a similar way So in this case, they might ask You tell us about the time when you had to solve a problem alone or in a group. How did it go? Tell us how you stay up to date with the new technologies and trends, or tell us about a cool project that you have worked on before. Finally, tell us the main reason why you chose to apply for this position and questions like that. So if you have done your homework correctly before, you will be able to answer these questions nicely by linking your own background. They think they're looking for on also creative things that come to your mind of all being interviewed. Remember that you can practice to become better at interviews, but nothing replaces a genuine and honest approaching. Answering interview questions be friendly, bi curious and be confident that things would be under the right track for you. In the next lecture, people discussed the next interview in the process, which is a technical or white board in area 3. Technical Interview: in this lecture, we are going to talk about technical or white for interview. Keep in mind that this meeting can happen sooner or later in the process, but you mostly find it as part of most developer position interviews. So what is the purpose off this meeting? There's no doubt this meeting is a bit more stressful than others. A lot of people believe that developer needs toe have the ability to discuss a problem on a possible solution. At a high level that is very white port or even a piece of paper comes in. But you only drawing and mapping your thoughts. Using figures, diagrams and shapes. You might not necessarily need to go into little details off implementation, but rather discuss the steps he would take to solve a particular problem. It is common to ask two types of questions in these interviews. First, our design or architectural based questions, no matter how skilled, your it is always a good sign. If developers have the ability to imagine a bigger picture design off, the system they're working on is in deaf teams. It is usually the job off more senior developers to help design the architectural off the applications on general processes on pipelines. However, it is expected for everyone on the team to have an impact on these decisions. The more you educate yourself in the years towards becoming a senior developer, the key here your answer will be to these types of questions. So, in a nutshell, they want to see you try to think about them. You can't get your knowledge for these types of questions from all your previous projects, even small or by reading best practices on architectural based articles from more experienced developers. Example. Questions for this type can be. How would you display a list off items, but you're lying on an external source like a P I. How would you describe the state of is designed for two tables that should reference each other? Or if you wanted to build a and e commerce site, how would you go about designing its architecture? Your answer can be not 100% correct or optimal, but they want to see you. Troy. They want to see you, or reading or thinking about these types of questions on. They might be looking for keyboard in your answer to see the bigger picture. For example, you might not be completely familiar with how to set up different parts of an e commerce platform. But if you mentioned that you would consider suppression concerns on Bill different layers off functionality for better maintain ability and to stability, that would be a very good sign for them. The second type of questions they might ask you or algorithmic based questions. These questions are narrower and more concrete and half the aim of testing your general computer science knowledge as well as your problem solving skills. The typical questions for this type can be How would you reverse the string? Or how would you count the number of words in a text? Or how which you find the highest or lowest number in an area of numbers and Stephen or types of questions? There are things to remember in passing this test. First, remember that staying home actively thinking about the problem and hints off solution that you might have in your head or key for passing this test before quickly trying to answer the questions. Take a moment to think about the problem and then start writing problem keyboards as bullet points on the white board. Second, read the problem out loud and do not be afraid to ask if any part of the problem does not make sense to you. They can try to expand better, which gives you more time to think or get more clues. Asking questions in this meeting is usually never the wrong thing to do. For example, know that these questions can be simpler if their criteria are clarified a bit better. If you do not know the type of input data you're getting, asked them for clarification, for example, they might tell you that you're provided data only comes in a reform. Well, that's made things easier. Third, start drawing and using text to show them your real thinking. I do not feel the rush to write code on the white board or on your computer. At this point, it is much more valuable for developer to get a clear idea about a problem before jumping into solution implementation. That is what we are practicing here. It's not wrong at all to us for pre. It's off off thinking time so you can mull it over. But if you feel stuck, it's best to communicate that and ask them for hints. They're always happy to give it to you and without taking its negatively. But remember to use their hands. Otherwise, it might seem like you are not a good listener when asking for advice. And finally, after drawing some diagrams and shapes for defining the problem, they come to writing some code. Your coat can be in pseudo court, which is a simplified programming language for describing coat design. If you can write the solution for the problem using a program a language you prefer, like JavaScript or python, this will be a very good sign. It can be a bit harder to write those types of algorithmic based codes, since we use utility functions to achieve them in our day to day work. But a string parts are library instead of writing our own. But practicing and knowing these shows that you have a firm grasp on the basic concepts of coding someone it twice for this part would be practice the fundamentals like conditional programming S Inc data fetches or four. Look on data my mapping regularly. I'm gonna be honest with you. I have never had a taking our interview, which I felt I have done 100% perfect. But most of the time I got to call back for the next interview by following the rules be described in this lecture. There are a lot of unknowns, and the recruiters are even ever off the complexity off some of the problems. But just want to test your problem solving skills and see how calm and focus you can be in those situations. So a big part off your success in this meeting will be dependent on your mind set on stress management skills. But another important part is to do enough practice on similar types of interview questions that make you feel comfortable with the format, even then approved approach by unknown topics. In the next lecture, Evil practice a sample technical interview question together. 4. Technical Interview: Exercise: in this lecture, we will work on a sample technical interview question together. So imagine you are in the interview and interviewer ask you what can you tell me about take a mapping? How would you build your own data mapper function? So it's a very comment has for developers to map set off data and transforming 21. This is where the core concepts like four loop or forage, comes in. Is iterating over a data on returning something here. So before writing any code, you can start to wrong some diagrams to tell them that you understand the core of the concept. With this diagram, you show them that you understand getting a data set in this case it is, or the great circles you do some sort of transformation on them on. Then get the new data, which are the new circles here, each off the secrets here go through a mapper function in the middle. Something happens to them in this case they become funky and then we get the new one. This diagram also shows that you understand every element in the original data is mapped to anyone grey to orange, so with a reverse mapper function we can get from the new data to the original one. In the next step, you can write some sort of surgical's, for example. Look at the illustration And don't worry. You don't have to use emojis in this example. We're using a mapping process with the declarative approach. So if you're not familiar with that, is that we or not? Do you get step by step approach? We are telling the program what we want in the end, not how we wanted to do it. So we just provide the array off in this case a potato, corn and an egg to the mapper function. And then we are also providing the transformation function, which is in this case, is cook. We're not. We don't know what is inside in that transformation function. In that case, we are running this mapper function, and in the end we get the new R A, which is an array of french fries, popcorn and omelet. Obviously, this code will not work, but writing a simplified version off the functionality you want to achieve will show your strength off conceptualizing a solution without getting into the syntax. As a final step you can actually write a mapper function using real coat. Let's do that together. So I am gonna use code sandbox. But obviously, in the interview you can use any editor and maybe use a console to see that if your solution is gonna work, so be it started actually blind creating a new viable called items. It's gonna be simple. We're just gonna call it 1234 or five days and there are five items and that's gonna be our or regional data we're gonna use, Um, so if I want to first show that we understand data mapping functions, so we're just going to use a simple for loop and we're gonna initialize it, it's going to run until the length off the origin Ilary at every situation. We want to increase it. So if we're actually doing anything here, just take a moment and know what you want to do. So we want to do some sort of transformation on the original array, which in this case, is items I'm gonna actually before writing the well, I'm just gonna think about what I want to achieve. So I want to maybe double every item in the original one. So in the end, I would get the 2468 and claim is that going over all of this, um array and then doubling each one off them. So here it means that we might need transformation function. I'm just gonna call the dysfunction double The's function is going to get on by item, and the item is gonna be doubled. So some sort, we are going to use that transformation function in the body off the four loop. But we also need to create a new array, which is gonna be returned in the end. So we're just gonna call this may be a result. So in this case, we are gonna push it. We're going to use the push method on the array and then at every situation we want to double or do the transformation function in this case, double at the items that were getting. So at every point, we are gonna have an index. So, for example, in the first, attrition is going to be 0123 at every point. We get that right and we double it, and then we push it to their or new all right. So if you want to kind off check if our results work, maybe you can just consul like this, and then we can just say rig salt. So as you can see here, we are getting what we want to do. But in this case, the job off in extracting, initializing and pushing the result with an array is on us. This is kind of an example off imperative programming. We are telling the computer how we want to achieve something, like using a step by step process. But maybe you actually can improve it a tiny bit. So we're not gonna do index tracking. But maybe we are going to use a method on the ray called forage. So on each one off there by Thames on the original rate, Ricana used for itch and then get each one off them. And then the Arkan off doing something similar, I'm gonna actually improve it. That beats. I'm just don't know. Call it new, valuable. And then each often your items find getting I'm just gonna double them, save them in this variable, and then for all of them, are just gonna push it to their results. So just As you can see, we are getting the same results. We just, like, don't have to do all the index tracking like the Ford. So with this approach, you can just show the recruiter that you understand how you are mapping soft. You can actually make this much, much simpler, boy, using a mapper built in native map function. So we're just gonna even don't initialize anything, just gonna call it results. And we're just going to say bye attempts. There was no way. It's native mapper method. So it goes over the array, it's masses one off them on. It gets each one off those items and do something with it. So in this case, you can see that it can be. Actually, something like this has also for better clarity. So we're getting the same kind of result Now we come to the next step, which is we want you to write our own mapping function so we still have the same data set on. We still want to double each one off them, but we're not going to rely on these tools, so we are actually able to use the for loop, but in a different way if you want to build our own mapper function so we can actually go ahead and call dysfunction that we want to build, maybe them map loop because it's a mapper function that uses loop. And these function is gonna have two parameters to arguments were going to get a transformation function on also, until right and we're gonna do something with it. So just gonna create the function here. Um, and in the initial step, we want to maybe Cole valuable cold, the map array. Maybe that is going to do something similar. We just want you gets the end result as a new array. And then we are gonna again use the for loop. So be initialize it. Like before and in dysfunction. We are getting the pantry called direct. So we're just going to say until the end off the length off that array. So these four room is initialized, and then we are going to create a new valuable here on in this variable. We are gonna again do something personal that we did before. So we are gonna get each one off those items and then double them and also like apply their function transformation function, but in this case, it's not gonna be double because we have passed the transformation function to the map. You. So we have to do something like this. We need to say that apply the transformation function on this index off the array that we pass originally. So that's gonna be so that's the situation is gonna be each one off the items that the transformation function is applied to it. And then after we get that transformation, we're going to just push it to the end result, Matt. And then in the end, when that kind of A for loop has finished, it means that it has run out off the length off the very array that you passed it. We're going up. Return that the rate. So, actually, let's go ahead and test this. So we're just gonna council log this and then we're just gonna say map loop, which is the name of our function. The first parameter is the transformation function and have it already is the double function on the 2nd 1 is the direct. So as you can see, we got the same result. So these kind of process shows the recruiter that you understand the concept, you can work your way through finding a solution, and that's always a very good sign for them. In the next lecture, we will learn about the next step in the interviewing process, which is the coding challenge. 5. Coding Challenge: sure if you are going to talk about coding challenge. This is a very common step in junior developer interviews. This step usually comes before or after the technical interview and can't be done mainly in two forms. In the first form, the recruiter sends you a description off the coding challenge via email or other means and ask you to solve it on your own from home. With this approach, they usually tell you how long they expect the coding challenge will take to be solved. But most of the time there is no hard limit on how much time you can actually spend on it, especially if you want to go the extra mile boy doing some extra improvements to the original spec. Another strategy for the recruiter will be to have the coding challenge in the presence off some other developers in their own office. There is a bit off more pressure on you as a candidate, since you're kind of expected to think on this sport and come up with a solution for recording challenge, but came to find that most off the recruiters outer mostly care about how you approach solving the problem rather than your final solution. No matter. Rich format decoding challenge Comes In There are few things to keep in mind for making a bigger impression on the recruitment team. First, try to host your final work on a code repository like Get help. Nowadays, most off the deaf teams are relying on gets for managing their code base. No matter like how skilled your it is not very hard to get familiar with the basics off gets and try to kind of make a repository one of your get hop account and push her coat there. Also adding a nice read me fall that describes what you have done for sewing. This cooling challenge is always nice. Also do your best to have clear separate comet messages Thestrals that you were able to break down according Challenge task into a smaller ones that always shows professionalism and make reviewing your work much easier, especially if you were asked to solve the coding challenge from home. Second, it's always a good sign for a developer to write test cases for their code. It shows that they care about the maintainable tea after coat, which could make the life of other developers on the team easier. Obviously, testing comes in many different flavors, like integration tests, E to eight hours or unit tests here, I would argue that's writing individual unit has for the core functionalities off the coding challenge is the best approach. Third, do not be afraid to go the extra mile, but also do your best not to get too sidetracked as ball. Their recruitment team would appreciate it if you thought outside, off the box on did some sort of improvement with origins. Back off the coding challenge they presented to you. For example, they might have asked you to build a simple to do list, but you could go the extra mile on adding some nice icons, nice phones and spent a bit of time styling and for a more appealing look. But the catcher is that the core off the coding challenge should be the priority on the extra Improvements should always come second. This is how you're going to plan your task as a junior developer anyway, so better be prepared for it from Day one fourth. Do your study by checking or asking for their text back and try to use some off their tools insulting your coding challenge. For example, they might be using some sort off a type checking to, like flow or typescript. Try to use one of those in your coat as well. Not only this will make you familiar with how they are solving their problems, but we'll have a nice impact on their evaluation off you, since there are more familiar with the tools they use on a regular day to day basis. Having said that, adding the tools you are also familiar with into the mix is also a very good idea and finally do your best to have a clean code structure. This means that it's much more readable to separate different ports off the functionality into separate falls rather than having everything glued together in a single file. Also at comments to part of the code that are not very easy to understand, to show that you care about other developers being able to pick up your logic in the coat much easier. In the next lecture Fever review a simple coding challenge together 6. Coding Challenge: Exercise: lecture, we will walk through a simple coding challenge. Exercise together for the coding challenge exercise. I want to show you the coding challenge I received for my very first junior dollar per position Before getting this position. I had some personal experience with coding through internships on personal projects. But this was my first entry into professional software developer position. The coding challenge spec I got from the city or waas. Something like this. So he mentioned that I checked your guitar profile. I see that even though you have some angler projects that are not any projects that show your react skills, So at this point I had some experience with angular and if you don't know, angular is a your library. It was their famous by thunder, but at the same time react another. Your library was getting more famous in the community, so I started using that more did some courses on it, did some minimal projects on it. I didn't have any project on my guitar profile, so he mentioned that I want you to fix that toe, have more react projects on your guitar performed. I'd like you to set up a react project on your get up to demo, a loading image card. The component should take in on image. Your l on display a placeholder until the image is loaded and ready to be displayed. So it's gonna talking about using some sort of a p I to get the image data on into the image gallery component. Feel for it to a structure, the component, the props and the silent however you like. But if you need additional guidance, feel free to ask. I'd recommend you use storybook for the development and testing. Once you're done, push it to your get hop on, let me know so I can take a look. I will give you a witch to work on it, but don't worry about spending too much time on it. Feel free to send it early. If you have any questions or concerns, you can always reach me by email. Half one. So this was very straightforward task. I got police break it down to pieces, so first it shows that the recruiters check your public profiles like get help, so try to start one. If you already do not have it, it's a perfect place to showcase your previous projects, however small they are. Even if you have one project, make sure to have something there. The technical challenge was to build an image gallery that is supported by on a P I. This task was specific enough. That kind of got me going, but it was also a bit open ended, so I could kind of at my own creativity into the mix. The city also recommended to for me to use in the project in this case storybook. So it's the Esterbrook is a very nice tool to test your react components in isolation. But if the recruiter do not send you such information, make sure to ask for it on the final point. Is the timing off the task? I was given one week to solve this, but I managed to finish it in two days. My final solution was not 100% perfect, but it was completely working. It had also some extra improvements to the original spec as well. They were very place with the final work, the timing on how I approached this task, obviously, as a junior developer, there will be flaws in your coding challenge. But as long as you can justify them correctly, things would be on the right track. Now let's check the coding challenge solution together just a big here. We are not going to go into too much detail here and rather look at the set up off the solution. If you are interested in exploring this coding challenge further, there will be a link into the get hop repository in the lecture notes. So do you remember our check lists for the coding challenge from the previous lecture? The first thing is, we want to host our coding challenge in a get hop repository. And so we how nice also read me fight here. That kind of explains what we have. Don't be discarding challenge, so there's kind of a description about what we have gone, and we're also explaining which tools we have you. So in this case, we are telling that we have used react starter kids to kind of bootstrap the reactor application and also the or using shit. So which is enables you to fake a P I instead of building an actual a p I sever, which is perfect for small coding challenges like this. They're also using react as a your library right router for managing the routes in application. Redox for managing the state Start components for managing this soils. Pre select is an Adam to for Redox for selecting parts of the state. It's very useful and access as a http client. So it kind of explains what tools we have done on used here. We're also explaining how they can actually set up Theis code repository. So if they actually clone this repository in their own computer and based on their operating system, run these commands, they have you been able to run our solution locally and check it for themselves? The second thing is that we have separated our main functionalities into separate components, as we mentioned in the previous lecture. If this kind of makes reviewing your work, much easier also is the primary way. Many deaf teams arranged their co pays. So here, for example, we have divided our components into a single directory. All of the components that are gonna be used or here, and these are mostly representation off the your application. And there's not much logic here, mostly presentation stuff. But with the containers, most off the logic is in these containers, meaning that fetching the data or getting data from anywhere else all you do is to manage them in the containers. We have also services, for example, making some AP on request to some external services as well, so that is very useful. Our styles are separated into its own directory, and then we have also a bunch of you tills that could be used in other parts of the goat. So you want to kind of separate them into their own director. I also asked the city, Oh, what technology is that use? He mentioned that they are mainly using react on Redox for managing their front and work. So I made sure to use those two tools. Primary. Also, since this was mainly a front man task, I made sure to add a proper your eye test using storybook. In this way, I could have tested my singular components in isolation. For example, you can see how it looks. I built this kind of singular car components that kind of made the gallery, Um, but if you want to test these kind of components in isolation and make sure that the styling on and the prophet enduring everything works. That is the best way to approach it. You want to test it in isolation. I had a lot of fun working on this coding challenge back then, and also I learned new things about how to structure a simple front and project, and in the end, the city or liked my coding challenge Solution on offered me a position in his company. But usually companies bring you for another meeting, which is called the Coding Challenge Review. In the next lecture, we learn what this meeting is about, on how you can manage it. 7. Coding Challenge Review: in this lecture, we are going to talk about the coating Challenge Review meeting. Before diving in, I wanted to mention a very important point. All junior developers who are watching this course, especially if you have done a coding challenge for a developer position before, got rejected. Somehow, at this point in your carrier, you might have done few personal or freelance projects. Or, if you were lucky, you had the opportunity to do an internship in a sort of or big company to develop your skills. No matter. Various stand Today, the coating challenge can be a bit near breaking for a junior developer, especially if you are asked to build a complicated project in a limited time. It is true that some companies value super smart developers. I would argue that the recruiters in those companies have ever taking our background or simply value Google based interviews, which are famous for their difficulty. Not everybody is similar and work on the same pace, so it is foolish to expect that everybody can solve problems like very smart developers. You have your own pace when it comes to solving problems. So if you approach a company that presented to you according challenge with this character . Six. First, do your best to solve it in the best possible way. But do not get this courage if the feedback you goes from them is not what you expected, even after a rejection, trying to solve the coding challenge by your own and added to your own portfolio. If you treat the coding challenge mostly as a learning experience, you will never be disappointed in the end result. So what is the coding Challenge review meeting about? It is common for companies to call you for this meeting to discuss your approach in solving your calling challenge. At this point, the recruitment team have checked your solution either manually by some off their own developers or having some sort of automatic check that run your coat again. Some pretty find us either way. If you were called in for a coding challenge review, it means that your solution past a certain level of quality and now they want to discuss its details with you. One thing you need to remember is that the companies receive I feel very good or very bad coding challenge solutions, but they receive a lot off average months. If the recruiters behind the company are smart enough, they know that it's not practical to only hire people with very good solutions. A lot of times later to become rock for developers deliver an average calling solution. So at this point, it is the job. Evaluate your work as well as your work personality, to see if they can bring on board and make you a good investment for the future of the company. So let's break down what they are looking for. First, they're doing a code review assessment. What The recruiters have somehow assess you on the taking apart when you did the technical interview and coding challenge. So this meeting is their chance to test your general knowledge about coding. They might ask full up questions about the architectural decisions or concepts behind your solution. They want to see if you followed any code best practices or half thought off any scenario that they did not mention in the challenge itself. This is your time to give them enough clarification about the technical decision you made in your solution. One common approach is the senior developers on the team try to make you think about another aspect off the coding challenge to see how you might react to unknown or difficult problems. For example, you might have been asked to use an A p r to fade some later on choice on a page. But somebody might ask you if you have thought about cashing JP responses so you do not have to make unnecessary a pair calls. If you do not have a clear answer for those kind of questions, it is critical to stake home and turn it into a conversation so you can show you're way off discussing an unknown issue with the team, even though you might not have 100% off the final answer. Second thing they're doing is they're doing working percent of the assessment. Harding, a developer, is expensive in many parts off the work, so they want to make sure they have chosen the right candidate for the job. There are few things you can do to show them you are the candidate they were looking for. First embraced the feedback they give you. It is never a good sign to get defensive about your way of coding or your ideas. This is the perfect learning opportunity for you, especially if you're a junior developer, to try to listen yearly on, respond positively to their feedback. Second, show that you are a good team player on include everybody into the conversation. Show them a glimpse of how you can be their future team mate by practicing pair programming and live code debugging. Do not forget to ask deeper questions about the subject that come up in the discussion. And in the end, try to show your unique personality traits or what makes you you discuss your hobbies, interests and passions in a realistic way. This makes you seem as a more competent candidate if done right and most importantly, do not forget that small and show them how awesome your and how great it would be if they have you as a teammate. 8. Conclusion: on, we reached the final lecture. If the interviews that you have passed until this point have been satisfactory, you will most likely be invited for a salary negotiation on offer anything. And in that case, I have to say big Congress relations. However, if you did not find luck in your first right, never ever give up. Learn whatever is there to be learned on aimed for the next one. You will for sure find a success we're looking for. Thank you very much for joining me on this course. I hope the advice you got here will be useful to you and help you land your dream. Some for level upper position. I've issued the best off, like in a terrier life as a software developer.