DEV Community

8 Ultimate Full Stack Interview Questions and Answers

Alex 👨🏼‍💻FullStack.Cafe on July 15, 2018

A Full-Stack Web Developer is someone who is able to work on both the front-end and back-end portions of an application. Front-end generally refer...
Collapse
 
antonfrattaroli profile image
Anton Frattaroli • Edited

Was asked recently: "say you type 'google.com' into a browser address bar and hit enter, what happens sfter that?"

They stopped me after 10 minutes of straight talking, seemingly safisfied. I'm still thinking of things I didn't get a chance to say. gzip

Collapse
 
theodesp profile image
Theofanis Despoudis

Even though you can study and learn what's happening when you do that, it doesn't mean that you know how to code. This is knowledge that is taken by standing over the shoulder of giants. The real deal is to actually implement part of the request/response cycle and really understand what really happens.

Collapse
 
antonfrattaroli profile image
Anton Frattaroli

Or a more common case: it's already implemented, now debug it.

Collapse
 
manzanit0 profile image
Javier Garcia

And what happens after that? I have some concepts, but I doubt I'd be able to explain it all lol

Collapse
 
vasilvestre profile image
Valentin Silvestre

Tell us please

Collapse
 
antonfrattaroli profile image
Thread Thread
 
albinotonnina profile image
Albino Tonnina

You can break the Internet!

Collapse
 
elmuerte profile image
Michiel Hendriks

These are all fact checking questions. None of them test if the person know how to wield the knowledge.

For example, a better question would be: Present an example where you would use an event loop.

Collapse
 
zenmumbler profile image
zenmumbler • Edited

Exactly; if you are a candidate in an interview and are presented with questions like these, you are fully in your right to answer "Let me google that for you."

IMO, the Bridge pattern especially (from the C++ "gang of four" patterns book) should only be considered in cases where the existing team has gone full-in on deep inheritance and have dug themselves an accordingly sized hole. Please do not feel bad if you do not know what that pattern is.

Collapse
 
baamenabar profile image
B. Agustín Amenábar Larraín

Is it ok if I use the pattern often, but had no idea how it was called? or it doesn´t count?

Thread Thread
 
zenmumbler profile image
zenmumbler • Edited

I feel that if you already used this naturally, that is before you had to because you've made a 5-level deep, 20+ class wide hierarchy of doom, then all is well, because you're already keeping things nicely separated. The part I'm not fond of is the underlying motivation for inclusion in the patterns book, namely: "now that you've written hundreds of classes using inheritance, let's make it a bit easier" An inversion of code design, if you will.

Collapse
 
okolbay profile image
andrew

“You have inverted control by handing the responsibility of instantiating“

Its not in wikipedia definition of IoC, but by just letting framework wire-up code you haven’t inversed control too much. You can inject mock in unit tests now, but specific implementation (maybe from a different package) is still there. What I see as IoC is when you declare interface in module you want to be in control of the contact.

Collapse
 
bgadrian profile image
Adrian B.G.

At that seniority level these questions were asked in real interviews?

Collapse
 
mixoglad profile image
Mish

This is helpful. Thanks

Collapse
 
Sloan, the sloth mascot
Comment deleted