Common Web Developer Interview Questions And Answers
blog.codegiant.io
blog.codegiant.io
1. 99.99% of candidates sound extremely nervous for the first few minutes. That’s fine. I think most interviewers expect it. Both the interviewer and the interviewee want to calm down, and a few min of introductory chat seems to help most people.
2. If I notice a candidate is nervous in the middle of a technical question, I try to say something to calm them down. Often people seem super nervous while doing well/sometimes people confidently do badly — Point is that nerves are not a sign that the candidate is bad, but rather a sign the candidate might be able to do better/be happier if they were calmer.
3. At least if you were interviewing with me, I’d hope candidates who feel too nervous tell me they are nervous. Maybe other interviewers wouldn’t take kindly to this, but if it leads to better/happier hiring then I’m all for it. FWIW this has only happened a handful of times in my career.
A lot of nerves come from the unknown. In an interview you could be asked pretty much anything. In my opinion, interviews should be about relevant experience and talking through a problem that was given to the interviewee before hand. I really wish I knew which companies did interviews like that near me.
There's a ton of interviewers who are on a power-trip would would potentially take an admission of something like that as a yellow or red flag. In engineering/business there's a ton of folks who have huge egos and love to rip into candidates for stuff that's small to insignificant.
Then there's the legitimate "that may just weed you out" thing. I have had to hire engineers who I know can deal with tough social situations with grace. Someone admitting openly that they're nervous in an interview isn't necessarily someone who I'd trust going glove-to-glove with execs who will bend your arm to get their way.
Anywho - maybe my reasons aren't the right ones (and they're surely not universally applicable)... but I'd absolutely not give someone the advice to show that card on the interviewee side of the table.
If I were interviewing someone, I would expect the linear solution and from a CS graduate would at least expect mentioning the logarithmic one..
Also why stop there? An actual smart coder would have looked up the constant time solution instead of bothering with any of that.
defmodule Fibnoc do
def fib(0), do: []
def fib(1), do: [0]
def fib(2), do: [1 | fib(1)]
def fib(n) when n > 2 and is_number(n) do
[a, b | _] = rest = fib(n - 1)
IO.puts("a: #{a} b: #{b} rest: #{inspect(rest)}")
[a + b | rest]
end
end
That's what I mean tho. In high school, they start leetcode practice from day 1 of programming or CS classes. Soon, you will get many leetcoders in the market.
> How does implementing Fibonacci weed out people who can't program at all?
There are many people applying for jobs who can't program a buzz fizz. They exist. A fibonacci is enough to throw them off in an unfamiliar language.
AJAX first appeared in 1999 [0], when people still ate Olestra and used pagers.
Who wrote this article again? An HR?
The section on 'How do you organize your class modules and assets?' doesn't contain any useful information at all.
It even defines AJAX and Big-O notation for us. Who's the target audience here? Someone trying to impersonate a knowledgeable web developer?