What to expect during a web dev interview (sharing my experiences)
VloĆŸit
- Äas pĆidĂĄn 16. 11. 2022
- article referenced in the video: swepro.co/the-7-interview-typ...
đŹ Discord / discord
đ Newsletter eepurl.com/hnderP
đ. GitHub github.com/codyseibert
My VSCode Extensions:
- theme: material community high contrast
- fonts: Menlo, Monaco, 'Courier New', monospace
- errors: Error Lens
- extra git help: Git Lens
- tailwind css intellisense
- indent rainbow
- material icon theme
- prettier & eslint
- ES7+ React Snippets
Some tips from my humble experience as a junior developer:
1. Show up a bit early - 5 minutes before a zoom interview shows that you respect the interviewer's time.
2. Don't be afraid to be light - If you throw on a joke or two, or have an open conversation with the interviewer, it can really lighten up the interview and put both you and the interviewer at ease. Just don't overdo it.
3. Explain what you do as you do it - I've had numerous interviews where I was going the wrong direction with my code, but since I explained what I'm doing and why, as I was coding, the interviewer was able to understand my thought process, and either redirect me, or ask me questions so that I was able to conclude that I should try something else.
4. However the interview went, be kind - Even if you think the interview didn't go so well technically, you'd be surprised by how much a good attitude and a thank you at the end of the interview can get you.
5. Have fun - You don't have to know everything the second it is mentioned. Take it easy, think about the questions you are asked, and have fun coding. People can sense when you are genuinely having fun coding, and it leaves them with a thought of "Hmm, this guy is having fun coding, maybe he can be a good addition to the team."
6. If you don't know something, it might be a good idea to mention it - Depending on how fundamental the subject is, if you are not sure about something, it might be a good idea to say something along the lines of "I'm not quite sure what that is, but I think it is when ...". It might be better than simply saying something that turns out wrong, but also better than saying "I don't know" and losing all the points on that question.
That's my 2 cents, good luck!
Thanks for that info, I know people here will appreciate reading it
to all people who are about to be part of an interview
i had my interview around 3months ago (was my first ever technical interview) i was pretty nervous but excited too!
- i messaged my interviewer prior to the interview and asked about what kind of questions to expect (i got some helpful infos)
- it was a very chill session, first we talked about myself and experiences (im a junior) so not too much to talk about then he asked me html, css questions (i could not answer all of them which was totally fine)
- he really liked that i knew how to handle the dev tools and had some knowledge about performance in the web (lighthouse is your friend here)
- for the coding part: i had to call an api with user input, not even sure if my code worked because the api was broken, but he was fine with my solution
at the end i had a lot of fun, learned some new things and got an offer about 2 days later, you guys got this!
DSA questions?
â@@pepperdayjackpac4521 you mean Data structures and algos? no, not really since the job i applied for was "frontend engineer"
@@OfficialLRY yeah, data structure and algorithms. And oh, I assumed every technical interview had some sort of dsa question. Thatâs sort of a relief
@@pepperdayjackpac4521 i see, i can only speak about interviews in germany :/
@@pepperdayjackpac4521 i have assumption that small companies that aren't like FAANG are not so centered about theese types of questions(don't know what interviews are about in your country). I've seen few interviews, been on one, questions tend to be 1. some shit abt html and css 2. some can ask if you vagely know what http is(and what status code there are, not every code, just what each section means e.g 200-299 - success in some sort, 400-499 - client error, 500-599 - server error) 3. js, built in methods, general stuff like how to determine if variable is an array or what will be output of typeof null 3.1 in every interview my friends were - question how to make deepcopy of object 4. some ask about design patterns, just which you can name and if you can describe them 5. event loop(my interviewer asked bonus question "how to create microtask w/o using promises", i was shocked that exsisted) 6. very basic react stuff 7. very basic redux stuff
Hey man could you continue posting content such as this, I shared your last video âDay in the lifeâ to my programming professor and he enjoyed it. Shared it with the class, this content shows me whatâs itâs really like and whatâs important. I appreciate it!đ€đœ
Knowing how to use Dev Tools is essential. During my interview, my interviewer was very surprised at my knowledge of them.
Communication skills are the second most important thing. You have lots of meetings as an SWE and being able to thoroughly communicate ideas is a must.
Good luck to you all.
Really liked this video! I've kinda been doing your interview questions as practice before watching each video just to get a notion of where I'm at.
I am a junior dev currently interviewing, and really liked what you said.
Keep up with the cool videos!
I had a full stack interview where the job posting was mainly focused on frontend 70/30. I studied and prepared as much as possible for about a week before the interview. During the interview he asked me if I knew what ACID was. I said yes I've heard of ACID compliant data before. He wanted me to go into detail about it and I couldn't remember it or explain it very well off the top of my head. He then decided to go deep into database topics and I'm just like wow... Out of everything I studied for, it was not databases. Mind you I know basic databases and was required to take a database course. This guy really wanted to talk about the virtual and physical aspects of databases and dbms. Not a single frontend question was asked in the 30 minute interview.
I thought about it for a while but I came to the conclusion that it doesn't matter if he found my weakness and just wanted to destroy me in that interview or if it was just a bad interview or whatever. My takeaway is that a career in computer science is extremely broad. There's so many different types of developers and even the same titles can have extremely different responsibilities and experiences. I definitely over prepared myself for the interview that was doomed from the beginning and it just wasn't the right fit. It doesn't matter if I answered his questions perfectly or not. It doesn't matter if I got the job. I probably would've hated working there.
That sounds rough. Iâm not a fan on quizzing on acronyms, especially if its a junior position. Not sure a junior needs to care if a db is acid compliant or not
You are right, being enthusiastic, humble and interested are very important, if not the most important. (besides knowing how to code, obviously)
The HR guy in the company I worked for told me one day
"Do you wanna know why I hired you?"
"yes"
"You were the only one who showed that you really tried our challenge, even though it was not perfect. You asked questions, the others didn't asked. You were one of the very few who actually knew what our company does and that's why we hired you."
I always take half an hour to do some research on a company's site, facebook and linkedin profiles. It helps a lot.
The previous company I worked for, the interview was supposed to last 1 hour. I asked questions for like an extra 90 minutes. And at the end they were like "we'll send you the contract tomorrow".
One extra thing I wanna say, if you manage to make them laugh, it relaxes the atmosphere and puts you at their top of the list. However, be aware, jokes are very risky and never start with a joke. lol
Yeah this is probably the best approach. With a bunch of people interviewing just to land a job, it really helps to show youâre a real human and not an asocial. Helps to show you care about the position
Interesting stuff đ. Thanks for sharing your experience đđ!
amazing video thank you very much!
Learning right now, so I'm a little nervous about the interview process, but will make it
Thanks for this!
Good job babe!!!!!
Nice video
Hey, could you make a video on some resume advice, for people who have like 2 years of experience, looking to switch?
I've never had this happen to me, so take this with a grain of salt, but I hear one reason as to why someone may pass on a take home assignment is because, from what I've heard, companies have given assignments that turn out to be actual work. Once they receive the assignment back, they state they'll review the code, but in reality, they stole someones work and don't plan on hiring the interviewee.
Like I said, it hasn't happened to me, nor do I personally know anyone that this has happened to but I have read it on posts in the past that this has happened to a handful of people.
Ultimately, I agree with you that if you want the job, do the assignment. At worst, you lose 4 hours of your day, at most, you'll get a job.
Yeah, with how software systems are setup, itâs very hard to have someone solve a coding challenge question and actually incorporate that into your real system. At the very most the interviewee would give you a star shaped block that you have to force into a cycle shape hole on your project, so youâd end up doing just as much work getting it to work well with your current system.
Iâm not saying shady companies havenât tried getting free work from people, but as an interviewee if the take home assignment is looking like a real legit feature for their company and it takes you a long time to do, Iâd skip it.
happened to me. the back end team wanted to learn how to style a react app with tailwind. Took me 8 hours to do the entire mockup and they never even got back me to to say the job was "not available anymore"... disgusting.
Hey Cody. I have been following you for a while . Your videos are not just awesome but also inspiration and a big motivation for me. If you do accept requests to review projects/code (ofcourse not free) I'd like to get a review from you.
You can try to send me something to review but no promises
Am in college, my third year, am undertaking an economics degree, though i got into web development like a year ago i just hope i'll find an internship when i leave for the holiday this semester before i join my fourth year.i like your videos
good luck I hope someone gives you an offer when you apply places
I've only had about 2 phone screens or so. Never got past them and I never have any idea what type of questions to ask during this part of the interview. I asked what the tech stack was and she tried to figure it out but couldn't. Hopefully I can start getting some calls back and get through the first damn phone screen lmao. Also asking questions seems like the hardest part when you've never had a job before. How am I supposed to know what I want to know about them if I just don't want to know anything? I dont want to know either because I'm inexperienced or because idc I just want to work and learn
Yeah thatâs true, itâs hard to know what to ask when you donât know what to expect. Even if you could come up with a couple of generic questions, âhow big is the code baseâ, âis this a greenfield project Iâll be working onâ, âhow big will my team beâ, âwill I be given a mentor or onboarding buddy when I join or is it just âgood luck, here is your taskââ. Stuff like that. I hope you get past your phone screening. What type of questions do they ask you?
@@WebDevCody I've really only been asked personal questions and basic stuff about me. I had one where I asked if I could followup and she said there's no point because she's supposed to pass my resume down to someone else after the phone screen and if I don't have the skills on my resume then I won't get another email or call from whoever they passed it down to.
the article link sends me somewhere else.....
Apply for a web dev position. get lots of leetcode problems for interview
People coming out of college are really not super fluent/competent coders?
No, not really.