Sort by

HireCade Community

A public feed for interview, offer, and career questions

The feed above is where candidates and working professionals compare interview loops, sanity check offers, and work out what a hiring process really involves. This guide explains how the community is organised, how to ask a question that gets answered, what belongs in the feed, and how it fits with the courses and interview practice on the rest of HireCade.

What is the HireCade community?

The HireCade community is a public discussion feed where candidates and working professionals post about interviews, offers, hiring processes, and careers. Every post is filed under one topic: a company, a college, or a role. You can read and search the feed without an account, and you sign in when you want to post, comment, or bookmark.

The feed at the top of this page is the whole product. Sort it by Latest to see what people are posting right now, or by Popular to see the threads that drew the most attention. The search box looks across post text, topics, and hashtags, so a query like Amazon loop or system design round will surface earlier discussions instead of making you scroll.

The point of a topic-first feed is that answers stay findable. A question filed under a company topic sits alongside every other question about that company, so the next person interviewing there reads your thread months later. That is very different from a chat server, where a good answer scrolls away in an afternoon and nobody can search for it again.

The community at a glance

Cost: Free to read, free to post. No subscription and no paywalled threads.
Account needed: Reading and searching are open to everyone. Posting, commenting, and bookmarking need a sign in.
Topics: Every post belongs to exactly one topic, and topics are companies, colleges, or roles.
Post format: Text posts with a title of up to 120 characters and a body of up to 3,000 characters.
Comments: Up to 1,250 characters each, so replies stay focused on one point.
Sorting: Latest and Popular, plus full text search across posts, topics, and hashtags.
Hashtags: Pulled automatically from any word in your post body that starts with a hash symbol.
Your own history: My posts and Bookmarks are in the left sidebar once you are signed in.

How to ask a question that actually gets answers

Threads that go unanswered almost always share the same three faults: no context, several questions at once, and a title that does not say what is being asked. This is the order that fixes all three.

1
Search before you post
Type the company name, the round, or the exact phrase from your recruiter email into the search box above. Interview loops change slowly, so a thread from last quarter is usually still accurate, and reading it first means your question can start where that thread stopped.
- Search covers post text, topic names, and hashtags in one pass.
- If you find a close thread, add a comment there instead of opening a new post. Discussion stays in one place and the thread keeps ranking.
2
Pick the topic that matches your question
The composer asks for a topic before it lets you write, and the choices are companies, colleges, and roles. Choose the one a future reader would search for. A question about a specific company loop belongs under that company, not under a generic role.
- One post, one topic. If your question genuinely spans two companies, pick the one you are interviewing with and name the other in the body.
- Topics have their own pages, so the right topic puts your question in front of people already reading about it.
3
Write a title that is a question, not a label
You have 120 characters. Use them to state the actual question. Titles like Help needed or Interview tomorrow tell a reader nothing, so they scroll past. A title that names the company, the round, and what you want to know gets opened.
- Weak: Amazon interview question.
- Strong: Amazon SDE 2 phone screen, how much system design shows up before the onsite?
4
Give enough context to make an answer possible
The body holds 3,000 characters, which is roughly 500 words. Spend them on the facts an experienced person needs: your level, the role, where you are in the process, what the recruiter told you, and what you have already tried or already read.
- Say what you already know. It stops people repeating advice you have outgrown.
- Name your constraint. Two weeks of evenings gets a different answer than three months full time.
- If you are asking about a rejection, quote the feedback you were given rather than summarising your feelings about it.
5
Ask one question, and make it answerable
Threads that ask five things get one thin reply. Threads that ask one specific thing get several detailed ones. If you truly have five questions, post the most urgent one now and come back with the next after you have acted on the answers.
- Prefer questions with a checkable answer over questions that invite opinion. How is the Meta phone screen structured beats is Meta hard.
6
Add hashtags by writing them in the body
Any word in your post body that begins with a hash symbol becomes a hashtag automatically, and hashtags are searchable. A couple of accurate tags is plenty. Tag the round, the language, or the topic area rather than tagging everything you can think of.
- Useful: a tag for the round type and one for the technology. Not useful: ten tags that describe the same thing.
7
Come back and close the loop
This is the step almost everyone skips, and it is the one that makes the community worth reading. When your interview is over, return to your own thread and post what actually happened. That single comment turns your question into the resource the next candidate finds.
- Say which advice worked and which did not.
- Bookmark threads you want to revisit so you can find them again after your loop.

How topics organise the feed

