πŸ™
Frontend Dev Guide
  • ⚑Read Me First
  • πŸ“–Frontend Interview Guide
    • πŸ’¬Technical Behavior
      • Frontend Interview Questions
      • Answering Interview Questions
    • πŸ’»Coding Challenges
      • Frontend Code Challenges
      • Data Structures and Algorithms
        • Binary Search Tree
        • Blind 75 and Neetcode
      • Take Home Assignments
    • πŸ•ΈοΈFrontend System Design
      • What is Frontend System Design?
        • Parts of the Frontend System Design
          • 1) Gather Requirements
          • 2) Architecture/High Level Design
          • 3) Data Model and Flow
          • 4) API
          • 5) Optimization and Deep Dive
        • Example: Design Spotify
  • πŸ”¦Frontend Deep Dive
    • πŸ₯žMicrofrontends
    • 🧩Fundmentals
      • πŸ”΅Cross Browser Compatibility
    • πŸ“šFrameworks/Libraries
      • 🟒Vue
      • πŸ”΅React
        • Waterfalls, Unidirectional Data Flow
        • React Server Components
    • 🏁Patterns
      • 🟑Design Patterns
      • βšͺRendering Patterns
      • 🟣Performance Patterns
    • πŸ”‹Performance
      • βšͺNetwork Optimizations
      • 🟠Build Optimizations
      • 🟣Asset Optimizations
      • πŸ”΅Core Web Vitals
  • 🐍Python
    • βšͺDjango
      • Classbased Views (CBV)
      • Cross-Site Request Forgery (CSRF)
  • πŸ—»Working Life
    • 🟣Technical Communication
  • πŸ“šGlossary
  • πŸ’‘Resources
  • πŸ‘©β€πŸ’»About Me
Powered by GitBook
On this page
  1. Frontend Interview Guide
  2. Coding Challenges

Data Structures and Algorithms

Algorithms that are typically seen for generalist software engineer roles

PreviousFrontend Code ChallengesNextBinary Search Tree

Last updated 2 years ago

Frontend developers as with any other software engineer role should know basic data structures and algorithms. A high level understanding of basic computer science concepts is foundational to becoming a better engineer. However, it also helps with problem solving in any programming role.

It's not surprising there will be at times interview loops that involve traditional algorithms mainly to test whether a candidate has the basic foundations to solve problems algorithmically.

Typically sites like leetcode.com or hackerrank have been popular for practicing and finding solutions to common algorithm problems that may often be found asked by different tech companies.

has a great breakdown of the different patterns that make up the common groups of algorithms that may be seen during software engineer interviews.

Generally what I've seen useful has been a focus on the following types of patterns/groups:

Commonly Seen
Least Commonly Seen

Arrays and Hashmaps

Graph

Two Pointers

Dynamic Programming

Sliding Window

Backtracking

Search/Sorting

Linked List

Tree

πŸ“–
πŸ’»
Neetcode's site