This video shouldn't be viewed by CD or developers. Today, I want to share some personal interview tips on how to do well in developer interviews. I will explain how to handle questions that I don't know the answers to and still appear competent. 

I've passed technical interviews and coding interviews, but often, I find myself struggling in technical interviews. It can be difficult to understand the underlying principles. If you are unsure about something, it’s okay to participate actively in the conversation and share what you know. 

In my case, when I receive a question that I am not familiar with, I typically respond by saying, I’m not really sure about that. However, I try to relate it to something similar that I do know. For example, I might say, Is it something like this? I understand this part, but is this related to what the interviewer is asking?

I may not know much about this stock, but I do have knowledge in a similar concept that I can demonstrate. That said, I don't need to explain things I don't know about, like the features of the vehicle. However, when it comes to my experiences, the interviewer might say that I shouldn’t do that. In the United States, I am not really that style. In fact, even if we fail an interview, I feel that it’s important to reflect on the time spent preparing for the mock interview. It’s not like I can just dismiss it and say I got it wrong. When I express that, I might ask, Can I ask what I did wrong? I tend to ask questions like this. Some people, however, don’t engage in this manner; there are those who might take a more formal approach.

Most of the satisfied individuals explain that the second point is the concept of being open-minded. First, I need to show that I have an open mind and am ready to accept what I don't know. This will help me to receive information better in the future. This place is incredibly diverse, and I think about why I should hold onto this opportunity for the next time as well. When I ask questions that I don't know, if I say something like, I don't know, it can lead to a more engaging conversation with the interviewer, and they may ask further questions. Many interviewers ask very sharp questions, particularly regarding areas I may not be familiar with or about the questions I have asked. There are instances where they might rephrase sharp questions. I need to think about how to respond to such questions.

First of all, I want to say that the other person's question is a very good question. I haven't thought about it in a way that leads to regret, but I believe that. The flow of the conversation can naturally lead to this. Although right now, the townhouse question is at its peak, and I'm just reflecting on it, you asked a very sharp and good question. This makes me realize that such questions are rare opportunities. I hadn't thought about it before, but it’s a great question.

So, in the case of Kim Se-ah, it seems like she had a style of responding by adding something like, Oh, in this way. Even if there was a little dealing at school, just looking at the attitudes of the writers, my friend saw a very next-level aspect, but despite that, there was a bit of a mindset to learn. What kind of attitude I am showing is a bit unclear. Towards the end, the writers tend to ask questions. In our company, we don’t have any formal studies; we definitely do it. Oh, the questions are really important. Right now, they are asking this question. This is something that doesn’t take away from the energy. From the interviewee's perspective, I really care about the impression. The good thing about this is that I usually try to ask questions. Among the questions I've asked, I...

I wasn't able to give a proper answer earlier, so can you explain the question I asked during the interview? I often ask about the brand and what it represents. This is because I really want to avoid making mistakes in my next interview. I tend to ask questions about the company as well. For example, if I were to join, what would the team's dynamics be like? What are the backgrounds of the developers? What concept would we start with? I'm really curious about the position at your company, and I want to show my interest through these questions.

Also, after the interview, at the right moment when I'm about to leave, I think it's very nice to compliment the interviewers. This is a personal technique of mine. After going through several interviews, I've realized that...

I once had an interview with a developer who had 14 years of experience in the field. Even though it lasted only two minutes, they asked very sharp questions. No matter how well I answered, they would point out the ambiguities and insisted that I choose my words carefully. Throughout that interview, I felt like I was learning. I thought to myself, Why not learn from this experienced developer and gain some insights into their skills and know-how? I ended up asking a lot of questions, and it felt almost like a discussion rather than a typical interview. 

I shared my experiences as a junior developer, noting that opportunities to discuss such depth are rare. I realized how much knowledge I was gaining from this person. It was an enlightening interview for me. Even though I didn’t succeed in getting the position, I expressed my gratitude for the insights I received and thanked them before leaving.

This is where I truly express my feelings. I've been through a lot, and now I want to share. Despite there being many candidates for the Eggmaster position, I received an offer from the company. When I was preparing for the next step, the CEO shared some insights with me. My dad also mentioned that the developers were very impressive, and they were particularly fond of the LG team. He told me that they are really great. He said they would definitely choose someone like me. 

During the interview, I felt a bit nervous, but I think it’s important to show emotion rather than just acting. The interviewers provided me with many good responses, and I am grateful for that. I believe cultivating gratitude is essential. Overall, the interview team was not just a myth; it was a genuine experience, and I hope to succeed.

In my case, the first interview didn't go well. However, during the second and third interviews, I learned from the first experience, which helped me improve. The second interview built on that learning, and the third one was also a result of that process. It's all a journey for you to gain something good, so there's no need to feel discouraged if things don't go perfectly. Instead, if you feel like you didn't learn anything from the interview, just keep trying and remember that it’s all part of the process. I hope my experiences can be helpful to you all. In the next session, I will share more.

기술면접 모르는 질문 받았을때 대처법 | 시니어 개발자 분들은 보지 마세요 | 신입개발자, 주니어 개발자 면접 꿀팁

누구보다 코딩을 쉽게 알려주는 채널입니다!
코딩배우고싶으면 닥치고 따라하자 
그외에 코딩관련 지식들도 알려드려요! 

코딩알려주는 누나 강의 듣는곳
https://codingnoona.thinkific.com/
뇌를 살찌우러 올래?

누나 인스타 뭐야? 1008_shine


기술면접 모르는 질문 받았을때 대처법 | 시니어 개발자 분들은 보지 마세요 | 신입개발자, 주니어 개발자 면접 꿀팁

기술면접 모르는 질문 받았을때 대처법 | 시니어 개발자 분들은 보지 마세요 | 신입개발자, 주니어 개발자 면접 꿀팁

스크립트