Every post on HireCade belongs to exactly one topic, and the composer will not let you start writing until you have chosen it. Topics come in three kinds: companies, colleges, and roles. That single constraint is what keeps the feed useful as it grows, because it turns a stream of unrelated posts into a set of readable collections.

Company topics are where interview loops, offer decisions, team transfers, and recruiter behaviour get discussed. If you are preparing for a specific employer, the company topic is the first place to look, because the questions people asked before their loops tend to describe that loop more honestly than any official careers page does.

College topics carry the questions that come with starting out: which internships convert, how to talk about a project when you have no industry experience, what a campus offer is actually worth, and how to move from a first job into the one you wanted. Role topics cut across employers instead, so a backend engineer, a product manager, and a data analyst each have a place to talk about the work itself rather than the company doing the hiring.

Each topic has its own page, so you can read one collection at a time. Filing your post under the topic a future reader would search for is the single most useful thing you can do for its long term value, and it costs you nothing at the moment of posting.

Company topics: interview loops, rounds, levelling, offers, and recruiter process.
College topics: internships, campus hiring, first jobs, and turning coursework into interview material.
Role topics: the day to day craft of a job, career paths within it, and what interviewers for that role look for.
One post belongs to one topic. Mention the others in the body if the question genuinely spans them.

What belongs in the feed, and what does not

The community works when posts carry information someone else can use. That is a low bar and most posts clear it easily, but it does rule a few things out. A question with real context belongs here. So does an experience report, a comparison of two offers with the numbers included, a correction to something inaccurate that got upvoted, and a walkthrough of how you solved a problem you were stuck on.

What does not belong is anything written for someone other than the reader. Recruitment adverts dressed up as advice, referral link farming, the same post copied into five topics, engagement bait with no substance, and content generated wholesale by a chatbot all take from the feed without adding to it. So does anything that names and attacks an individual interviewer or candidate.

Confidentiality deserves its own line. Discussing the structure of an interview, the difficulty, the rounds, and how you prepared is normal and useful. Reproducing the verbatim text of a live take home assignment or a proctored assessment is not, because it puts the person who shared it at real risk and makes the question worthless for everyone who comes after. Describe the shape of a problem instead of pasting it.

Treat compensation numbers as facts, not as a competition. If you post an offer, say the level, the location, the base, the equity structure, and the year, because a number without those four things cannot be compared to anything. If you would rather see aggregated data than individual posts, the salary pages carry it in a structured form.

Good posts: specific questions with context, experience reports after the fact, corrections, and offer details with level, location, and year.
Not welcome: job adverts, referral farming, cross posting the same text to several topics, and chatbot filler.
Never post the verbatim text of a live assessment or take home. Describe the shape of the problem instead.
Attack an argument if you disagree with it. Do not attack the person who made it, and do not name individual interviewers.

How moderation and self correction work here

Moderation on a topic based feed starts with the people posting. Because every thread is attached to a company, a college, or a role, the readers who see it are usually the readers who know whether it is true. A confidently wrong claim about an interview loop tends to get corrected quickly by someone who sat that loop last month, which is a faster and better outcome than any moderator could produce.

So the norm we care about most is that you correct rather than pile on. If a post is inaccurate, reply with what is actually the case and say how you know. If a post is a duplicate, link the existing thread. If a post is a genuine question asked clumsily, answer the question the person meant to ask. That behaviour is what makes a community readable years later.

Content that exists to promote, to harass, or to leak protected material does not stay. Spam, personal attacks, doxxing, and verbatim assessment material are removed when we find them, and accounts that keep posting them lose access. Sign in is required to post or comment for exactly this reason: an account gives a post an author, and authorship is what makes a public feed self policing.

One practical consequence: assume everything you write is public and permanent. The feed is indexed, threads are linkable, and your posts are visible under My posts. If you would not want a future interviewer to read a post, do not write it. Talk about processes, rounds, and outcomes rather than about individuals, and you will never have to think about this again.

Correct inaccurate posts with a reply rather than reporting them by reflex.
Link the existing thread when you see a duplicate, so discussion consolidates.
Spam, harassment, doxxing, and leaked assessment material are removed.
Posts are public and indexable. Write as if a future interviewer will read them, because one might.

How the community actually helps a job search

Most job search advice online is generic because the person writing it does not know your target company, your level, or your timeline. A community fixes that specificity problem. The person who interviewed for your exact role at your exact target two months ago knows things no guide can tell you, and they are usually willing to say them if you ask a question worth answering.

