---

Documentation

This is well documented and maintained at the Read the Docs.

Follow the link https://interview-docs.readthedocs.io or click the image below to read the Complete Interview Docs

Community

Gitter Community

All the discussions related to the Interview and Data Structures and Algorithms are discussed on the Gitter Community Channel.

Follow the link https://gitter.im/data-structure-and-algorithms/community or click the Gitter Logo on the left to join the community

---

Contents

• Data Structures

  • Abstract Data Type
  • Computational Complexity Analysis
  • Array
  • Linked List
  • Tree

• Algorithms

  • Array

    • Boyer Moore Majority Vote Algorithm

  • Linked List

    • Floyd's Tortoise and Hare

  • Searching

    • Searching

  • Sorting

    • Sorting

• Interview Preparation

  • Interview Preparation
  • Networking

• Solution of Books

  • CLRS
  • Cracking the Coding Interview
  • Elements of Programming Interviews

• Programming Languages

  • Python

• Competitive Coding

  • Codechef

    Cookoff	Long Challenge
    Easy

  • Codezforces

    Div 2	Div 3
    April Fools Day

  • HackerEarth

    Circuits	CodeArena

  • HackerRank

    • Contest : MentorshipKarona Webinar by Vinit Shahdeo

  • Leetcode

    array	hash-table
    binary-search	linked-list
    binary-search-tree	math
    bit-manipulation	minimax
    Contests	mock
    databases	stack
    Geometry	string
    greedy	tree
    April '20 Challenge	May '20 Challenge
    June '20 Challenge	July '20 Challenge
    August '20 Challenge

Resources

Books

• CLRS
• Cracking the Coding Interview
• Elements of Programming Interviews

Competitive Coding

• Codechef
• Codeforces
• HackerEarth
• HackerRank
• Leetcode

Online Study Materials

• Free Code Camp
• GeeksforGeeks

---

Issues

1. Graph Algorithm
2. Solutions of CLRS
3. String Algorithms

NOTE: Feel free to open issues. Make sure you follow the Issue Template provided.

Contribution Guidelines

• Write clear meaningful git commit messages (Do read this).

• Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (Check this for more info)

• When you make very very minor changes to a PR of yours (like for example fixing a text in button, minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at here)

• When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.

• Please follow the PR Template to create the PR.

• Always open PR to develop branch.

• Please read our Code of Conduct.

• Refer this for more.

Contributor

• Aditya Raman : www.ramanaditya.com
  • LinkedIn : https://www.linkedin.com/in/ramanaditya/
  • GitHub : https://github.com/ramanaditya
  • LeetCode : https://leetcode.com/ramanaditya/
  • CodeChef : https://www.codechef.com/users/ramanaditya
  • HackerEarth : https://www.hackerearth.com/@ramanaditya
  • HackerRank : https://www.hackerrank.com/ramanaditya

If you like this repository, support it by star 🌟

Community	Documentation	Source Code
Gitter	Read the Docs	GitHub
Join Now	Read the Docs	View Code