How do I approach Other / Miscellaneous interview questions?

Other / Miscellaneous questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master other / miscellaneous interviews.

What difficulty level is this interview question?

This is a hard difficulty Other / Miscellaneous question, commonly asked during Onsite rounds at DoorDash.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at DoorDash during technical interviews.

Implement Bootstrap-like responsive utility classes

Quick Overview

This question evaluates proficiency in front-end engineering, including CSS utility system design, responsive grid layout, semantic HTML, accessibility (ARIA and focus management), form validation, asynchronous submission patterns, and lightweight JavaScript for interactivity and telemetry.

Build a Bootstrap-like Utility System and Accessible Responsive Form (No External CSS)

Context

You are asked to create a minimal, reusable CSS utility system inspired by Bootstrap (grid, spacing, typography, components) without importing any external frameworks. Demonstrate it with an accessible, responsive page that includes a navbar, a layout using a grid, and a form with strong validation and error handling. Include minimal JavaScript to manage interactivity, validation, async submission, and telemetry.

Requirements

Utility classes (mobile-first):
- Container, rows, columns with gutters and support for nesting
- Breakpoints (e.g., sm, md, lg)
- Spacing utilities (m- , p- , directional variants)
- Typography helpers (e.g., text-center, text-muted)
Components:
- Accessible navbar with mobile toggle
- Buttons
- Form inputs with labels, helper text, and validation messages
Responsive grid:
- col- , col-sm- , col-md- , col-lg- (common fractions are acceptable)
- Gutters adjustable via utilities
- Show nesting
Accessibility:
- Proper semantics (nav, main, form)
- Label–control association
- aria-* for errors, aria-live for status
- Focus management and keyboard operability
Async form submission with robust error handling:
- Client-side validation (required fields, email format)
- User-facing states: loading, success, retryable error (e.g., network/5xx), non-retryable error (e.g., 4xx)
- Retry flow
- Telemetry for key events (start, success, failure, retry), using sendBeacon when possible
Deliverables:
- Provide the HTML, CSS, and minimal JavaScript in a single example that demonstrates responsiveness, accessibility, and error handling.

Quick Overview

Context

Requirements

Utility classes (mobile-first):

Container, rows, columns with gutters and support for nesting
Breakpoints (e.g., sm, md, lg)
Spacing utilities (m- , p- , directional variants)
Typography helpers (e.g., text-center, text-muted)

Components:

Accessible navbar with mobile toggle
Buttons
Form inputs with labels, helper text, and validation messages

Responsive grid:

col- , col-sm- , col-md- , col-lg- (common fractions are acceptable)
Gutters adjustable via utilities
Show nesting

Accessibility:

Proper semantics (nav, main, form)
Label–control association
aria-* for errors, aria-live for status
Focus management and keyboard operability

Async form submission with robust error handling:

Client-side validation (required fields, email format)
User-facing states: loading, success, retryable error (e.g., network/5xx), non-retryable error (e.g., 4xx)
Retry flow
Telemetry for key events (start, success, failure, retry), using sendBeacon when possible

Deliverables:

Provide the HTML, CSS, and minimal JavaScript in a single example that demonstrates responsiveness, accessibility, and error handling.

Implement Bootstrap-like responsive utility classes

Quick Overview

Build a Bootstrap-like Utility System and Accessible Responsive Form (No External CSS)

Context

Requirements

Solution

Comments (0)

Implement Bootstrap-like responsive utility classes

Quick Overview

Build a Bootstrap-like Utility System and Accessible Responsive Form (No External CSS)

Context

Requirements

Solution

Comments (0)