The concrete wins fall into four buckets. First, calibration: reading three threads about a company loop tells you how many rounds there are, roughly what each one covers, and how long the process takes, which lets you plan your preparation instead of guessing at it. Second, levelling: knowing whether a title maps to a senior or a mid level band changes what you negotiate and what you prepare.

Third, failure diagnosis. When you get rejected with vague feedback, posting what happened often produces a specific reading of it from someone who has been on the other side of that panel. That is far more actionable than replaying the interview in your head. Fourth, timing. Threads about hiring freezes, team reorganisations, and reopened requisitions tell you when a company is actually hiring, which is information the careers page never carries.

None of this replaces preparation, and it should not be the largest slice of your week. Use the feed to decide what to work on, then spend the rest of your time doing the work: courses, interview practice, and a resume that survives a screen. The community is where you point your effort, not where the effort happens.

Calibrate the loop before you prepare for it: number of rounds, coverage, and timeline.
Check how a title maps to a level before you talk about compensation.
Turn vague rejection feedback into a specific diagnosis by asking people who run those panels.
Read for signals about when a team is genuinely hiring.

What to read first if you are new here

Start with the Popular sort. It surfaces the threads that drew the most attention, which is a rough but effective proxy for the questions most people share. Give it ten minutes and you will have a working sense of what this community talks about and how much detail a good answer carries.

Then search for your own target rather than browsing. If you have a company in mind, search its name and read the newest threads first, because processes change and a two year old description of a loop can be misleading. If you have a role in mind but no employer, search the role and read for how people describe the work, because that language is what you will need in your own interviews.

Once you have found threads worth returning to, bookmark them. Bookmarks live in the left sidebar and need a sign in, and they are the difference between a useful afternoon of reading and a useful reference you can come back to the night before a round. My posts, also in the sidebar, keeps your own questions in one place so you remember to close the loop on them.

Finally, post something. Reading is the smaller half of the value. The first time you write a real question with real context and get three specific answers, the community stops being a website you browse and starts being a resource you use.

Ten minutes on the Popular sort to learn the room.
Search your target company or role and read newest first.
Bookmark the threads you will want again before a round.
Post one real question with context, then come back and report what happened.

How the community connects to courses and interview practice

A community is good at telling you what to work on and bad at making you work on it. The rest of HireCade exists to close that gap, and the handover is usually obvious once you have read a few threads.

If the feed tells you that a loop is heavy on data structures, the beginner friendly DSA course covers the ground systematically and the Python for coding interviews course covers the language patterns those problems need. If the threads about your target are full of design rounds, the system design course for beginners is the structured version of what those threads describe in fragments. If your problem is that you know the material but freeze when asked to say it out loud, the AI interview practice pages are built for exactly that, and you can run a session in twenty minutes.

When you want a person rather than a model, the expert mock interview packages put you in front of an engineer or hiring manager who has run real loops, and you get feedback and a recording afterwards. When the blocker is earlier in the funnel and you are not getting screens at all, the resume builder and the salary pages are the right next stops instead.

The habit worth building is a loop: read the feed to find the gap, work the gap in a course or a practice session, then post what you learned. That last step is what turns your preparation into something the next candidate can use, and it is why the threads here get better every quarter.

Feed says the loop is algorithm heavy: work through the DSA and Python interview courses.
Feed says the loop is design heavy: work through the system design course.
You know the answers but cannot say them out loud: run AI interview practice sessions.
You want a human read on your performance: book an expert mock interview.
You are not getting screens at all: fix the resume first, then check salary and levelling data.

Community, AI practice, or a mock interview with an expert

These three do different jobs, and people who stall in a job search are usually over indexed on one of them. Use the feed to find the gap, then pick the format that closes it.

What you want	Community feed	AI interview practice	Expert mock interview
Best for	Finding out what a specific loop contains and how people prepared for it	Rehearsing spoken answers until they come out cleanly	A human read on your performance and a plan for what to fix
How long it takes	Minutes to read, and a reply can arrive any time	One session, budgeted at twenty minutes	A booked sixty minute session
What you get back	Answers and corrections from people who sat the same process	Written feedback and improvement suggestions at the end of the session	Feedback with concrete improvement areas, plus a recording of the session
Cost	Free	Free templates, and some templates use one credit	Paid packages
Account needed	Only to post, comment, or bookmark	Yes, and a working microphone and camera	Yes
Where to go	This page	The AI interviews page	The mock interview page

