r/cscareerquestions
A large Reddit community where people starting or already in software careers share interview experiences, timelines, offers and rejections, and ask for advice on job hunting, career changes and workplace problems. It is one of the few public places to see what a hiring process actually looks like right now. It suits anyone calibrating expectations about a company or the job market, read in limited doses.
Free
Reddit · Sept 2026
Community
Interview Prep
Ongoing
All
Free
What it is
r/cscareerquestions is one of the best-known communities for people entering or working in software and computer science careers. Posts range from "I got an offer, should I negotiate?" to detailed write-ups of interview loops, layoff news, and questions about switching careers or countries.
Much of the discussion reflects the US market, so check whether advice applies where you are applying; some countries have their own regional career communities.
What it is good for
- Ground truth on process. How long a company takes between stages, what the phone screen actually contained, whether an offer was negotiable, what a level means in practice. That information rarely exists anywhere official.
- Negotiation and offers. Many posts compare offers and discuss what worked in negotiation.
- Career questions that interview resources do not cover: staying or leaving a first job, moving from support or QA into development, returning after a break.
- Searching past threads. Most questions have been asked before; searching the subreddit for a company name plus "interview" often finds recent experiences.
How to read it carefully
Communities like this skew towards extremes. A smooth, ordinary process rarely gets posted about, and a disaster always does. During downturns the mood can become very negative, which does not reflect every market (and US conditions may be very different from the market you are applying in).
- Treat individual posts as anecdotes and look for the same point repeated across many posts before believing it.
- Salary figures and timelines are more reliable than the sentiment around them.
- Check the post date; hiring conditions change quickly.
- Be wary of confident advice from accounts with no history.
The failure mode to avoid
Reading it instead of preparing. It is easy to spend an evening absorbing other people's anxiety and mistake that for progress. Set a time limit and a purpose, such as "find three recent posts about Company X's onsite".
How to participate well
- Read the rules and any weekly or pinned threads before posting; many simple questions belong in those threads.
- When asking for advice, give context: your experience, location, target roles and what you have tried.
- When you finish a process, post your own experience. It is how the community stays useful.
Pair it with
For structured preparation, use dedicated resources (the Tech Interview Handbook, NeetCode, company interview guides). For salary data, sites such as Levels.fyi aggregate reported compensation more systematically than threads do.
Best for: calibrating expectations about a specific company or a current market, in limited doses.
Ready to start?
Opens on Reddit in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.