#interviewcake

[equal-growth]

Top Websites for Coding Interview Preparation💥🔴! Follow ➡️ Pythontechno for more content. #pyhton #computerscience #job #career #enrollnow #socialmediaalgorithm #developers #today #tommoro #ganesh #chathurthi #Websites #coding #interview #preparation #top #Stackoverflow #geeksforgeeks #Interviewcake #Algoexpert #W3schools #meme #laptop #technology #blogger #tutorial #instructor #viral #progress #new (at India) https://www.instagram.com/p/CEL1TVGAsqg/?igshid=1byt8tf5tl49

[mr-struggle6000]

22.06

i got stuck (mostly emotionally) at one of the exercises for linked lists on leetcode. probably because it mentioned hash tables and my brain was like “you don’t know that, can’t continue”

i was disappointed to find out weekly quizzes in the roughgarden algorithms course are not available for free. that is, the answers are unavailable, and the questions are specific and convoluted enough that attempting to figure them out by myself would be very frustrating, so that demotivated me a bit,

but i will continue to watch the lectures. maybe this will hel p me understand hash tables.

i also found this website www.diversifytech.co where i found out about a discount on interviewcake, and after a bit of deliberation i decided to buy the three month course / 12-month access to questions. i’ll see if it’s helpful

One big thing is that i’m now focused 100% on getting a job, but i want to complete some things first. all these sites with coding questions i’m using right now are perfect for me actually, because i don’t feel confident in all of that. applying the knowledge of algorithms and data structures but also being timed

but i also want to complete a project to start a portfolio. freeCodeCamp is making some effort to nudge me and give me some ideas. but having a project i would actually be happy with enough seems so out of reach. i can’t even think of building a house in minecraft without making negative judgements every step of the way. i’m shooting everything down.

but maybe this judgement wouldn’t be what i expect it to be if i saw progress.

but i wouldn’t underestimate my ability to find something to feel bad about anywhere, anytime

[rposervices]

Software Engineers Need More Than Just a Tech Recruiter To Land Their Dream Job

Computer science (CS) majors and employed software engineers should always consider using a technical recruiter when they are ready to being their job search. Using a recruiter saves so much time and can make the interview process much easier. Without a recruiter, it's a lot like trying to sell or buy a house without an agent. It's possible...but it involves many extra steps that you most likely don't even have time to do. But technical recruiters alone aren't enough. Software engineers (SE) who use a recruiter still only have a 1 in 25 chance of getting an offer. That means, regardless of how amazing their recruiter is...their dream company may not be interested. There are several reasons why a tech interview can go badly. The biggest, most common reason is that software engineer recruits simply are not prepared and their recruiters aren't trained in the technical aspects to help them get ready. What are the issues then that CS majors and SE's are facing?  They didn't study the right way They get stuck on a problem and can't get unstuck They forget to be human - not a computer They forget to talk through the code The first issue is that they didn't study right. Studying the "right way" means that they didn't just try to memorize common problems and hope that they'll be able to solve whatever algorithm is thrown at them. Many people fall into the coding bootcamp and 2 week cram session trap. This sounds like a good idea because they desperately want to get an offer from Google, Facebook, Amazon, etc. But in reality it isn't preparing them the right way, and it typically leads to nervousness and anxiety. To properly prepare there are several things they should do.. Mock interviews - Pramp, Gainlo Practice problems - InterviewCake, Byte by Byte Drill down the issues you keep getting stuck on Strings Recursion Dynamic programming Brute force solution Trees Graphs Arrays Big oh notation Work through Cracking the Coding Interview book Before they begin any of the above items, they will want to come up with a studying game plan. Deciding when they want to begin interviewing, and then figure out how many problems/how much time they should devote each day to get ready. Most companies will have the recruit pass a phone screen before an onsite interview. But they want to be ready for both so they aren't scrambling when the call comes. The second reason they fail is that they get stuck on a problem and can't get out of it. This problem seemingly ruins the entire interview because then they begin to panic or simply give up. What they can do are to 1.) find a brute force solution 2.) fully understand the problem 3.) work through the problem by hand 4.) brainstorm different data structures and algorithms 5.) consider all the information they have been given 6.) simplify the problem 7.) breakdown the problem into subproblems 8.) take a step back 9.) collaborate with their interviewer, and lastly 10.) ask for help. The third reason software engineers fail their coding interviews is because they are too focused on getting the right answer that they forget to be themselves. To let their personality shine through so that the interviewer can see if they would fit in well with the office. Will they click or are they not a good fit? This is important even in the tech industry. Companies want to know that their current employees will mesh well with the new hire....and it should be equally important for the SE to want that as well. Lastly, many times the interviewee gets wrapped up in their own head. Thinking through the problem but not actually talking through the problem. This is a big concern for companies because they need to hear what they are doing and thinking. Simply talking as they work is a highly effective way of communicating their skill set and abilities. Tech recruiters can help their clients succeed and get the best offers by giving them resources to study and prepare. It's free to do, easy to send, and will payback huge dividends in the long-run when they get better offers from top tech companies. Read the full article

