CoderPad

CoderPad

CoderPad is a technical interview platform for leading development teams. It enables a quick, accurate read on a candidate’s skills. CoderPad works like an IDE to help candidates easily share their skills and ensure you understand how they work. Through both collaborative coding sessions and take-home assignments, CoderPad is with you at every stage of the hiring process.

Пікірлер

  • @lewiemarks6418
    @lewiemarks6418Ай бұрын

    I had terrible interview the other day for a junior role. Interviewer was rolling eyes, yawned once and asked the most generic and pointless questions, asked only one question about tech the rest were "give me example of X or Y in your current role, half of which didn't pertain to my current role. Lovely experience.

  • @shaunp1660
    @shaunp16602 ай бұрын

    This was painful to watch. Realtime coding interviews do not realistically reflect an engineer's ability to assess a problem and solve it using all of the tools at their disposal. In this case, having a candidate draw out their logic and write code or pseudo code on a real whiteboard and then explain what they drew and wrote would have been more effective. Alternatively, giving the candidate a larger take home project that closely reflected the level of sophistication they need to have for the role, followed by a code review interview, would have been even better, as it would 1) demonstrate the ability to arrive at a working solution without hand-holding, 2) give the interviewer a good understanding of the candidate's communication skills, how the candidate approached the problem, why they implemented it in the way they did and whether they understood the code they wrote, and 3) would realistically reflect how they will interact with the team during PR reviews. The interviewer in this mock interview had A LOT of patience; however, since filter() was suggested, I'm not sure why a simpler and more concise solution was not recommended for the initial problem. JavaScript is not my strength, but given the clue about using filter(), even I could see that no for loop was required and it could be made easier to read. For example: function diffSet(arr1, arr2) { let set1 = new Set(arr1); return arr2.filter(value => !set1.has(value)); } const array1 = [1, 2, 3, 4]; const array2 = [1, 2, 3, 4, 5]; console.log(diffSet(array1, array2)); // Output: [5] or if OOP needs to be demonstrated: class ArrayDiffer { constructor(arr1, arr2) { this.set1 = new Set(arr1); this.arr2 = arr2; } diffSet() { return this.arr2.filter(value => !this.set1.has(value)); } } const array1 = [1, 2, 3, 4]; const array2 = [1, 2, 3, 4, 5]; console.log(new ArrayDiffer(array1, array2).diffSet()); // Output: [5]

  • @BBRR442
    @BBRR4422 ай бұрын

    Thank you! Hope i nail my interview

  • @farazahmed7
    @farazahmed72 ай бұрын

    Where is the delete tool?

  • @CodyHortonTalent
    @CodyHortonTalent3 ай бұрын

    Thanks for a great discussion. My input on the question of whether you should use AI to compare candidate's answers to an interview question is No. You should not compare candidates to other candidates. All candidates responses should be compared to the requirements for the role. Whether using AI or not, it is key to assess candidates based on job requirements, not against each other.

  • @uchennanwosu4625
    @uchennanwosu462510 ай бұрын

    I hate to say this, but you guys are going about coding the wrong way. You are getting lost in the implementation details. The first thing to do is to draw pictures. This enables you properly visualize and understand the problem -- you did this when you had the lists side-by-side vertically. Afterwards you can choose your algorithms. At that point you can opt for using inbuilt functions like filter, include, splice etc. In this case, the problem is isolating the differences in both lists. The solution is iterating through the first list and for each member checking to ensure it is not in the second list. If it isn't push or append it to a temporary list. If it is in the second list delete it from the second list. When you have looped through the first list, concatenate your temporary list with whatever is left (if any) in the second list - those are items in the second list that do not exist in the first. Deleting the items in both lists enables us to ultimately determine the items in the second list not in the first. It also makes the code more efficient because the second list potentially gets smaller as we progress in the loop. The advantage of using the so-called old way is that it's simpler to do a runtime analysis of your code. When you use inbuilt functions, you have to be either knowledgeable of their implementation or view their documentations. In certain cases, they make your code more difficult to read and maintain. 😊

  • @CrisDevDotDot
    @CrisDevDotDot23 күн бұрын

    yeah, lists. more specifically linked lists and hash structures. that's where deletion works. arrays in true sense are contiguous and fixed size, deleting something means re-creating an array without the deleted element. but differs on the language. javascript uses hastables for arrays so not contiguous, C/java use the real deal arrays(fixed-size and contiguous in memory) [although Java is debatable based on the JVM type, so contiguousness is not assured]

  • @housetechStudio
    @housetechStudio10 ай бұрын

    Nocmts

  • @marsinsmusic
    @marsinsmusic10 ай бұрын

    thanks

  • @BrianWoodruff-Jr
    @BrianWoodruff-Jr Жыл бұрын

    Why did this show in my recommendations?

  • @phil7121
    @phil7121 Жыл бұрын

    Interviewer: "Which one do you want to start off with?" Interviewee: "Probably the array one." Interviewer: "Okay, sure." *picks the Diff one*

  • @derickmoncado
    @derickmoncado Жыл бұрын

    My brother in christ. The humiliation, the carnage. This was like watching a train wreck that lasts an hour looool. Had no idea this was online until someone messaged me about it ha. Everyone, everyone, I suck A LITTLE LESS now okay 🙂, I'm still dogsh*t but we still out here practicing don't worry. -guy in video

  • @marlonstevenson4923
    @marlonstevenson4923 Жыл бұрын

    How long had you been coding for when you did this mock interview?

  • @derickmoncado
    @derickmoncado Жыл бұрын

    @@marlonstevenson4923 Honestly, since 2012. I know, I know, but it was mainly just HTML, CSS, and Sass with a tiny bit of jQuery. Hadn't ever taken programming seriously until 2020 when the pandemic hit and realized how much I didn't know. I'm still dogsh*t at it but making progress. Data structures and Algo's are just very difficult for me, can't seem to get them.

  • @jerictorres3552
    @jerictorres3552 Жыл бұрын

    Idk if you see this man but i'm an 8kyu type of guy and you seemed very human and it was a relief to see this type of interview vs the galaxy brain 14 year olds interviewing at google. So fwiw I greatly appreciate your sacrifice to all of us underachievers.

  • @derickmoncado
    @derickmoncado Жыл бұрын

    @@jerictorres3552 appreciate the kind words man 🙏 I've got nothing in those kids, on my best day, they could probably code me under the table on their worst. This was probably the most vulnerable I've ever been, I honestly needed it though. It gave me tremendous perspective.

  • @jerictorres3552
    @jerictorres3552 Жыл бұрын

    ​@@derickmoncado I'm glad you're okay with it. Definitely nothing to be ashamed of. It was really cool cause a lot of what you said were a lot of the same things I feel like I would think in the same position. Granted, I'm not exactly a dev, but adjacent, and I hate technical interviews with a passion. I really can't shine in them but I'm trying to improve that aspect of myself anyway. Are you dyslexic/mildly dyslexic by any chance? I saw you mentioned that algos are a struggle for you, you should maybe consider that. This realization helped me with algebra, calculus and physics etc. Tbh I used to think my brain just couldn't do it. I struggle with algos a lot too, and I think it's cause I have dyslexia/dyscalculia. I actually use bizarre highlighters, themes and even comic sans (comic code) in my CE so that I can visualize the logical structure of my code better in my head. Learning is much, much easier for me when I write difficult concepts involving variable, algos, and logic on paper and then transfer. I would actually do BETTER in a technical interview if I had to use a paper and pencil lol.

  • @notpreacher1564
    @notpreacher1564 Жыл бұрын

    I love how patient the interviewer is.

  • @derickmoncado
    @derickmoncado Жыл бұрын

    Corbin was a saint for this.

  • @CrisDevDotDot
    @CrisDevDotDot23 күн бұрын

    i think it's actually an interview to hire a "technical interviewer". so the junior dev will decide if the interviewer gets hired based on his competences and patience 😆😆

  • @NewVybzBoss
    @NewVybzBoss Жыл бұрын

    I love to see this. Gives me more perspective

  • @derickmoncado
    @derickmoncado Жыл бұрын

    You and me both lol.

  • @alexsoyes
    @alexsoyes2 жыл бұрын

    Great video guys ✌️