Interview questions for a novice web technologist/decoder

Question

css

Apart from the test task and portfolio, what questions can be asked to applicants applying for this position?

UPD: Thanks to everyone, I made something like this cheat sheet for myself:
HTML? CSS?
HTML5?
Specification? Who is developing it?
DOCTYPE?
class? id? what is the difference?
div? span? what is the difference?
jpg? png? gif? what's better?
BEM?
SASS? LESS?

reflow? repaint?

Answer 1

and if you try a hot corner in which Put display to sleep, then close the lid and open it again after a couple of seconds? Turns on?

Answer 2

1. What is position:relative, absolute, static? What is the difference?
2. What is overflow?
3. What is the difference between margin and padding?
4. Specificity of selectors .
5. How to embed custom fonts on the page? Should name font-squirrel and something similar + google fonts.

Answer 3

a counter question arises - why give 999999 tasks (as you say, in addition to the test and portfolio) to a beginner? everything that a person can do, you will see in the test work and portfolio. theory asking somehow... looks more like an attempt by a useless manager to be helpful.
Apparently, the test task was compiled incorrectly, since when viewing a candidate, you cannot understand anything from it about the skills of a recruit.

Answer 4

When I interview, I use these pages for inspiration :
darcyclarke.me/development/front-end-job-interview-questions/
www.impressivewebs.com/skills-front-end-developers/
passed:
isobar-idev.github.com/code-standards/

Answer 5

One question might be "what's the difference between a div and a span". It's funny, but some of the layout designers don't even know this.

Answer 6

I usually start interviews with layout types - for example, "there is a two-column layout, list all the ways to create it." This is a fairly broad topic, explaining which you can jump to a lot of similar questions - about floats, and about inline-blocks, and about the CSS Box Model, and so on. The question about the doctype is also one of the first, from the answer to this question, in fact, the impression of the interviewee as a specialist is built. Then comes a more or less general set of simple questions:
- CSS selectors, their specificity, support, performance;
- code organization (semantics, class names, clearfix, etc.);
— support for older versions of browsers, graceful degradation.
If a person copes with these questions confidently, I turn to BEM (usually, if a person is familiar with this, this abbreviation for this issue should have already been heard from his lips), CSS preprocessors, I ask a couple of questions about js - about vanilla and jQ. By this point, usually a person manages to talk about abstract topics like some articles by famous authors or reports from conferences that he read or watched, and which he relies on in his answers. This helps to further appreciate his skill, and not just a skill, but in general as a person who consciously writes good code, is interested in new trends, learns and improves his knowledge.

Answer 7

It is better to open some kind of layout and ask how he would lay it out, where would he place which blocks, what properties should they have, position, float, etc. Along the way, we will find out what methods of positioning he knows and other points.

Answer 8

The best layout designer in the company should conduct an interview for the position of a layout designer, this is my opinion. And he will already be able to determine what questions to ask by looking at the js and html code.
After all, even if, for example, they tell you what to ask, how will you know that you were answered correctly if the respondent does not understand the layout.