[aminecodes]

Tweeted

- Don't study all night—sleep! - Practice stuff you rock at - Imagine your best day - Walk through your problem solving process - Precompute your morning - Get pumped { author: InterviewCake }https://t.co/iOcGDRMyMo

— Λmine (@aminecodes) July 17, 2018

[securitynewswire]

Exploiting the code execution engine powering InterviewCake CodeWars others the dangers of SSRF vulnerabilities in an AWS environment

SNPX.com : Exploiting the code execution engine powering InterviewCake CodeWars others the dangers of SSRF vulnerabilities in an AWS environment http://dlvr.it/PNCy81

[codingequanimity]

  InterviewCake: My favorite resource for data structures and algorithms. It breaks down solutions into step-by-step chunks — a great alternative to Cracking the Code Interview (CTCI). My only gripe is that they don’t have more problems!

  HiredInTech’s System Design Section: Great guide for system design interview questions.

  Coderust: If you’re avoiding CTCI like the plague, Coderust 2.0 may be perfect for you. For $49, you get solutions in almost any programming language, with interactive diagrams.

  Reddit’s How to Prepare for Tech Interviews: I constantly used this as a benchmark for how prepared I was.

  Front End Interview Questions: Self-explanatory. An EXHAUSTIVE list of front-end questions.

  Leetcode: The go-to resource for algorithm and data structure questions. The company filter is useful (e.g. you can find questions that Uber or Google typically ask).

[rposervices]

Software Engineers Need More Than Just a Tech Recruiter To Land Their Dream Job

Computer science (CS) majors and employed software engineers should always consider using a technical recruiter when they are ready to being their job search. Using a recruiter saves so much time and can make the interview process much easier. Without a recruiter, it's a lot like trying to sell or buy a house without an agent. It's possible...but it involves many extra steps that you most likely don't even have time to do. But technical recruiters alone aren't enough. Software engineers (SE) who use a recruiter still only have a 1 in 25 chance of getting an offer. That means, regardless of how amazing their recruiter is...their dream company may not be interested. There are several reasons why a tech interview can go badly. The biggest, most common reason is that software engineer recruits simply are not prepared and their recruiters aren't trained in the technical aspects to help them get ready. What are the issues then that CS majors and SE's are facing?  They didn't study the right way They get stuck on a problem and can't get unstuck They forget to be human - not a computer They forget to talk through the code The first issue is that they didn't study right. Studying the "right way" means that they didn't just try to memorize common problems and hope that they'll be able to solve whatever algorithm is thrown at them. Many people fall into the coding bootcamp and 2 week cram session trap. This sounds like a good idea because they desperately want to get an offer from Google, Facebook, Amazon, etc. But in reality, it isn't preparing them the right way, and it typically leads to nervousness and anxiety. To properly prepare there are several things they should do.. Mock interviews - Pramp, Gainlo Practice problems - InterviewCake, Byte by Byte Drill down the issues you keep getting stuck on Strings Recursion Dynamic programming Brute force solution Trees Graphs Arrays Big oh notation Work through Cracking the Coding Interview book Before they begin any of the above items, they will want to come up with a studying game plan. Deciding when they want to begin interviewing, and then figure out how many problems/how much time they should devote each day to get ready. Most companies will have the recruit pass a phone screen before an onsite interview. But they want to be ready for both so they aren't scrambling when the call comes. The second reason they fail is that they get stuck on a problem and can't get out of it. This problem seemingly ruins the entire interview because then they begin to panic or simply give up. What they can do are to 1.) find a brute force solution 2.) fully understand the problem 3.) work through the problem by hand 4.) brainstorm different data structures and algorithms 5.) consider all the information they have been given 6.) simplify the problem 7.) breakdown the problem into subproblems 8.) take a step back 9.) collaborate with their interviewer, and lastly 10.) ask for help. The third reason software engineers fail their coding interviews is because they are too focused on getting the right answer that they forget to be themselves. To let their personality shine through so that the interviewer can see if they would fit in well with the office. Will they click or are they not a good fit? This is important even in the tech industry. Companies want to know that their current employees will mesh well with the new hire....and it should be equally important for the SE to want that as well. Lastly , many times the interviewee gets wrapped up in their own head. Thinking through the problem but not actually talking through the problem. This is a big concern for companies because they need to hear what they are doing and thinking. Simply talking as they work is a highly effective way of communicating their skill set and abilities. Tech recruiters can help their clients succeed and get the best offers by giving them resources to study and prepare. It's free to do, easy to send, and will pay back huge dividends in the long run when they get better offers from top tech companies. Read the full article