Senior Software Engineer Mock Technical Interview (Coding/Algorithms in JavaScript)
HTML-код
- Опубликовано: 21 ноя 2021
- 🎉 Join Discord - / discord
🐦 Follow On Twitter - / thedonofcode
🤝 Get Help From Me - calendly.com/donthedeveloper
❤️ Become A Member - ruclips.net/user/donthedevelop...
-
Apply to my official frontend mentorship program:
forms.gle/Y9zuGxzVZe154uSz8
Disclaimer: The following may contain product affiliate links. I may receive a commission if you make a purchase after clicking on one of these links. Also, I will only provide affiliate links for apps that I've used and highly recommend.
My #1 recommended FRONTEND course:
scrimba.com/?ref=donthedeveloper
My #1 recommended BACKEND course:
boot.dev?via=donthedeveloper
Want to come onto my podcast and ask me a few questions? Just fill out this form: forms.gle/esQMbaRjQt9SkD1XA
My favorite todo app (Todoist): get.todoist.io/lbibntzmg4yg-H
---------------------------------------------------
Many of you wanted to see what a senior technical interview looked like for software engineers. You asked, and thanks to Sophie and Dan, you shall have. Here's what an algorithm/coding portion of a senior software engineer interview can look like. I love how Sophie progressed the problem until Dan was truly challenged. How you handle that moment in the interview speaks volumes about your character and how you'll most likely handle future challenges. Enjoy!
Host (Don Hansen):
Linkedin - / donthedeveloper
Interviewer (Sophie Novati):
Linkedin - / sophienovati
Website - formation.dev
Interviewee (Dan Cortes):
Linkedin - / dan-cortes-8954b345
Website - dancortes.dev
These interviews are fantastic. Props to Sophie and especially Dan for exposing themselves like this for our benefit. Seeing Dan struggle with understanding what she was going for was really uplifting after seeing the other interview he did as an interviewer.
Thanks a bunch!
Yeah props to both of them for being willing to do this on camera where it can be even more nerve-racking.
@@DonTheDeveloper hey Don, could I participate in such an interview? Seems like a ton of fun. How could we set something up if you're open to it? Kind regards mate
Thanks Gabriel! We're glad it's helpful to get a peak into realistic interviews. We also always suggest to practice interviews from both directions, because you learn a lot giving interviews to others as well.
Incredible content, I was amazed by how human it felt, making mistakes and not knowing what to do at some point is something that many of us try to avoid, but Sophie clearly pointed out that it can totally happen, and the important thing is how you deal with it rather than trying to avoid it. I'm not looking for a job right now, however, this video gave me some helpful insights about how I can improve my performance in my current work, things like asking as many questions about the problem, thinking of edge cases, and most importantly to don't rush into coding without a well planned and designed solution. Great video !!!
This was a fantastic interview! I have seen many interviews on RUclips but almost none covers the deep recruiter feedback that Sophie delivered. It not only helped Dan, but also helped me when I am set to interview for a company. It is just amazing to get the rich feedback and get to see what things to avoid in an interview. Thanks and Really helpful!
This is very real, not some RUclips interview drama, thank you!
One thing I don't miss is these type of tests. I now, refuse to waste my time doing them. Every one needs to till they gain experience and as such build a portfolio. First issue is spending an hour or more on these fake tests before even talking to someone about the job, if you are a fit, how the team operates, etc. Most of those of use who have say more then 5 verifiable years pf experience for the most part and if your good, refuse jobs weekly. I had to delete and/or make repos and social media private just from spam.
Funny part about this example is in the last 10 years I have yet to see, and I run more in the VUEJS circles, any actual live code like what was in the interview. I mean setting up classes etc. and not just one lining or exporting a function type of mixin.
When I interview junior developers to add to my team, biggest think I look for is passion and the ability to look it up/figure it out. Almost all the people I have had to let go would ask the same question repeatedly and I don't have time to teach someone how to book mark or screen shot a section of the documents because you can't remember "npm run watch" and "npm run dev".
This guy is a genius and I recommend all to learn from his people skills as well as his approach to the code questions. Notice how in the first question he was told to use setup(), but because He didnt understand its purpose (I also dont) and didnt want to get stuck up on it he found a build around. CHEEKY!! Its all about adapting
Sophie is the best - awesome feedback post-interview.
Great interview, I learned a lot with what questions to ask, and more on how to approach problems like this.
Special thanks to Don, Dan and Sophie for this spectacular mock interview. It definitely gave me an insight of how tech interview will be and the atmosphere is so profound and palpable even though I am sitting just in front of a computer screen! Sophie is so professional as an interviewer and I really appreciate her professionalism.
major kudos for you guys putting yourself out there for our benefit. I learned a lot, thank you
I’ve always been afraid of the interview process and as a result always set it aside but 20mins in and I’m blown away. The thing that has really hit home so far is the importance of communicating your thought process. Sure he’s a brilliant programmer but he isn’t afraid to say he doesn’t know something and is extremely good at organizing and conveying is thoughts, thank you so much.
This is so refreshingly different in approach to the create a divide and conquer or binary search etc algorithm. And the feedback was really great. Thank you so much for this resource.
Cool content, I really like the debrief section at the end.
It would be nice to see a third segment at the end where you and the interviewee reflect on the feedback from the interviewer.
That could be interesting. Thanks for the suggestion.
being a novice my first thought was remove the * and do an 'any' search, seems like O(n) would be pretty fast already but getting it to O(1) is neat and an interesting example of forward planning
edit: after testing it's not possible to do it quite so easily as "c*t" fails the 'any' check unless you add in pattern checking etc which makes it much less time efficient
What a cool problem and solution. Definitely would've been sweating that one. Thank you Don and the participants. 🙏
This was amazing, I need to watch more of these type of videos.
Man, this is great! Thanks for the video.
I really liked how casual they were with each other in the interview. I was expecting more of a corporate setting as well as conversations. Great video :)
mock means not real bro
@@stemipadpro what's the point of your comment?
@alwinbaybay @stemipadpro you are both right, this is a mock interview but to a great extend this mirrors real life.
Coding can be challenging, collaboration and conversations shouldn't be.
As long as boundaries are observed.
After giving multiple interviews at big tech can confirm being casual doesn't hurt.
She is a very very good interviewer, I really liked the feedbacks at the end. Amazing content, congrats and keep it up!
It started off very simple then got much harder. If I understood the interview process correctly it seems like the point of the coding interview is to see how you solve problems when you don’t know the answer to that problem initially.
Yeah, it can be a really popular and effective strategy for interviews.
Yeah, and the cool thing about these problems is that one often HAS to reconsider initial assumptions / designs, and often a simple change (in data structure for example) can reduce the complexity of the problem. Else, one ends up trying to fit a square into a circle, and this is sometimes not that obvious under pressure.
Hi Marlow! Different interviewers have different styles. The overall goal for the interviewer is to gather both a signal (hire/no-hire), and the stength/confidence of that signal. Similar to cell phone reception strength bars. You can have a really strong 5 bar signal for a slower 3G/4G connection, or you can have a blazing fast 5G connection but with only 1 bar. The goal of the interviewer is to measure the connection speed and get the most bars possible. Some interviewers prefer ramping up from easy to harder problems, and some prefer jumping into medium level problems and not getting any harder.
This is one of the most impressive interview I've ever seen and tbh I would not have passed it! Sophie is a thorough interviewer and I have gained a lot from her observations
@@TheMasterUzi DANMMM
@@TheMasterUzi What are you on about 🤣. I'm sure you would've flopped it
How come the senior technical interview is way more chill than entry-level SWE
they both look so chill
I appreciate you making this video looking forward to watching more videos like this
you have me subscribed
Welcome! That's just confidence from both the interviewer and interviewee. That's what an entry-level interview can look like, but anxiety tends to get the best of most people in the beginning.
Hi Kelvin, a common misconception is that senior engineers have to be better at data structures and algorithms. The DS&A bar is really the same, regardless of the level, and the smarter you are is not the more senior you are! With senior candidates, having clean code and clean thought process is more important. You want to hire someone that will mentor and do code review for junior engineers and instill in them habits and patterns for writing clean code. But you don't have to be any smarter to be more senior :D
As a developer with 6 years experience these interviews are ridiculous. I get you need to know how someone may think about solving a problem but this isn't a real world situation solving a problem on the spot while someone is pressuring you lol. In reality if i needed to use regex for something complex i would just google it lol no one has time in a real world situation to take an hour figuring out the answer when google is right there. Interviewers should ask about experience, security, architecture and to show your code for any features you've created.
I tend to agree, I think the interviewer needs to understand that. And it is more important for the candidate to talk through a solution and outline their process vs testing their memorization of mdn web docs.
14 years in the industry and I can attest; these questions are absolutely absurd and as soon as I get answered one of these questions, I end the call or walk out. I'm not wasting my time on companies that value hackerrank solutions more than all of the other attributes it requires to become a competent developer.
@@Maverick2k I've been developing for 9 years. I applied to some remote jobs, and one sent me a hackerrank test. I didn't do perfectly, but I did just OK. This was not a FAANG company, so why bother testing me on dynamic programming that isn't going to ever be used on the job? Even though that company wanted to proceed with the next stages in the interview, I didn't want to. On the other hand, I had a different company which gave me technical questions about real problems that they actually experienced. As a result, I ended up taking that job.
Wanna mentor me and make superiour web-developing machine from myself? I have all the free time of this world.
Interviewer said you are free to look up anything you want. As an interviewee who hired 20+ developers without live test and only a sample project, I can tell that does not work. I think, if you are confident on what you can and can not do, these interviews should not be a problem. Just be yourself and work on camera just like you would off camera. The goal of this interview is to see if you are a good fit and what your level is. If you are feeling insecure or pressured, that seems to me like your way of thinking of interviews is flawed. I know being questioned on the spot is not a pleasant feeling in general, but sadly there is no other reliable way.
As a response to, "Interviewers should ask about experience, security, architecture and to show your code", that is usually asked in the previous step, but all those questions can be easily faked. You can not believe the amount of people who says they can do something and when we ask them to do it, they just can not, even offline and without time pressure.
It is near impossible to know full capability of developer in the matter of hours, but that is what you have to do as a interviewee. If you get it wrong, it will cost your company 6+ months.
This was really cool and helpful as I prepare for such interviews myself. It did not feel fake at all. I feel like I would have gotten into the “Yes” bucket, too, as I worked through the problem myself. That being said, I did have the advantage of being able to pause it and think through things in a zero-pressure situation. I thought the feedback Sophie provided was excellent. I was initially confused about the setup function as well, but that is where we’re supposed to ask better questions and she was very gracious throughout the whole process. I also appreciated her comment about needing to ask more behavioral questions to gauge seniority.
So, I am both a developer who has gone through many interviews as well as a current hiring manager of developers. I think that in an idealized environment this is great. In practice, it would almost never go this smoothly, and I have been the victim of this kind of scenario being abused. Asking someone to work in an environment outside their norms with direct observational pressures and stresses, things are never going to be this fluid. I think the discussion of the code was worth far more than the actual coding, and that could be accomplished with some standard example code prompts for discussion.
The only thing I object on this practice is developer not using their preferred IDE/editor. Also developer should be aware they are always free to google anything they want as long as it is in screen.
@@erkinyildiz2367 It's my own experience that I can talk to a developer, ask them questions, and I will be able to figure out very quickly what kind of a dev they are. You're far more likely to get a false bad read than you are by asking them about how they approach problems, what patterns they use, and that sort of thing than you are by taking them back to college-type interactions. Also, unless they're coming in as a Jr Developer there's going to be evidence and corroborating accounts as to how good they actually perform. Everyone will use the tools they're happy with. I'm not happy with this one. If you are, more power to you.
@@GravyTraining "Also, unless they're coming in as a Jr Developer there's going to be evidence and corroborating accounts as to how good they actually perform." What do you mean by that? If you mean they will have references willing to speak highly of them, that is not always true. Sometimes really good devs work at really bad companies, which is especially likely if they don't live on the East or West Coast.
Thanks for doing this I really appreciate that
Wow, really great feedback from Sophie! Super helpful.
Super beneficial to see the interview and communication process
This is FAANG or now called MANGA tier frontend engineer technical interview. Watching Sophie grilling Dan with time space complexity through out the interview made me realize the importance of understanding Big O for big tech company interview. Thanks for this valuable mock up interview. We need more of this please!
Another one should be released in the next month or so.
not at all dude, this is a junior interview in my reality
@@RaZoRxan junior to mid at best but even then definitely not MANGA tier, just your normal everyday interview
@@RaZoRxan I don't think a jr would know this to be honest. More like mid to SSr.
pretty sure this is LC med so perhaps 1 question of 5 you’d be seeing in FANG
Hey. Just want to say that your videos really helped me out. You are the best and coolest and the MVP. Respect for everything you do. You rock! Thanks for being so awesome!!! :)
Immediately subscribed to your channel!
I'm currently learning JS Fundamentals and watching him code gives me a headache probably after 3 or more months i can understand this. Really great mock interview it motivates me more to learn new technology.
Same here, what are the odds 😄
hope ur still learning 🙂
Great mindset to have, seeing something you're unfamiliar with and feeling inspired to learn is basically a key component in being a successful programmer. Just don't burn yourself out!
it's funny, looking at this problem at home makes the gotchas obvious, however I'm sure if I were sitting in front of an interviewer, I'd be sweating profusely 😂. Shows how much pressure an interview environment can create!
9 years experience, never did an interview before as I always got referred by other engineers. So super surprised how straight forward this is. Hoping my interview this week is like this. I had a few ideas alternative on how I would have solve this as well
Wow. Great video. Loved every second of it. Both parties were amazing. i get the interniewee's resistance to that feeling of "I'm drawing a blank here". How an individual deals with that emotion can be very varied so props to the interviewer for her great handling of the situation. She is clearly very good at what she does. As a task-oriented thinker myself the technical parts' importance far outways the non-technical but when you get the interviewing side of the job, you realize just how important behaviour and communication skills become critical factors in career growth. I'm at that point where you realize you need to train in these things to grow as a developer. Hence me watching this video :) So this was amazingly helpful.
i loved it and i hope to see more content like this
That was awesome thanks so much!
Ok feeling good. I got 7 years under my belt and I stopped and got through these relatively easy. I really dig what he said about how he likes to write code how he'd like to use it, and that brings me back to a good happy place in my head
Amazing! thank you so much!
This is a classic Trie problem and can be easily solved with it.
Really fun to watch and super helpful! Thanks a bunch Sophie and Dan! Love the videos Don. Stay awesome! =D
You too!
Thank you! There's a lack of senior engineer interview prep on RUclips.
Very helpful and precise. Thanks for sharing.
This was a great interview!
First of all, the question is wow. I came up with the logic inside the `isInDict` function, I couldn't think of optimizing by creating a structure, and it was really impressive by how he wrote js code fast. I mean the speed doesn't matter but I believe it showed that he's fluent in a language javascript. The feedback given by the interview was also constructive and amazing. Thank you for sharing the great video!
really helped me in deepening the javascript language 😁
Took me a while, but I would take the input array, iterate through it and generate every possible pattern per word, store it in a Map structure. The 0 wildcard case is also pattern.
EDIT: during implementation I just realized I only need a set :)
At first glance I was thinking bloom filter/set for q1 than q2 my first thoughts were Trie where we attempt all paths when we hit a * and after you mentioned looping over the list I was thinking take prefix + try all chars + postfix to see if its in the dict
This mock interview was great! So many times I have wondered how a good or bad interview goes, and especially to hear the feedback from the interviewer (because this doesn't happen in real life)...very helpful !
What do you mean it doesn't happen in real life? It does. Every time I had interview like this, interviewer was helpful and discussing with me.
Seems like a really good structure to use here would be a trie.
I LOVE THIS SERIES!!!! :) Thanks Don
Thanks for sharing!
Setting up Trie in the constructor might have helped. I guess that was what Dan tried to come up with. if wildcard is provided in isIndict, you just need to iterate thru all the leaves to find the match
Totally, that'd be more optimal, but this is just weird. Why even have a trie as a frontend dev? The space (and time) complexity of setup is O(NM^2) where N=array size and M=length per string, and it supports only one wildcard. The first solution supported multiple wildcards and would have been faster in almost every real-world scenario.
@ A `Trie` type structure would be reasonable if you needed to implement an `Autocomplete` that had to search through a lot of items. Maybe something a bit like a "Ticker Search" in a stock trading application -- in this case, there can be a lot of items, since there are many tradable listed companies, etc, and each would be combined into a separate pair item. There could be millions of potential tradable pairs, and if you also add wildcards in it could be very slow.
classic leetcode problem aka make a trie and recurse if it's a wildcard and return true if we reach end of the trie and false if a single letter is not a wildcard. time complexity depends on how long the word is / how many paths we need to take due to wildcards and space is mostly based on the call stack bc of the wildcards.
I've just begun learning Python/coding in general and this is daunting.
Are you still going?
First thing I thought of was storing the dictionary as a trie to optimize the runtime of `isInDict`, I think I can see the interviewer's excitement when the interviewee starts getting "warm" towards a similar solution lol
And her way of leading him towards that solution without giving it away is also pretty skillful
very helpful thanks for sharing
This is such a good video
Tough interview. I don't see myself passing this but then again, I'm an accountant.
This is amazing video with a lot of great helpful works very you.
Seems like you can just interact through each letter in your dictionary and check that the input words letters match. So word one character one would check if the first character in the input word matched. Then just keep doing that.
My approach was to find the index where the * is and replace the letter from the dict word at this position with a * too. Then you can just dict.some(dWord => word === dWord). RTC should be O(2n)? Find the index and then loop through dict words while replacing the letter..
His hairline is impressive for a senior dev
He's the resurrected Boris from the Bond film Goldeneye.
I'm not really that impressed with his JavaScript fluency though
@@minademian 🤣🤣🤣🙌
@@minademian “I AM INVINCIBLE!”
💀💀
Dan needs to discover styled components for react native - really fills a lot of the gaps with the mobile styling issues he talks about
I eenjoyed every bit of this video..aweesome
What they are trying to come up with on the coding interview is basically very similar to a Patricia Tree, which ethereum uses in a differente way in its block chain.
i would have aced it but the follow up (multiples wildcard) question had me. For that, I was thinking toward binary search
Another way to solve this problem is to create your own function that compares a two arrays character by character. if there's an asterisk, in that particular string location then that means you have to skip that character and just compare the other characters of the word.
he's very inventive. i would created a tree node dictionary, every node is letter. and for any wildcards, search the BFS. O(n), where n is number of letters in the input. I dont understand reduce() very well.
Wow. This channel is amazing. Thanks for bringing such interviews. I am a software engineer myself with 3+ years of experience. This video is helping my in upskilling.
You're welcome!
I could only make it through 22 minutes in due to time constraints, but I thought he should sort the string array in the setup with an O(n*lg(n)) sort complexity in the setup and then use binary search for an optimized search mechanism for O(lg(n)) search complexity. Wild cards ... didn't recall if they said the wildcard represented 0 or more characters... I don't know about that... I'll finish the video later.
You guys are highly professional
i came back to this video after visiting 4 months ago and this time i did the assignment along with the video. i didn't allow reference material since guy in video didn't have any. I got what i believe is a working solution. i was thinking of some kind of tree structure at first but realized that would take too long to do. since i am learning javascript and i had just done some samples with maps, i decided to use maps to do all my preprocessing and then my lookup. assuming some kind of fast hashing is used to access elements of the map, my map solution would have ok speed. if i did only ascii characters i could have wayyy sped up the search. but i decided on an international language solution. once it seemed to work i spent the last couple minutes renaming my variables. if anyone tries out my code please let me know where it can be improved so i can use that advice on my other projects. thanks. here is my solution done in the time allowed:
function buildSubDictionary( subDictionary, word )
{
const firstLetter = word.substr( 0, 1 );
let dict;
if( subDictionary.has( firstLetter ) )
dict = subDictionary.get( firstLetter );
else {
dict = new Map();
subDictionary.set( firstLetter, dict );
}
if( word.length > 1 )
buildSubDictionary( dict, word.substr(1) );
}
function preprocessDictionary( wordlist )
{
const wordDictionary = new Map();
for( let i = 0; i < wordlist.length; i++ )
buildSubDictionary( wordDictionary, wordlist[i] + '#' );
return wordDictionary;
}
function findWord( subDictionary, word )
{
if( subDictionary.size === 0 )
return false;
const firstLetter = word.substr( 0, 1 );
if( firstLetter === '*' ) // wildcard
{
if( word.length < 2 )
return true;
for (let [ledder, subDict] of subDictionary.entries()) {
if( findWord( subDict, word.substr(1) ) )
return true;
}
}
if( !subDictionary.has( firstLetter ) )
return false;
if( word.length > 1 && !findWord( subDictionary.get( firstLetter ), word.substr(1) ) )
return false;
return true;
}
function wordInDictionary( dictionary, word )
{
// all words added to dictionary have a # terminator
return findWord( dictionary, word + '#' );
}
function buildAndTestDictionary()
{
const gameDictionary = preprocessDictionary( ['car', 'cat', 'dog', 'deer']);
console.log( 'has *at ' + wordInDictionary( gameDictionary, '*at' ) );
console.log( 'has d*n ' + wordInDictionary( gameDictionary, 'd*n' ) );
console.log( 'has dee ' + wordInDictionary( gameDictionary, 'dee' ) );
console.log( 'has d*** ' + wordInDictionary( gameDictionary, 'd***' ) );
}
buildAndTestDictionary();
I'm surprised how much she helped him. It was like hand holding him to the answer.
My face melted off early on...good vid
That’s good. Face melting was the goal of this video.
Wow this interview made me realize how dumb I sound in most interviews. No wonder I'm unemployed still lol
with the code at 41:59 if I do isinDict('ca') it seems this will return true, but it should return false. It didn't seem like interviewer knew about it because they decided to follow-up even though problem with 1 star isn't solved. We could do 26^K (assuming we have lower-case english chars) for search and N*K(worst case) for building and memory with Trie in the worst case. alternative is K for search and (26^K) * N for building and memory. (26^K) * N (worst case with all possible permutations) could be enormous value.
I think he would fail the solution was syntactically clean but all his solutions had an O(n)^2 time complexity. The point is in setup you convert the array to an object or a map and in the inDict you use hash search which is object.hasOwnProperty or Map.has as both of these search methods have a time complexity of 1. I got stumped on a similar interview question the interviewer was nice enough to explain why I had gotten it wrong
Hi Simon. A lot of companies don't have a single pass/fail bar, most have a range of outcomes. By not having the most efficient solution, you might not get a "strong yes!" but you might be able to still pass because of the cleanliness of the solution and strong and clear communication of the thought process. We often see people put too much pressure on themselves to get the perfect solution or otherwise fail. This works if you get every question perfect, but it's not the most efficient and overall successful way to approach interviews.
I was surprised he didn't ask when first assigned the task:
How do we treat capital letters?
How big can the list of words be?
English words? Unicode?
What kinds of wildcards?
What will be the longest word? supercalifragilistic? antidisestablishmentarianism?
How will the code be used within the company? Throwaway? One-time? Multiple use in many apps?
Will it grow so complex that we need to move it to C or webasm or faster sub-system? (should code be written to be able to easily port to other languages?)
Never mentioned possibility of building a tree/graph/etc. either unidirectional or bidirectional out of the list of words for easy lookup. I thought the interviewer kept hinting to him - please do most of the work in the constructor so that lookup is fast and simple, but I don't think he understood what she was asking for.
I thought he should have asked more clarifying questions as well, especially around the wildcard functionality (particularly, how many wildcards came to mind immediately, and also, system constraints -- can I trade space to store a crazy data struct that would enable efficient lookups?). However, I'm not surprised because I've brain-farted one too many times under the pressure of interviews, and what's seemingly apparent went right over my head and the hints just didn't register 😂
thats why such interviews with coding sessions solving "real problem" is wasting time, it is not possible to solve such problems in one hour!
@@ceplusista i know a bunch of coders who could all do it in less than an hour. however, i do like when they ask several questions of increasing difficulty and challenge your problem-solving skills
@@mazthespaz1 I know right?? People use the word "senior" so loosely these days. It was pretty Junior-ish. Mid-senior level tops.
I was actually sweating for this guy when he started the class like a regular function, he later removed the parentheses and I was able to breathe again 😅
i love the fact that these coding interviews still exists lol
Sophie killed it!
I don't understand why they are so obsessed with ds & algo, like only ds & algo matters? Reflection, debugging, networking, multithreading, design patterns, distributed systems, memory management, docker, inversion of control frameworks, integration tests. No one cares?? So go solve enough leetcode problems and you are senior dev?
true!
There are multiple rounds. Things you have mentioned would be tested too in system design round
Thanks for sharing this, and thanks to Dan and Sophie for taking part in this exercise, that was really interesting to watch!
That's a lot of high level library methods for a simple string building task. This makes it so more complicated to read.
So there is difference between finishing uni and not. We learned of trie in 2nd year at construction and analysis of algorithms class.
NIce one. enjoyed watching
What is "isIntdict" function purpose? Setup seems to create a dictionary but what is Intdict? This interview seems easy and could be more simplified, he got any entire hour to get it right and able to debug.
I would like to have seen what his searches looked like. I have a huge blocker on what is appropriate to search and what that search looks like.
@Don, let's say if someone is in Manual testing profile and want to switch to automation using programming language like JAVA. Is this channel a good choice for those guys also?
It can be noted for up and coming Devs not all interviews are like this. Watching these can seem very daunting, most of them are very simple and they are looking for someone who would fit in well within a team.
oh thank GOd because that was terrifyingggg!!! to be honest im
just at the beggining of my career..just graduated from a bootcamp so..its too much for me definitely but I enjoyed it a lot! an d learned a lot
Visual coding is so much better and flexible. I always beginning from the end, probably I am different of a common people
love it!!!
Honestly, interviewing is a blade you need to keep very sharp. It's a skill that is overlooked, often times costing you the job. Most important details after technical boils down to one thing: did, I like the person?
I was asked this same problem when I interviewed with Blue Origin after graduating college (I didn't make it haha)
This video is very educational and especially Sophie is very talent. Unfortunitely, she did not see the potential power of Dan. She values Dan's skill, coding behavior, etc exactly. But in my poor opinion, it seems like Dan is a little nervous and he does not have any experinece to have this kind of technical interview before. If he puts something more a little, he will be a greate engineer.
This was a fantastic mock interview! I've been surfing the web this past week preparing (as an Interviewer) to find the best mock interviews to learn from. Have found a lot of takeaways as both an Interviewee and Interviewer 😄
Thanks so much for setting this up Don. Dan, Sophie and Noa were amazing in the two mock interviews I've watched here, definitely looking forward to more of these discussions on your channel! 😀
Is the levesthein distance a possible solution of the jolly character problem?
come on regular expression look , every time you have a character like a star or a dot you look on the second position if it’s a you look for ace in the array so you can search it that way and you can make very fast search with it with a method so you start to searches or you can search backwards or you can search like for characters with the specific amount of positions of characters so free for example, and every vent has small characters in free will be excluded.
In the specific test, it will be faster to search for the “t” on the end of the three letters, the search will be extremely fast.
wow i understood this, apart from the data structure language (o) notation, looked like java?
As far as interviews go, this was a good one but I have to say from my experience, it kind of is a hit or miss for what interviewer you get. Some are nice, some are okay.