kottans / kottans/kottans-ongoing-projects

Tech Interview Prep/LeetCode Study Group

Open
#52 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
32
Forks
1
PR merge metrics
No merged PRs in 30d

Description

This issue is about

  • Course
  • Conference
  • Workshop
  • Meetup
  • Project
  • Other -- Study Group

By/for

  • kottans
  • non-kottans

Subject: A study group to do LeetCode-like problems twice+ a week.

Term/duration:
Duration:

  • Indefinite duration, but see if the incentive can last the month of June.
  • Twice a week. Tuesdays, Thursdays + Saturdays, if you're willing. Starting June 1st.
  • The schedule is flexible at the moment and can be discussed and adjusted depending on people joining.

Location:

  • Kyiv (Right bank, precise location TBD).
  • We can book space at local coworking spaces or study at a chill local coffee shop (e.g., Kharms at Golden Gates). Open to suggestions.

Keywords:
leetcode, study group, interviews, interview prep, algorithms, data structures, programming problems

General description:
I am a Python backend developer actively studying for FAANG-style tech interviews. Most of my current preparation is doing LeetCode-like problems every day. I am seeking enthusiastic people who want to do programming problems together, share knowledge, tips, tricks, approaches -- or just be there to hold each other accountable.

I will not act as a teacher or mentor, since I am fairly new to competitive-style programming problems and have a lot to learn. I have, however, accumulated a fair amount of tips and methods.
This is an accountability partnership / knowledge-sharing offer.

Your skill level or job status does not matter to me, as long as you have a beginner/intermediate-level knowledge of at least one programming language. (You've written functions and classes, and have the surface knowledge of data structures like queues or heaps -- or at least actively willing to learn about them). I prefer Python, but you can pick whatever floats your boat. Problem-solving is language-agnostic at its core.

You do want to hang out with me if you're interested in at least one of the following:

  • ramping up your problem-solving skills together
  • learning competitive/whiteboard coding together
  • studying algorithms/data structures/systems design to become better at your job or university studies
  • getting a prestigious programming job
  • all of the above, and, just like me, find it hard to stay motivated alone

I tend to do preparation based on cherrypicked problems instead of blindly going through LeetCodes. Study outline will involve the following resources you're free to finish at your own pace.
Presently, I need a study group to finish and review these 3 things:

  • Blind 75
  • AlgoExpert -- 155 problems, I'm willing to share access to it during our Study Group sessions and link you to corresponding LeetCode problems, so you can do it on your own.
  • Grokking the Coding Interview -- also willing to share access, though I highly recommend you buy your own copy for studying outside of our meetings.

I'm halfway through AlgoExpert, and I genuinely promise you, it's a lot of work, especially if you're just starting out. But if you're willing to stick with me, we are going to level up together.

Ping me on Telegram if you're interested or leave a comment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue body and its Blind 75, AlgoExpert, and Grokking the Coding Interview links; no repository files or tests are identified. Contact the proposer through Telegram or a comment to determine whether the study group is still wanted, then confirm a schedule and participants if the activity is revived.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.