I have been a coder for years. The interviewing process never gets easier because they expect you to know and have experience with the latest and greatest technologies. It is usually a soul-crushing event when you go to interview. Most of the time, the interviewers themselves do not know the answers to the questions they are asking. It's truly horrible what we have to do to secure employment.😢
Those questions i cannot even answer right away, and i am working in IT since 1991. But i would know where to search for answers, if i need it. What sort algorithm i used? Nobody cares. When i need one, i will find one. In real life its about problem solving skills, project awareness - not algorithms or rarely. And soft skills! Som etalented person are difficult to handle in real life bec of their pride.
You’re doing the right thing. I also noticed a big difference with design questions that weren’t asked at the junior level. If you already got two interviews then that’s good. Try to interview as much as you can even if you’re not interested in the company, for practice
I got one interview through an agency with an European company. Most of the questions are like those ones stated in video. I answered all of the questions, but unluckily in the end they rejected me with unclear reason, even the agency asked whether I feel the questions were too easy, but I reckoned I was overqualified.
You are a very clever young professional. I also found recording interviews invaluable. Its not just about answering questions accuratly, because answering them in a pleasant and interesting way can have a huge competative advantage. Try to sound excited about what you do! Watch for phrases that you use too repetitively as this can bore the interviewer. Try to always sound upbeat, but when you are dicussing something that is a drag, don't be afraid to acknowledge that if its not central to the job. I like to talk to interviewers like they are someone you might meet at a professional event or conference. You are both interested in the topic, but you want to impress this person with your knowledge of the topic.
Common for the interview to be of higher expectation than what is expected to perform at your job. If you answer one question well, give another question to check for breadth. Followup with a depth question, change or repeat if answer is not optimal. It is funny cause in a lot of debriefs, you compare the potential candidate with your current team and gut check if the candidate at least matches with what similar level engineers in your team is performing at. Often than not, new positions are harder to make it to the offer round than a posting that has been around for longer. The panel and HM always looking for a candidate that is exceptional and appears better than the current engineers initially.
You are doing the right thing, it always helps knowing as much as you can about the company interviewing you. Yes, know these answers back and forth, but always try to get to your added value for the company. Ask the interviewer at some point "What are the companies biggest needs that you could help with". After doing more interviews you will impress someone who is looking to grow the company. Remember, you have the same goals. Both you and the company are looking to make money.
@@jimh3595 not just that, there’s also mutability vs immutability etc. There’s actually a fair bit of stuff to consider, aside from the sheer design which obviously is also a consideration
Aside from que C# specific question (which i am no proficient in), the others i think are quite manageable. But can be tricky in the nervousness of an interview and depending on how deep the interviewer wants you to get. But it's still better than leetcode style questions
The questions in that first interview seemed pretty difficult for a backend engineer. Thing like how to debug kubernetes, availability, and scalability. This looks like questions more for a role of a platform engineer than a backend engineer. My advice is make sure that the resume you are sending out plays directly to your strengths and is specific not generalized to the position that you want otherwise you can end up with awkward quesitons outside your expertise.
Look into tech consulting companies for potential part-time gigs. Triple Crown is a good one. They source engineering support for many high profile companies. Don’t be discouraged as it is a tough market right now. Consider also this time might be a good opportunity to switch career focus, such as team leadership, product management etc. Definitely consider this if your unemployment starts to drag longer giving you the time to learn or retrain.
Lot of pitfalls in multi-threading and async/await. I would just concentrate on researching those pitfalls and the primary benefits/uses of multi-threading. Talk about what you learned when you discovered some of the pitfalls.
The first interviewer sounds like someone truly know his/her trade and try to encourage and discover potentials from candidate. They are not necessarily ghosting you, some companies are just moving much much slower than others.
Just came across this channel and wanted to leave a comment while wondering how was your search. Seeing this video is 1 month ago and you mentioned ‘hedge fund’ I believed you interviewed at a financial institution (FI) towards a Fiscal Year (FY). That is the time when FI does financial planning and budgeting. Assuming the FI did not achieve its target it may cutback and freeze hiring for the time being; So may not be due to your interview performance. Wish you the best and update us in the next video!
To be honest, most tech interviews over tested the candidates. When I was in a trading firm, I co-interviewed candidates with another tech guy. His questions made me uneasy for they are the sort of questions you get in your video but we don't really use them. But yes, at a senior level, you will need to know design patterns, in-depth knowledge or data structures and algorithms, and different tech stacks.
On the other hand, you don't expect them to give you the best possible answer. You're simply trying to see how they think, how they proceed, and whether it's compatible with your team/workflow. Even a wrong answer for the right reasons may be more acceptable than a right answer to the question for the wrong reasons. But each of these situations is highly dependent on the recruiting staff.
Multithreading and synchronization were becoming every-day topics when I was in junior position working in some kind of trading projects. But now I am in senior position and I feel very easy to tackle that kind of issue all the time.
If they treated kubernetes as a nice-to-have then great, if not they are asking too much for a regular backend dev. That's typically a concern for devops, etc.
I noticed that some companies with small software teams don't have the budget for a dedicated devops team, so they want the backend engineers to cover those as well 🫠
@@eeeuphieee And that's fair, as long as it comes with reasonable expectations and not outright demands. Otherwise they need to pony up more dollar signs.
Recording a job interview, not sure if that is even legal. At the very least, would need the consent of the interviewer. Also, interview questions for a senior developers are to judge how senior they really are. The "learning" for those questions cannot be done in a few weeks, it is mostly the experience of years working on those topics. Probably the interviewer is just asking things he knows from years of experience, he does not have a default question list from the internet.
It would depend on where you are, I would think. In general, some locations require the other persons consent regardless, while others allow you to record without consent if it is not for legal purposes.
To "ghost" someone is a very rude thing to do... That's a company I would want to keep a safe distance from ;-) By the way, may I ask, what is your favourite programming languare?
You've only done 2 interviews? You should do a lot more, you can try spamming your CV to job postings and see which one gets through I'm also still doing lots of interviews, since i spammed my CV to many job posts
When your unemployment is fresh, you concentrate on the companies you prefer, and it's only after a while (which depends on each people) that you start spamming.
just be careful when been ask a question on how to do something like what you was ask if given a chance to redesign it again fresh by yourself. the person at the end could be asking you actual issue-problem which they cant do it good enough, and want you to give "free" ans from this interview.. its more like a free loader.. i ever face this type question during the interview (not IT stuff but mech eng) before so its a real deal and not make up story... some people may not like it, some people cant care about this type of issue... its all up to you on how this matter is.
The advice you are giving is not something that you prepared for the last week or so. It doesn't matter If someone uses it. I can recall only one situation when a colleague of mine asked a question during an interview and the answer was surprisingly relevant to one of his projects. If was a DB design question. It solved an issue he didn't know he had. The person being interviewed was told about this.
Huh, no jobs in your country too? BTW which country are you from? Don't answer questions about garbage collection, threading and all, if they ask such basic for more senior experience you can assume its ghost job so say bye bye and move on.
Finally someone shares HONEST results of interview and the process! Thanks, good luck 🍀
you smart people amaze me. my brain can't even begin to contemplate what coding and developing is about. i wish you well in your search.
I have been a coder for years. The interviewing process never gets easier because they expect you to know and have experience with the latest and greatest technologies. It is usually a soul-crushing event when you go to interview. Most of the time, the interviewers themselves do not know the answers to the questions they are asking. It's truly horrible what we have to do to secure employment.😢
Those questions i cannot even answer right away, and i am working in IT since 1991. But i would know where to search for answers, if i need it. What sort algorithm i used? Nobody cares. When i need one, i will find one. In real life its about problem solving skills, project awareness - not algorithms or rarely. And soft skills! Som etalented person are difficult to handle in real life bec of their pride.
Best of luck with your search, thanks for sharing these tips this was very helpful
Glad it was helpful!😊
Best of luck in your search, and thank you for making these videos.
You’re doing the right thing. I also noticed a big difference with design questions that weren’t asked at the junior level. If you already got two interviews then that’s good. Try to interview as much as you can even if you’re not interested in the company, for practice
Euphie, those questions terrify me. You are very brave.
I got one interview through an agency with an European company. Most of the questions are like those ones stated in video. I answered all of the questions, but unluckily in the end they rejected me with unclear reason, even the agency asked whether I feel the questions were too easy, but I reckoned I was overqualified.
You are a very clever young professional. I also found recording interviews invaluable. Its not just about answering questions accuratly, because answering them in a pleasant and interesting way can have a huge competative advantage. Try to sound excited about what you do! Watch for phrases that you use too repetitively as this can bore the interviewer. Try to always sound upbeat, but when you are dicussing something that is a drag, don't be afraid to acknowledge that if its not central to the job. I like to talk to interviewers like they are someone you might meet at a professional event or conference. You are both interested in the topic, but you want to impress this person with your knowledge of the topic.
All the best. you will make it soon.
3:00 ah, I would have stumbled here
Gotta prep this just in case
Thanks !
Common for the interview to be of higher expectation than what is expected to perform at your job.
If you answer one question well, give another question to check for breadth. Followup with a depth question, change or repeat if answer is not optimal.
It is funny cause in a lot of debriefs, you compare the potential candidate with your current team and gut check if the candidate at least matches with what similar level engineers in your team is performing at.
Often than not, new positions are harder to make it to the offer round than a posting that has been around for longer. The panel and HM always looking for a candidate that is exceptional and appears better than the current engineers initially.
thanks for sharing this! 🙂
You are doing the right thing, it always helps knowing as much as you can about the company interviewing you. Yes, know these answers back and forth, but always try to get to your added value for the company. Ask the interviewer at some point "What are the companies biggest needs that you could help with". After doing more interviews you will impress someone who is looking to grow the company.
Remember, you have the same goals. Both you and the company are looking to make money.
Thanks for the advice! 😊
The struct vs class is a very nuanced one and you really need to dive into both because what you use may greatly affect performance
Stack vs heap.
@@jimh3595 not just that, there’s also mutability vs immutability etc. There’s actually a fair bit of stuff to consider, aside from the sheer design which obviously is also a consideration
@@andrearaimondi882 value types vs reference types.
@@jimh3595 "Stack vs heap" is a C/C++ answer. In C# it is way more nuanced.
Aside from que C# specific question (which i am no proficient in), the others i think are quite manageable. But can be tricky in the nervousness of an interview and depending on how deep the interviewer wants you to get.
But it's still better than leetcode style questions
The questions in that first interview seemed pretty difficult for a backend engineer. Thing like how to debug kubernetes, availability, and scalability. This looks like questions more for a role of a platform engineer than a backend engineer. My advice is make sure that the resume you are sending out plays directly to your strengths and is specific not generalized to the position that you want otherwise you can end up with awkward quesitons outside your expertise.
Look into tech consulting companies for potential part-time gigs. Triple Crown is a good one. They source engineering support for many high profile companies. Don’t be discouraged as it is a tough market right now. Consider also this time might be a good opportunity to switch career focus, such as team leadership, product management etc. Definitely consider this if your unemployment starts to drag longer giving you the time to learn or retrain.
thanks for the nice advice! 👍
Lot of pitfalls in multi-threading and async/await. I would just concentrate on researching those pitfalls and the primary benefits/uses of multi-threading. Talk about what you learned when you discovered some of the pitfalls.
The first interviewer sounds like someone truly know his/her trade and try to encourage and discover potentials from candidate. They are not necessarily ghosting you, some companies are just moving much much slower than others.
Yah I can tell that the first interviewer truly know his thing. Kinda hope that I get to join his team one day
One thing everyone needs to understand those are standard questions. Many times the interview gets their questions from the same resources.
Just came across this channel and wanted to leave a comment while wondering how was your search.
Seeing this video is 1 month ago and you mentioned ‘hedge fund’ I believed you interviewed at a financial institution (FI) towards a Fiscal Year (FY). That is the time when FI does financial planning and budgeting. Assuming the FI did not achieve its target it may cutback and freeze hiring for the time being; So may not be due to your interview performance.
Wish you the best and update us in the next video!
Thanks for sharing this with me! :)
Best of luck, thanks for sharing!
The more of these you do, the better you will get at it.
To be honest, most tech interviews over tested the candidates. When I was in a trading firm, I co-interviewed candidates with another tech guy. His questions made me uneasy for they are the sort of questions you get in your video but we don't really use them. But yes, at a senior level, you will need to know design patterns, in-depth knowledge or data structures and algorithms, and different tech stacks.
On the other hand, you don't expect them to give you the best possible answer.
You're simply trying to see how they think, how they proceed, and whether it's compatible with your team/workflow.
Even a wrong answer for the right reasons may be more acceptable than a right answer to the question for the wrong reasons.
But each of these situations is highly dependent on the recruiting staff.
Multithreading and synchronization were becoming every-day topics when I was in junior position working in some kind of trading projects. But now I am in senior position and I feel very easy to tackle that kind of issue all the time.
You are pretty and smart and still at good age = young. Some boss will hire you for sure or get self-employeed in a niche, where is more demand.
If they treated kubernetes as a nice-to-have then great, if not they are asking too much for a regular backend dev. That's typically a concern for devops, etc.
I noticed that some companies with small software teams don't have the budget for a dedicated devops team, so they want the backend engineers to cover those as well 🫠
@@eeeuphieee And that's fair, as long as it comes with reasonable expectations and not outright demands. Otherwise they need to pony up more dollar signs.
Great videos
Glad you like them!😊
Recording a job interview, not sure if that is even legal. At the very least, would need the consent of the interviewer.
Also, interview questions for a senior developers are to judge how senior they really are. The "learning" for those questions cannot be done in a few weeks, it is mostly the experience of years working on those topics. Probably the interviewer is just asking things he knows from years of experience, he does not have a default question list from the internet.
She mentioned she changed questions in video.
It would depend on where you are, I would think. In general, some locations require the other persons consent regardless, while others allow you to record without consent if it is not for legal purposes.
Maybe they are asking for free consultations rather than interviewing and are seeking a peak into competition's code development.
Ah I have heard of this before too... 😢
Got laid off this week. I feel anxious too
i know how it feels...hang in there!
im scared
To "ghost" someone is a very rude thing to do... That's a company I would want to keep a safe distance from ;-)
By the way, may I ask, what is your favourite programming languare?
Cici, impress you, total you, I hopes there going ok 🙄
it's really unpleasant to leave the "music" (this term is really inappropriate). Good luck, I'm sure it will work out.
mam where are u from
You've only done 2 interviews?
You should do a lot more, you can try spamming your CV to job postings and see which one gets through
I'm also still doing lots of interviews, since i spammed my CV to many job posts
When your unemployment is fresh, you concentrate on the companies you prefer, and it's only after a while (which depends on each people) that you start spamming.
IT is a male dominated industry, not easy to compete as female
just be careful when been ask a question on how to do something like what you was ask if given a chance to redesign it again fresh by yourself. the person at the end could be asking you actual issue-problem which they cant do it good enough, and want you to give "free" ans from this interview.. its more like a free loader.. i ever face this type question during the interview (not IT stuff but mech eng) before so its a real deal and not make up story... some people may not like it, some people cant care about this type of issue... its all up to you on how this matter is.
The advice you are giving is not something that you prepared for the last week or so. It doesn't matter If someone uses it. I can recall only one situation when a colleague of mine asked a question during an interview and the answer was surprisingly relevant to one of his projects. If was a DB design question. It solved an issue he didn't know he had. The person being interviewed was told about this.
Sad
even when you do get the next job, you will just get laid off again, at some point. working in tech is not a ride i want to be on.
Huh, no jobs in your country too? BTW which country are you from? Don't answer questions about garbage collection, threading and all, if they ask such basic for more senior experience you can assume its ghost job so say bye bye and move on.
she sounds singaporean