Video summary

Crack Barclays with Insider Tips | C2C VIT Pune

Main summary

Key takeaways

Business

Business/Interview Strategy Takeaways (Barclays internship / PO process)

Recruitment process & timeline (operating “funnel”)

  • Shortlisting → OA → 2 interview rounds → summer internship (2 months) → PO
  • OA → Interviews (compressed turnaround)
    • One speaker noted: notification at ~4:00 PM, interviews at 8:00 AM next day
    • This implies you must be ready to perform immediately (very short prep window).
  • Interview structure (as described)
    • Round 1: Technical
      • Project deep dive + coding/DSA/SQL + resume depth
    • Round 2: HR/Behavioral
      • Primarily behavioral, but with some technical probing as well.
  • Internship
    • June–July (2 months) summer internship.
    • PO depends on performance on real projects
      • No formal KPI framework was described, but performance rating/impact is implied.

Key frameworks / playbooks mentioned (how to answer)

STAR method for project storytelling

  • Use: Situation → Task → Approach → Result
  • Also recommend: show architecture/flow visually
    • Example: front-end calls back-end, etc.

“Problem-first” project explanation playbook

  • Start with a real-world problem
  • Then explain your contribution
  • Then present technologies at the right depth

Gap-proofing playbook (avoid claiming unknown tech)

  • Don’t put tools/skills on your resume that you can’t explain.
    • Example given: claiming React/ReactJS without actually knowing it.

What to prepare (technical & resume-centric “spec”)

OA (Online Assessment) focus

  • OA is described as heavily SQL, with MCQs under time pressure.
    • Example OA pattern:
      • 5 SQL questions + 20 SQL MCQs
      • ~45 minutes
  • Positioning
    • Speakers emphasize that SQL is easier than DSA (in their case)
    • But DSA still matters overall, especially for thought process and later rounds.

DSA depth & topic prioritization

  • DSA emphasis: logic/pattern recognition rather than copy-paste drills.
  • Practical advice:
    • Focus on understanding & solving, not memorization
    • Quality > quantity: pattern mastery beats brute-force volume
  • DSA topics explicitly recommended:
    • Arrays
    • Strings
    • Stack
    • Sliding window
    • Queue
  • Additional note:
    • Some candidates report DSA touches “everything” (e.g., link list → graphs)
    • But this doesn’t necessarily mean perfect codewriting for every topic.

SQL concepts to cover

  • Include:
    • Joins
    • Subqueries
    • Grouping/aggregates patterns
      • Examples: average salary, max salary, conditional logic via WHERE / HAVING
  • One speaker note:
    • SQL may be broadly within DBMS syllabus → DBMS fundamentals matter.
  • Another note:
    • SQL testcases may include edge cases → practice helps more than theory alone.

“Project heavy” interviews: what actually gets evaluated

What interviewers test (resume & project deep dive)

Interviewers probe:

  • How well you know what you wrote on your resume
  • Edge cases / constraints
  • Architecture/block diagrams
  • Your specific contribution in team projects
  • Depth of your understanding of the problem

Strong recommendation: keep at least one individual project (not team-only) so your ownership is clear.

Common mistakes (actionable)

  • Mistake 1: Tech-stack-first storytelling
    • Instead: lead with problem → approach → result
  • Mistake 2: Resume claims you can’t defend
    • Example: claiming ReactJS but not being able to explain it
    • Or claiming computer networks without familiarity
  • Mistake 3: Half-knowledge
    • Don’t say you know something if you only partially do—probing reveals gaps
  • Mistake 4: Not being ready for “pen and paper”
    • No laptops during at least some coding sections
    • You must write code and explain time/space complexity

HR round: behavioral tactics that “work”

What HR questions look like

  • Strengths/weaknesses (with notable emphasis on weakness)
  • Fit with Barclays and its principles (expected to be known)
  • Team management / extracurricular leadership
  • Scenario/situational prompts, e.g.:
    • Handling teammate conflict professionally
    • Handling sensitive differences (one example involved a teammate’s sexual orientation)

How to handle unknowns mid-interview

  • It’s acceptable to miss some questions; strategy matters:
    • Aim for ~70–80% coverage (one speaker’s suggestion)
    • If you can’t answer:
      • Say you can’t answer now
      • Add you’re ready to learn and will review after
  • Confidence + structured communication are repeatedly emphasized.

Interview execution tactics (last-mile checklist)

  • Practice pen-and-paper coding and complexity explanation
  • Do mock interviews (at least 1–2 suggested)
  • Resume preparation is critical
    • Carry editable copies
    • Update your resume locally and print copies
    • Don’t manipulate the uploaded system copy
  • Formal attire
    • One speaker was blocked due to improper formal wear—formal dress is strongly recommended.
  • For very short prep windows (~12 hours / ~48 hours):
    • Prioritize core fundamentals, resume prep, and mock interview reps over deep research

Internship & PPO expectations (high-level)

  • Internship is described as:
    • Learning new technologies quickly
    • Adapting to existing projects
    • Delivering tasks to a reasonable standard (not perfection day 1)
    • Being a team player
  • PO phrasing:
    • PO treated as a consequence of internship performance and learning velocity
    • One referenced figure:
      • Stipend around “75k per month” (approximate)
  • Department/stack variation:
    • Interns may be assigned technologies/projects different from the resume
    • Learning is expected
    • Example: working on Spring Boot/Java and digital banking/cards domain

Metrics & selection-related KPIs mentioned

Cutoffs / selection rates (qualification signals)

  • CGPA / cutoff
    • Suggested “safe score”: > 8.5
    • “Safer” target repeatedly mentioned: ~9.0
  • Dynamic cutoff
    • Not fixed; depends on applicant volume and shortlist size
  • OA selection volumes (examples from speakers/drive anecdotes)
    • 18 → 8 internship selected
    • 22 → 13 selected
    • Another anecdote: around 30 hired (speaker unsure)

Recruitment stage conversion assumptions

  • HR sitting for technical qualifiers:
    • Not all technical-round candidates go to HR
    • Example: about ~50% of technical-round candidates continued to HR
  • PO/Intern conversion:
    • Not given as a fixed KPI, but PO depends on internship performance

Actionable recommendations (compressed playbook)

Resume strategy

  • Include 1–2+ complete projects, ideally one individual project
  • Ensure each resume line/tool is interview-defendable
  • Use professional resume formatting
    • One suggestion: Overleaf; avoid Canva/poor templates
  • Add:
    • GitHub repo links
    • Live deployed project links if possible

Project interview structure

  • Use STAR
  • Include architecture/flow (visual or step-by-step described)
  • Provide numeric impact when possible (e.g., % improvement, reduction)
  • Explain why tech choices were made (e.g., SQL vs NoSQL, database reasoning)

Tech prep

  • OA: be ready for SQL MCQs + SQL queries in 45 minutes
  • DSA: prioritize the core patterns listed (arrays/strings/stack/sliding window/queue)
  • SQL: joins/subqueries/filters/aggregate patterns

HR prep

  • Prepare weakness framing (not just listing weakness)
  • Memorize/understand Barclays principles
  • Practice conflict/team scenario responses with a professional tone

Crisis handling

  • If you don’t know:
    • Be honest
    • Communicate next steps (“ready to learn”)
    • Maintain confidence

Presenters / sources

  • Amy Bi (host)
  • Shri (Shrui / Shrii) (speaker; Barclays intern + received PPO)
  • Kavish Parasar (Kavish / Kawish) (speaker; Barclays intern + received PPO)

Original video