numankacar / interview-prep

:8ball: A collection of tips for interviews - for those who are looking for freelance gigs or employment

interview-prep

A collection of tips for interviews - for those who are looking for freelance gigs or employment

Tips for Interview

Sign up for any services the company provide as part of your research.

Be prepared to complete a Javascript task with the interviewer looking over your shoulder.

Competency questions

How has your project experience aligned to what we're trying to achieve?

What has been the most difficult application you've built?

What technology do you most want to learn next?

You're working in a project that involves two teams. If the other team criticizes your work, what happens?

What kind of manager are you looking for?

Wireframing

How have you gone from recording user stories to breaking them out into tasks to build?

Which wireframing tools have you used?

Management Questions

What's your experience with agile methodologies?

What do you expect from me as a scrum master?

How do you tend to organise tasks?

What's your development environment?

General Technical

What is a procedural programing language?

What is an object-oriented language?

What area of development are you most interested in? (planning, frontend, backend)

What happens when you go on a web page? (in terms of requests, server)

If you inherited a website and it was slow, how would you improve it?

Security

How can we best prevent script injections?

How would you make sure your application is secure against hackers or malicious attacks?

Databases

What are the different advantages of NoSQL and SQL databases?

What are the main threats to website security?

What does Map Reduce mean in databases?

How would you scale a socket?

Feedback on Technical Tests

There are certainly easier ways to pull information from the file system and attach it to routes than the route you seemed to take with Hapi (for example, there were a lot of files). In the logic itself, you could have just tried to read the path from the file system and handle the error if the file is missing, but you did a lot of processing to make sure you were requesting a valid file. I'm not saying there was anything wrong, it just could have been a little more elegant. (Discussing use of HAPI plugin architecture).

The project contains files / dependencies that are not used by the application, code is not tidy, unused variables, commented out blocks.