What does a loop entitle? It means that at the very end, the last node does not point to a null pointer as the next node, but instead it points to a previous node, so you keep looping through a number of nodes.
In technical interviews, it is common that the interviewer will throw in a question that tests your knowledge of higher-order functions and function-binding.
This repository is an attempt to answer the age old interview question "What happens when you type google.com into your browser's address box and press enter?"
Understanding underlying logic of requirements is a fundamental skill for a programmer, because of the challenge of changing requirements. The requirements always change, but they often do so within an implicit logic.
This repo seeks to be an ever-improving starting point for technical interviewees when asked the question 'Do you have any questions for us?'.
There are a few questions which are deal breakers in case they are not answered correctly. These questions are quite simple, though fundamental. The candidates who cannot answer these questions, leave a bad impression.
People always complain about they can’t come up with the right solution. However good approach doesn’t come from nowhere. If you analyze the problem in the right direction, those smart answers should come to your mind naturally.
Wherein our lowly protagonist gets fed up with the state of software development interviews, and creates a new programming language which is particularly well-suited to implementing FizzBuzz.
In this post “Top 10 coding problems of important topics with their solutions ” are written. If you are preparing for a coding interview, going through these problems is a must.
“Whiteboard” interviews are widely hated. They also discriminate against people who are already underrepresented in the field.
If you want to get a job as a software witch, you’re going to have to pass a whiteboard interview. First, we need a linked list. Clear your workspace of unwanted xterms, sprinkle salt into the protective form of two parentheses, and recurse.
Long ago, on Svalbard, when you were a young witch of forty-three, your mother took your unscarred wrists in her hands, and spoke: "Vidrun, born of the sea-wind through the spruce / Vidrun, green-tinged offshoot of my bough, joy and burden of my life / Vidrun, fierce and clever, may our clan’s wisdom be yours: Never read Hacker News"
In the formless days, long before the rise of the Church, all spells were woven of pure causality, all actions were permitted, and death was common. Many witches were disfigured by their magicks, found crumpled at the center of a circle of twisted, glass-eaten trees, and stones which burned unceasing in the pooling water; some disappeared entirely, or wandered along the ridgetops: feet never touching earth, breath never warming air.
These are a sampling of questions I’ve asked and been asked when hiring frontend engineers. Keep in mind that some places (like Google) focus more on designing efficient algorithms.
Interviewing for technical positions is, in many ways, a balancing act. You look at past, present, and future; you look at soft skills and hard skills; you have to think as both a buyer and a seller; you even have to worry about company image and reputation management. There are some basic things you can do to keep that balance and best represent your company.
Everybody gives lip service to the idea that people are the most important part of a software project, but nobody is quite sure what you can do about it. The very first thing you have to do right if you want to have good programmers is to hire the right programmers, and that means you have to be able to figure out who the right programmers are, and this is usually done in the interview process.
This was a question that was asked in an Uber technical interview.