The first interview was relatively easy, with all the trivial questions others have already mentioned: what port is used for HTTP, what does SSL stand for, and what is the difference between GET and POST.
On the second interview, I was asked to code FizzBuzz, create a simple code for caching values (I used an array where the key is md5(value)), and set a timer in JavaScript.
Some questions will be dynamic; they will ask you to code something easy and then ask you to modify it, for instance, to handle a slightly different task or dataset. The interviewer was really nice; we chatted about our favorite programming books.
In the first interview, they asked me a few questions about the "number of digits needed to code an octet" and other bits and bytes topics. I failed these questions, but it didn't seem to affect the first interview much, and I was still passed to the second one.
The following metrics were computed from 4 interview experiences for the Yelp Software Engineer (Web Developer) role in United States.
Yelp's interview process for their Software Engineer (Web Developer) roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Yelp's Software Engineer (Web Developer) interview process in United States.