Video summary

How he landed a 19.4 LPA Software Engineer role at Gameberry Labs | AccioJob Placement Story

Main summary

Key takeaways

Business

Summary (business/career execution focus)

Ashraf shares a placement journey into a Software Engineer role at Gameberry Labs after moving from teaching. His path emphasizes structured learning, consistent project proof, and interview execution through repeated feedback loops.

Key actions & strategy playbook (what worked)

  • Leverage a program with strong placement outcomes

    • A friend (technical trainer at Parul University) recommended AccioJob because its placement records were higher than other edtech providers.

  • Structured curriculum + repetition

    • Completed a Java fast track program covering 6 units/modules with recorded videos.
    • Learned by understanding concepts from trainers, then reinforcing with practice (e.g., LeetCode).

  • Build industry-aligned interview practice

    • Used mocks starting around the June to November timeframe (per the story flow).
    • Went through ~5 interview rounds for the final offer, with increasing specificity:
      • DSA → low/high-level DSA → machine coding / LiD style.

  • Project-driven resume (treat like product development)

    • Mentors pushed him to:
      • Create GitHub links
      • Add project links clearly in his resume
      • Incorporate learnings based on mentor feedback
    • He built an end-to-end system and validated it with real engineering workflow:
      • REST API
      • CI/CD pipeline
      • GitHub Actions
      • Docker
      • Iterative development via PRs and merging after review (Agile-style).

  • Fail fast during interview cycles

    • He mentions giving 1–2 interviews and failing, then using those failures to improve how he explained solutions.

Frameworks/processes & “playbooks” explicitly mentioned

  • Consistency method: “3-day rule”

    • Learn something one day, then revise notes/problems in the next two days to keep them fresh.

  • Backtracking as an interview template

    • Use ChatGPT/templates to memorize a generic backtracking structure:
      • Recognize when a problem requires exploring combinations
      • Apply the template by plugging in the problem’s variables/data constraints

  • Machine Coding (LLD) approach

    • Interview process trick:
      1. Draft user flow (step-by-step actions)
      2. Confirm with interviewer before coding
      3. Convert flow in English → OOA/D entities
        • nouns → classes
        • verbs → methods
      4. Define relationships between classes (data flow)
      5. Then implement + run to show working output
    • Example domain referenced: Clash of Clans town halls/upgrades style model.

  • Project = product mindset

    • Build iteratively (“what next can I build”), not one-shot.
    • Validate via real engineering practices (PRs, CI/CD, Docker), not only code output.

Metrics / KPIs / targets & timelines (concrete)

  • Target role & outcome

    • Landed a 19.4 LPA Software Engineer role (from the video title).

  • Program timeline

    • Joined AccioJob in July last year
    • Selected and joined Gameberry Labs on 10th of August

  • Interview process

    • Selection involved ~5 interview rounds:
      • Round 1–2: DSA
      • Round 2–4: low-level DSA and high-level DSA (progression described)
      • One round explicitly described as machine coding / low-level design

  • Resume/project validation

    • Team/manager checked his GitHub repo activity (including GitHub Actions and PR workflow), not just the resume text.

Note: No financial KPIs like CAC/LTV/churn are discussed; this is execution-focused career engineering.

Concrete examples & case elements

  • Hero project: Student Management System

    • End-to-end REST API demonstrating:
      • CI/CD pipeline using GitHub Actions
      • Docker containerization
    • Iterative workflow:
      • Built feature-by-feature (“face-wise”)
      • Submitted PRs, reviewed, then merged
    • Recruiter emphasis (per Ashraf’s account):
      • They reviewed repository content to verify actual engineering capability.

  • Interview uniqueness advice

    • Use industry-relevant ideas already common in companies, but improvise/extend to show differentiation and capability.

Actionable recommendations (condensed)

  • Pick a training route tied to placement outcomes (not just content quality).
  • Practice in loops:
    • Learn → revise (3-day rule) → mock interviews → apply fixes from mentor/feedback.
  • Use structured templates during interviews
    • Backtracking template for combination/exploration problems.
    • LLD process: flow → confirm → OOA/D mapping → relationships → code-run.
  • Build GitHub like a production workflow
    • Add PRs, CI/CD, Docker, and clear documentation/links in resume.
  • Treat your project like a product
    • Iterate and expand features; show that you can continue improving.

Business takeaway (how he “won”)

Ashraf’s success wasn’t only DSA knowledge—it was the operational execution of a job-search “system”:

  • curriculum completion + timed mocks,
  • repeated interview practice with iteration after failures,
  • and a project portfolio demonstrating real engineering practices that recruiters/manager could verify directly.

Presenters / sources mentioned

  • Ashraf (placement-alumni guest; source of the story)
  • Yash (video host/interviewer)
  • Parul University (institution and technical trainer context)
  • AccioJob (program provider mentioned throughout)
  • Gameberry Labs (employer)

Original video