Technical Interview Questions Someone might ask you

Technical interviews can be stressful at times, and some questions can catch you off guard. Here is a list to help you prepare for the technical interview, and hopefully you’ll feel more at ease knowing how to answer them!

Types of questions:

  1. Trivia
  2. CS/Algorithms
  3. Problem Solving

For now, let’s start off with something really simple. Trivia-type questions. The type of questions you either have memorized or you can easily google. A few of those include:

— — — — — — — — — — — Trivia — — — — — — — — — —

  1. What does HTTP, HTTPS, FTP stand for, and what port number do they use?

HTTP = Hypertext Transfer Protocol, 80

HTTPS = Hypertext Transfer Protocol Secure, 443

FTP = File Transfer Protocol, it uses a pair of connections between the FTP client and FTP server. The FTP server’s port is 20, and the FTP client’s port is 21.

2. What type of programming language is X (where X is the language you know best).

For example:

Ruby - a dynamic, reflective, object-oriented, general-purpose programming language.

Javascript - a multi-paradigm language meaning it’s scripting, object-oriented (prototype-based), imperative, and functional

Python - an interpreted, object-oriented, high-level programming language with dynamic semantics.

3. What are the steps my computer takes between me typing in a URL and seeing a rendered page?

  • A request is sent out from your computer to a Domain Name System (DNS) server to find the IP address of the domain name you typed in.
  • A Hypertext Transfer Protocol (HTTP) GET request is sent from your computer to the server for that IP address.
  • The server for that IP address sends back data which your browser interprets and renders it to the page.
  • Now you have a functioning website to view.

4. What are the Hypertext Transfer Protocol (HTTP) methods and their corresponding CRUD Operation?

CRUD (Create, Read, Update, Delete) - the four basic functions of persistent storage

5. What does MVC stand for?

The Model, View, and Controller is an architectural pattern that separates an application into three main logical components.

Model - contains the data-related logic, such as the business logic or the data that is being transferred between the View and Controller components.

View - contains all the User Interface logic for the application. It renders the content to the user and transfers the user commands to the Controller.

Controller - interacts with the Model to create or manipulate data for the View in order to render the final output.

Come back next week for a list of CS/Algorithms questions and answers!