What Are Codinzhub Company Guides? A Detailed Walkthrough
Learn what Codinzhub company interview guides are, how they are researched, what each section contains, how they differ from the question bank, and how to use a guide to prepare for a real OA and interview loop.
On this page
If you are preparing for a campus drive or an off-campus interview, the first problem is not practice — it is knowing what actually happens in that company's process. How long is the online assessment? Do they test DSA, SQL or system design? Is there a group discussion? What do interviewers actually ask in HR?
Codinzhub company guides answer those questions on one page. There are 140 guides covering 60+ companies and roles, all free to read on the blog.
In this guide
- What a company guide is (and is not)
- Why we built them alongside the question bank
- What each section of a guide contains
- How the questions are sourced and verified
- Guides vs question bank vs company pages
- How to find and use a guide
The short answer
A company guide is a researched interview playbook for one role at one company. It maps the real hiring process stage by stage — application, shortlisting, online assessment, technical rounds and HR — using questions that candidates actually reported. Every question is a verbatim report or a faithful paraphrase of a real account. Nothing is invented to fill a round, and there are no calendar-based study plans.
Start with the 30-second summary, jump to the round you are preparing for, then follow the practice links on that page.
Why we built them
Codinzhub already had two useful pieces:
- The question bank at Problem Set tells you what was asked.
- A company page such as BNY collects the raw questions and interview experiences candidates shared.
What was missing was the connective tissue: in what order do stages happen, what changes by level, and which questions belong to which round? Guides fill that gap. They turn scattered reports into a single map you can actually study from.
What is inside a guide
| Section | What it gives you |
|---|---|
| 30-second version | The whole process in one paragraph: OA format, round count and the one habit that matters most. |
| Level differences table | How intern, new-grad and experienced loops differ, instead of mixing them into one vague answer. |
| Round-by-round breakdown | Each stage with its length, question count, common topics and what candidates reported. |
| Sourced question tables | Real questions with the round, level, year and source label shown next to them. |
| Codinzhub practice links | Links to the company's question hub, a company-filtered OA search and related guides. |
| Searchable question bank | When a guide has five or more sourced questions, the site renders a filterable bank above the appendices. |
| Next-round playbook | Concrete actions candidates used to clear the OA, the loop and the final round. |
| FAQ and "About this guide" | Straight answers to common doubts and a note on how the guide was built. |
| Keep preparing | Links to that company's questions, OA question search and three role-matched guides at other companies. |
You can see all of this in a complete guide such as AMD Software Engineer or Paytm SDE 1.
How the questions are sourced
The research workflow is deliberately strict:
- Collect internal candidate records shared on Codinzhub and public first-hand write-ups.
- Keep only first-hand accounts with a described round; marketing pages and second-hand summaries are excluded.
- Deduplicate near-identical reports and merge different spellings of a company name.
- Attach a source label and year to each question so you can judge how current it is.
- Never fill a gap with an invented question. If a round has fewer than five distinct sourced questions, the guide is labelled
[Draft]and the gap is disclosed.
That is why two guides for the same company can look different: they cover different roles or levels, and the evidence base for each is different.
Guides vs question bank vs company page
| Resource | Best for | Example |
|---|---|---|
| Company guide | Understanding the whole process and what to expect in each round | Deloitte Data Analyst |
| Question bank | Drilling hundreds of OA problems by company, topic and difficulty | Browse questions |
| Company page | Reading the newest raw questions and experiences as they arrive | BNY questions and experiences |
| OA papers | Seeing an actual past question paper format | Premium resources |
Use them together: read the guide first, practise from the question bank, then check the company page for anything newer.
How to find a guide
Every guide has a stable URL:
/blog/guides/<company>/<role>
Examples:
- AMD Software Engineer
- BNY Software Engineer
- Deloitte Data Analyst
- PayPal SWE Intern
- Kuku FM AI Generalist — a draft, so treat it as partial
You can also open the blog and use the company categories. Each guide ends with related guides at other companies, so one guide naturally leads to the next.
A practical way to use a guide
- Read the 30-second version. If it does not match the role you are applying for, check the level table or pick another guide.
- Map your stage. Find the round you are preparing for and read only that section first.
- Check the length and topic mix. A 90-minute MCQ-plus-coding OA needs different practice from a whiteboard design round.
- Follow the practice links. Open the company's OA question search and solve the patterns named in that round.
- Use the company page for freshness. Guides carry a last-updated date; the company page shows reports published since then.
- Use the playbook for the next round. The "Next-Round Playbook" turns what candidates did into a short checklist.
Are the guides free?
Yes. Every guide on the blog is free and needs no account. Coins are only used to unlock premium question content and resume reviews. Guides link to free company pages and question searches, so you can follow the whole trail without paying.
How often are guides updated?
Each guide carries a last-updated date and a structured dateModified in its metadata. When a new batch of candidate reports arrives for a company, the relevant rounds and question tables are revised. If you spot something out of date, you can contribute your own experience; approved reports feed both the question bank and future guide updates.
FAQ
Are the questions in a guide real? Yes. Each one is a verbatim report or a faithful paraphrase of a candidate's account, with the round, level and year shown.
Do guides replace the question bank? No. A guide explains the process; the question bank gives you volume. Use both.
Why do some guides say [Draft]?
Because at least one round has fewer than five distinct sourced questions. The guide is still published with the gap disclosed, and it is improved as more accounts arrive.
Can I use a guide for a different company? Only as a pattern. Processes differ by year, team and campus, so always prefer the guide for your actual target company and role.
Where to start
- All company guides
- AMD Software Engineer — a full, sourced example
- Deloitte Data Analyst — a non-engineering role
- How CodinzHub works — coins, referrals and unlocking
- Explore CodinzHub — every page and shortcut
Keep track of what you’ve learned.