Credit costs and package contents are shown on the AI interviews and mock interview pages.

Community questions

Do I need an account to use the HireCade community?

No account is needed to read or search the feed. Every post and every topic page is public, so you can browse the whole community, use the search box, and switch between the Latest and Popular sorts without signing in.

You do need to sign in to post, to comment, and to use Bookmarks and My posts. Those three features are tied to an account because they are tied to you: a post needs an author, and a bookmark list needs somewhere to live.

How do I create a post?

Use the create post button at the top of the left sidebar. The composer asks you to choose a topic first, and it will not let you write until you have picked one. Search for the company, college, or role your question belongs to, select it, then write your title and body.

A post needs all three parts: a title, a body, and a topic. If any of them is empty the composer will tell you rather than publishing something unreadable.

How long can a post be?

Titles hold up to 120 characters, post bodies hold up to 3,000 characters, and comments hold up to 1,250 characters. In practice 3,000 characters is around 500 words, which is far more room than most questions need.

The limits exist to keep threads scannable. If your question genuinely needs more than 500 words of setup, it is usually two questions, and posting them separately gets you better answers to both.

How do topics work, and can I post to more than one?

Every post belongs to exactly one topic, and topics are companies, colleges, or roles. You cannot post the same thread to several topics, which is deliberate: cross posting splits the discussion and makes both copies less useful than one good thread.

Pick the topic a future reader would search for. If your question spans two companies, file it under the one you are interviewing with and name the other in the body.

How do hashtags work?

Hashtags are extracted automatically from your post body. Any word you write that starts with a hash symbol becomes a tag, and tags are searchable alongside post text and topic names.

Two or three accurate tags help people find your thread. Ten tags that all describe the same thing do not, so tag the round type, the technology, or the subject area and stop there.

What gets removed from the community?

Spam and job adverts, referral link farming, personal attacks, doxxing, and the verbatim text of live assessments or take home assignments. Accounts that keep posting those things lose access.

Almost everything else stays, including posts that turn out to be wrong. The better response to an inaccurate post is a reply that corrects it with specifics, because that correction is what the next reader needs.

Can I talk about my interview questions without breaking confidentiality?

Yes, if you describe the shape rather than reproducing the text. Saying that a phone screen was one medium graph problem followed by fifteen minutes of behavioural questions is useful and normal. Pasting the exact wording of a proctored assessment is not, and it is the one thing we remove on sight.

The same rule applies to take home assignments. Describe what the task tested, how long it took you, and what you would do differently, and you have given the next candidate everything they can act on.

Are community posts public and indexed by search engines?

Yes. Posts and topic pages are public web pages, so assume that anyone including a future interviewer can read what you write. Your own posts are also listed under My posts once you are signed in.

Write about processes, rounds, and outcomes rather than about individuals and this is a non issue. If you would not want a hiring manager to read a post, do not publish it.

Why did my question not get any answers?

Almost always because it did not give a reader enough to work with. Questions with no context, questions that ask five things at once, and titles that do not say what is being asked are the three common causes.

Rewrite it with your level, the role, where you are in the process, and what you have already tried, then ask one specific thing. Filing it under the right topic also matters, because a company question in a generic role topic reaches the wrong readers.

What is the difference between asking here and practising an interview?

The community tells you what to prepare. Practice makes you able to do it under pressure. Reading three threads about a company loop will tell you that there are four rounds and one of them is design, but it will not make you fluent at talking through a design out loud.

Use the feed to decide where your gap is, then close it with a course, an AI practice session, or a mock interview with an expert. Most people who get stuck are doing plenty of reading and almost no speaking.

Is the community free?

Yes. Reading, searching, posting, commenting, and bookmarking are all free, and there are no paywalled threads.

Other parts of HireCade are priced separately. Expert mock interviews are paid packages, and some AI practice templates use one credit while others are free.

How do I keep track of threads I want to come back to?

Bookmark them. The Bookmarks link in the left sidebar collects every post you have saved, which is what you want the night before a round when you are trying to find the thread that described the loop.

My posts, in the same sidebar, lists the questions you have asked. Use it to go back and post what actually happened after your interview, which is the single most useful contribution you can make here.

A public feed for interview, offer, and career questions

What is the HireCade community?

The community at a glance

How to ask a question that actually gets answers

Search before you post

Pick the topic that matches your question

Write a title that is a question, not a label

Give enough context to make an answer possible

Ask one question, and make it answerable

Add hashtags by writing them in the body

Come back and close the loop