Video summary
How Priyanshi Cracked GoTrust in Her Very First Interview | AccioJob Placement | AccioJob Review
Main summary
Key takeaways
Main ideas, concepts, and lessons
-
Practice platforms helped reduce “silly mistakes”
- Priyanshi explains that in earlier contests she lost marks due to small errors (e.g., a semicolon mistake).
- She notes that AI/automated checking catches such errors, so accuracy improves over time.
- After repeated attempts, her performance improved steadily.
-
Mocks + feedback loop = better interview confidence
- She attempted 4–5 mock sessions, split by modules (e.g., JS1, JS2).
- She cleared Mock JS2, but felt not fully satisfied.
- She then discussed with her mentor where she was lagging, retook/gave the mock again, and felt more confident afterward.
- Key takeaway: feedback and reattempts matter more than just clearing mocks once.
-
Interview felt familiar because mocks were tougher
- She claims interview questions felt familiar because she had already cleared mocks.
- She also states: the mock level is higher than the actual interview, so clearing mocks reduces risk.
-
Interview structure and what was asked
- Total: 3 rounds
- 2 face-to-face rounds
- 1 virtual round
- In company-held rounds (face-to-face)
- They first asked conceptual questions verbally (e.g., “tell me what is this concept”).
- Then a coding round where they asked her to solve problems related to:
- R (as mentioned in the subtitles)
- DSA (Data Structures and Algorithms)
- In the virtual round
- She had to showcase the project she was working on.
- On the spot, the interviewer asked her to modify the project immediately and demonstrate the change.
- Total: 3 rounds
-
Project modification demonstrates practical implementation
- Example from her project:
- She already had email + password fields on a login page.
- The interviewer asked her to add a number field and connect it to the backend (demonstrate real implementation, not just the UI).
- Lesson: companies want to see working implementation, not only how the project “looks.”
- Example from her project:
-
How her learning journey worked (habits and mindset)
- She used to hesitate to ask questions, but realized:
- “No one will ask for me.”
- If she didn’t understand a topic:
- She read it once and initially postponed further effort, but “later never came.”
- Eventually she adopted a routine:
- Read 2–3 times
- If still unclear, ask again (mentor/others)
- After finishing topics, she realized they became easier once learned.
- She used to hesitate to ask questions, but realized:
-
Assignments/contests build real readiness
- Conceptual understanding wasn’t enough—she learned by solving questions.
- She describes a pattern:
- She might feel confident after reading a concept,
- but when implementing, test cases fail.
- Retrying and using mentor guidance fixed the gap.
- Contests improved her through repetition and gradual score increases (sometimes around 50–50–60).
-
Why she preferred the program/job pathway
- She values hands-on learning:
- whatever she studied, she implemented,
- then discussed issues with mentor/batchmates.
- She says she previously lacked consistency:
- she would start studying,
- then stop when she got stuck.
- In her new environment, she learned to continue consistently.
- She values hands-on learning:
-
Group study/practice groups accelerate learning
- She and 2–3 others formed a small study group.
- They solved problems together by:
- discussing approaches,
- challenging each other,
- learning multiple ways to solve the same question.
- She says group learning made learning smoother and more engaging.
-
Handling “I want to quit” moments
- She faced multiple moments of wanting to quit (not understanding topics even after multiple reads).
- Her strategy:
- rewatch recordings,
- discuss with mentor,
- keep going until clarity arrives.
- She also emphasizes that “introvert behavior” from school shouldn’t prevent asking doubts in college/program:
- If you don’t understand, discuss with instructors/mentor.
-
Advice about fear of being judged
- If students worry they’ll be mocked for asking doubts:
- She advises not to assume that.
- If everyone is studying together, their skill levels are similar.
- Teachers treat everyone equally.
- If you don’t ask batchmates, ask the mentor/instructor.
- If students worry they’ll be mocked for asking doubts:
-
Telling parents about placement
- She did not plan a surprise.
- She told her parents immediately after receiving placement news.
- Her parents were shocked because it was her first interview and they didn’t expect it so soon.
Methodology / instructions conveyed
-
Use a feedback-and-retry loop
- Attempt mocks.
- If results are not satisfactory, identify weak areas with your mentor.
- Retake the mock after improvements.
-
Don’t stop at reading—practice until test cases pass
- Read concept.
- Solve problems.
- If implementations fail test cases:
- retry,
- debug,
- ask mentor for specific failing cases,
- repeat until stable.
-
Improve accuracy through repeated contests/practice
- Treat small errors (e.g., syntax like semicolons) as fixable targets.
- Use automated feedback (AI/testing) to catch mistakes early and correct them.
-
Adopt structured learning repetition
- If a topic is unclear:
- read it once, then don’t postpone indefinitely,
- read it 2–3 times,
- if still unclear, ask again.
- If a topic is unclear:
-
Ask doubts instead of staying silent
- If you’re confused, discuss with:
- mentor,
- instructor/professor,
- or study group peers.
- Don’t fear being mocked—assume peers and teachers are there to learn and correct.
- If you’re confused, discuss with:
-
Stay consistent even after getting stuck
- When you face difficulties, don’t pause indefinitely.
- Use resources (recordings) and support (mentor discussions) to continue.
-
Work with a small practice group
- Form a group (3–4 people).
- Share your approach,
- compare alternative solutions,
- and learn multiple ways to solve the same problem.
Speakers / sources featured
- Priyanshi (interviewee) — credited in subtitles as Priyanshu Mittal (placed as a Junior Software Developer at GoTrust), and the video host addresses her as Priyanshi.
- Mentor / interview mentor figure — referenced by Priyanshi (not named in subtitles).
- Interviewer(s) / company interview team — not individually named.
- Host (speaker addressing Priyanshi) — not named in subtitles.
- GoTrust — company mentioned as the placement destination (not a person).
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.