Coding Interview Prep

A daily problem, two-seat mock interview rooms, a system-design forum, private resume review and an offers board.

9 categories
31 channels
11 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

LOBBY

prep-lobby
New members land here. Pick your tracks, read how this works, do today's problem.
prep-announcements
Mock weeks, guest interviewers and changes to the routine. Hosts only.
how-this-works
Solutions go behind spoilers, mocks happen in the two-seat rooms, feedback is specific and kind.
pick-your-tracks
Grab Algorithms, System Design, Frontend or Data Engineering, and Mock Partner if you will interview others.

DAILY PROBLEM

daily-problem
One problem each morning. Discuss the approach in the thread; full code goes in #daily-solutions.
daily-solutions
Full solutions behind spoilers, with the complexity stated. Reply in threads.
patterns-and-tricks
Sliding window, two pointers, binary search on the answer. One pattern per message with an example.

ALGORITHMS

arrays-and-strings
Hashing, prefix sums, sorting tricks and the string questions that hide a pattern.
trees-and-graphs
Traversals, shortest paths, union find and the recursion nobody trusts.
dynamic-programming
State, transition, base case. Say which you are stuck on.
time-and-space-complexity
Is this O(n log n)? Post the code and the argument.

SYSTEM DESIGN

system-design
One design question per thread. Requirements first, then the diagram, then the trade-offs. Tag the shape.
design-resources
Papers, talks and write-ups on real systems, with one line on what to take from each.

MOCK INTERVIEWS

mock-signups
What kind of interview, what level, when. Ping Mock Partner if nobody replies.
mock-feedback60s slowmode
The interviewer's notes after each mock: what went well, what to fix, one thing to practise.
Mock Room 1
Mock Room 2
Mock Room 3
Whiteboard Session

CAREER

resume-review
Post your CV here. Only hosts and helpers can read it; feedback comes back in a thread or a DM.
applications-tracker
Where you applied and what stage you are at. No company drama.
behavioral-questions
Tell me about a time. Story structures, what to prepare, what interviewers listen for.
negotiation-tips
Offers, counters and what people wish they had asked.

WINS

offers-and-wins
Got the offer, passed the onsite, cleared the screen. Say what the process was.
rejections-and-lessons
What was asked and what you would do differently. Company optional.

LOUNGE

water-cooler
The open room for everything that is not a problem or a job.
AFK

HOST ROOM

host-chat
Who posts tomorrow's problem, who has been harsh in mock feedback.
mock-partner-vetting
Who has asked for Mock Partner and whether their feedback so far earns it.
prep-logsHidden from @everyone
Vetox posts joins, role changes and moderation here.
Host Voice

Roles

HostAdministrator
Co-HostModerator
HelperModerator
Mock Partner
Member
Algorithms
System Design
Frontend
Data Engineering
Muted

Overview

A peer server for people preparing for software engineering interviews together, with no instructor: a host, a few helpers and members who take turns being the interviewer. DAILY PROBLEM is the routine: #daily-problem is posted by a host or helper each morning and discussed in threads, #daily-solutions is where full solutions go behind spoilers, and #patterns-and-tricks collects the sliding-window and two-pointer style patterns that keep coming back. ALGORITHMS is split by topic, #arrays-and-strings, #trees-and-graphs, #dynamic-programming and #time-and-space-complexity. #system-design is a forum where each design question is a thread tagged by its shape, read-heavy, write-heavy, realtime or storage, with #design-resources beside it. MOCK INTERVIEWS is the part that needs a server: #mock-signups pairs people up, Mock Room 1 to 3 are two-seat voice rooms so an interview is never walked in on, Whiteboard Session is the open room for screen-shared walkthroughs, and #mock-feedback is where the interviewer writes up what they saw. Mock Partner is a mentionable role for members willing to interview others. CAREER holds #resume-review, a drop box where a member posts a CV that only hosts and helpers can read, plus #applications-tracker, #behavioral-questions and #negotiation-tips. WINS has #offers-and-wins and #rejections-and-lessons, because both are data.

When to use it

Your interview prep group is a chat where the daily problem is lost by lunchtime, mock interviews get interrupted by whoever joins the voice room, and someone posted their CV where every recruiter-adjacent stranger could read it. This layout gives the daily problem its own read-only channel with threads, capped mock rooms that seat exactly two, a resume channel only hosts and helpers can read, and a design forum that keeps each question as one thread.

What makes it different

Mock Room 1 to 3 are two-seat voice rooms, so an interview is never joined by a third person.
#resume-review is a drop box: members post a CV that only hosts and helpers can read.
#daily-problem is host-posted and discussed in threads, so it is still visible at the end of the day.
#system-design is a forum tagged by question shape, so read-heavy designs are one filter away.
Mock Partner is a mentionable role, so finding an interviewer is one ping instead of a plea.

Recommended Vetox setup

Reminders
Schedule a Reminder in #daily-problem each morning so the host never forgets, and one in #mock-signups on Sunday to fill the week's slots.
Streaks
Turn on Streaks for thread replies under #daily-problem so solving daily becomes a run members protect.
Self-Roles
Post a Self-Roles panel in #pick-your-tracks for Algorithms, System Design, Frontend, Data Engineering and Mock Partner.
Temp Voice
Point Temp Voice at Mock Room 1 with a two-person limit so a fourth simultaneous mock gets its own room.
Leveling
Give Helper as a Leveling role reward at a level that takes a couple of months of daily problems and mock feedback.

Questions

How do mock interviews get arranged?

Post in #mock-signups with the kind of interview you want and a time, or ping the Mock Partner role. Take one of the two-seat Mock Rooms, and afterwards the interviewer writes their notes in #mock-feedback so the candidate has something to work on.

Who can see my CV in #resume-review?

Only the host, co-host and helpers. Reading the history is denied for everyone else, so you post it and nobody but them can scroll back to it. Feedback comes as a reply in a thread you can see or in a direct message.

Why is there a rejections channel?

Because a rejection with the interview questions attached is more useful to the next person than an offer. #rejections-and-lessons is for what was asked and what you would do differently, with the company named only if you are comfortable.

Common mistakes

Letting mocks happen in an open voice room, where a third person joining ends the interview.
Posting full solutions in the problem channel, so everyone who opens it after lunch has the answer before the question.

Consider instead

Certification Study Group The goal is a certification exam with fixed objectives rather than live coding interviews.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages