Interview Q&A

Pseudo-class: targets an element’s state.

hover { color: red; }

• Pseudo-element: targets part of an element.

p::first-line { font-weight: bold; }

• Follow me on LinkedIn:

Key Takeaway:

:hover changes behavior; ::before and ::after insert content.

Add the draggable="true" attribute and use drag events in JavaScript.

Example:

<p id="drag1" draggable="true" ondragstart="drag(event)">Drag

me!</p>

<script>

function drag(e) {

e.dataTransfer.setData("text", e.target.id);

}

</script>

Key Takeaway:

Use draggable="true" plus ondragstart and ondrop to enable drag-and-drop

functionality.

Semantic elements clearly describe their purpose in the document structure.

Examples include: <header>, <footer>, <article>, <nav>, <section>.

Example:

<article>

<h2>Breaking News</h2>

<p>New tech trends are emerging every day.</p>

</article>

Key Takeaway:

Semantic tags improve SEO and accessibility.

Answer: Hoisting is JavaScript’s behavior of moving variable and function declarations to the top of their scope during compilation. Example: console.log(a); // undefined var a = 5; Here, var a is hoisted but not initialized.

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

• <script> runs JavaScript.
• <noscript> displays content when JavaScript is disabled or not supported.

Example:

<script>

document.write("JavaScript is enabled!");

Follow me on LinkedIn:

</script>

<noscript>

<p>Please enable JavaScript to view this content.</p>

</noscript>

Key Takeaway:

<noscript> provides graceful fallback content.

Answer: Use the grid system and responsive classes: &lt;div class="col-12 col-md-6 col-lg-4"&gt;Responsive column&lt;/div&gt;

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Shallow equality: Compares only top-level properties. Deep equality: Compares nested values recursively. Example: {a:1} === {a:1} // false (different refs) Use libraries like Lodash’s _.isEqual() for deep comparison. Follow me on LinkedIn:

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Template literals allow embedded expressions and multi-line strings using backticks (`). Example: let name = "John"; console.log(`Hello, ${name}!`);

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

BEM is a naming convention for writing scalable and reusable CSS.

Structure:

.block__element--modifier

Example:

<div class="card card--featured">

<h2 class="card__title">Profile</h2>

</div>

Key Takeaway:

BEM enforces clarity:

• Block = independent component
• Element = part of a block
• Modifier = variation/state

Use @keyframes and the animation property.

Example:

@keyframes fadeIn {

from { opacity: 0; }

to { opacity: 1; }

}

.box {

nimation: fadeIn 2s ease-in-out;

}

Follow me on LinkedIn:

Key Takeaway:

@keyframes define the animation steps; animation applies them.

Answer: Using Flexbox: .parent { display: flex; justify-content: center; /* horizontal */ lign-items: center; /* vertical */ height: 100vh; } Key Takeaway: flexbox is the easiest and modern way to center elements.

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Semantic HTML elements (like <nav>, <main>, <form>, <button>) provide meaning to

content — making it easier for assistive technologies to navigate.

Example:

<nav aria-label="Main navigation">

<a href="#home">Home</a>

<a href="#about">About</a>

</nav>

dvantages:

• Better screen reader support
• Improved SEO
• Easier code maintenance

Key Takeaway:

Semantics = communication between developers, browsers, and accessibility tools.

Follow me on LinkedIn:

The <head> tag contains metadata — information about the document that isn’t displayed

on the page (like title, styles, or scripts).

Example:

<head>

<title>Portfolio</title>

<meta charset="UTF-8">

<link rel="stylesheet" href="style.css">

</head>

Follow me on LinkedIn:

Key Takeaway:

Think of <head> as your page’s control room.

Answer: Primitive types: stored in stack, immutable (number, string, boolean). Reference types: stored in heap, mutable (object, array, function).

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Specificity determines which rule wins when multiple styles target the same element. Priority order (lowest → highest):

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: bsolut Nearest positioned ncestor ✅ Yes Fixed Viewport ❌ No Example: div { position: absolute; top: 10px; left: 20px; } Key Takeaway: bsolute is relative to parent; fixed stays on screen. Follow me on LinkedIn:

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Predefined classes that handle spacing, display, text, alignment, etc. Example: &lt;p class="text-center m-3 p-2"&gt;Centered text&lt;/p&gt;

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

JS manages memory via automatic garbage collection.

Memory allocation happens when objects are created, and deallocation occurs when they’re

no longer reachable.

Example:

Creating large arrays without clearing references may cause memory leaks.

Answer: The rest operator ... collects multiple arguments into an array. Example: function sum(...nums) { return nums.reduce((a, b) =&gt; a + b); Follow me on LinkedIn: } console.log(sum(1, 2, 3)); // 6

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Transitions animate property changes smoothly. Example: button { background: blue; transition: background 0.3s ease; } button:hover { background: red; } Key Takeaway: Transitions are great for hover effects and simple UI feedback.

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Position Based On Moves with Page

Scroll?

Relative Its normal position ✅ Yes

Absolut

Nearest positioned

ancestor

✅ Yes

Fixed Viewport ❌ No

Example:

div { position: absolute; top: 10px; left: 20px; }

Key Takeaway:

Absolute is relative to parent; fixed stays on screen.

Follow me on LinkedIn:

Web Components are reusable custom elements built with:

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Use CSS or the HTML5 srcset and sizes attributes.

HTML Example:

<img

src="small.jpg"

srcset="medium.jpg 768w, large.jpg 1200w"

sizes="(max-width: 768px) 100vw, 50vw"

lt="Mountain view">

CSS Example:

img {

max-width: 100%;

height: auto;

}

Key Takeaway:

Responsive images adjust to different screen sizes for faster load and better UX.

Answer: Use the &lt;img&gt; tag with the src and alt attributes. Example: &lt;img src="images/photo.jpg" alt="A sunset at the beach"&gt; Key Takeaway: The alt attribute improves accessibility and helps SEO.

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: Values that evaluate to false in Boolean context: false, 0, "", null, undefined, NaN Example: if (!0) console.log("Falsy"); // prints "Falsy"

What interviewers expect

• A clear definition tied to JavaScript in JavaScript projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production JavaScript application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in JavaScript architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.