technifyed
Weekly list
Opportunities
Learn
Interview prepAI toolsGet the weekly list

Popular: InternshipsScholarshipsFree coursesInterview prep

Interview preparation roadmap · Technology

A game engine in depth, game maths and physics, C# or C++, and a portfolio of finished games.

EnginesMathsPortfolio

0 / 17 complete · 11 core · 6 other · 91 subtopics

0%

Start here

  1. 01Interview foundations
  2. 02Coding
  3. 03Game fundamentals
  4. 04Portfolio
  5. 05Practice
  6. 06Company & final prep
CoreCommonly assessedGood to knowRole-dependentAdvancedFor deeper interviewsOptionalNot needed by everyoneCompletedYour progressYou are hereNext up

  1. 01Interview foundations

    What every interviewer sees first.

    1. 01.1Resume

      CoreBeginner3–5 h

      A one-page resume you can defend line by line.

      What this covers

      • One-page format — Reverse-chronological, clean fonts, no photos or tables that confuse parsers.
      • Project bullets — Action + what you built + a number (users, speed, accuracy).
      • Skills section — Only skills you can answer questions on for two minutes.
      • ATS readability — Export a text-based PDF and check it with a parser.
      • Working links — GitHub, LinkedIn and a live project link that open.
      • Tailoring — Reorder bullets to match the job description.

      What to practise

      • Run your PDF through a parser test
      • Rewrite each bullet as action + result
      • Remove any skill you can't explain for 2 minutes

      Common questions

      • Walk me through your resume.
      • Which project here are you most proud of, and why?
      • Why is this skill on your resume?

      Free resources

      • OpenResume — Free ATS-friendly resume builder and parser test (Free)
      • Jake's Resume (Overleaf) — The LaTeX resume template most SDE freshers use (Free)
      • Resume Worded — Resume and LinkedIn scoring (Free plan)
      • Jobscan — Match your resume against a job description (Free plan)

      Free courses

    2. 01.2Tell me about yourself

      CoreBeginner1–2 h

      A 60–90 second answer: present, past, why this role.

      What this covers

      • Present — Who you are now: degree, year, focus.
      • Past — One or two proof points: a project, internship or result.
      • Future — Why this role and this company next.
      • Length — 60–90 seconds; stop before you list everything.
      • Delivery — Calm pace and eye contact, not a memorised script.

      What to practise

      • Write it, then say it out loud 5 times
      • Record yourself and cut anything over 90 seconds

      Common questions

      • Tell me about yourself.
      • Why should we hire you?
      • Where do you see yourself in a few years?

      Free resources

      Free courses

    3. 01.3Behavioral & STAR

      CoreBeginner3–4 h

      Stories about teamwork, conflict and failure, told with STAR.

      What this covers

      • STAR structure — Situation, task, action, result. Spend most of the time on action.
      • Story bank — 6–8 real stories you can reuse across questions.
      • Teamwork & conflict — Disagreeing respectfully and what you changed.
      • Failure & weakness — A real one, what you learned, what you do now.
      • Ownership — Times you took initiative without being asked.
      • Common HR questions — Why us, why you, strengths, relocation.

      What to practise

      • Write 6 stories in STAR form
      • Map each story to 2–3 common questions
      • Practise one story with a friend

      Common questions

      • Tell me about a time you failed.
      • Describe a conflict in a team and what you did.
      • What is your biggest weakness?

      Free resources

      Free courses

  2. 02Coding

    Many studios test coding.

    1. 02.1Programming fundamentals

      CoreBeginner6–10 h

      One language you know well: syntax, memory, complexity.

      What this covers

      • One language deeply — C++, Java or Python: syntax, standard library, quirks.
      • Time & space complexity — Big-O of loops, recursion and common operations.
      • Recursion — Base cases, the call stack, when it overflows.
      • Memory basics — Stack vs heap, references vs values, garbage collection.
      • Strings & arrays — Immutability, copying and slicing costs in your language.
      • Debugging — Reading errors, dry runs, using a debugger.

      What to practise

      • Solve 10 easy problems without an IDE's help
      • Explain the complexity of each solution aloud

      Common questions

      • What is the time complexity of your solution?
      • What happens in memory when you call a function?
      • Difference between an array and a linked list?

      Free resources

      Free courses

    2. 02.2Data structures & algorithms

      CoreIntermediate40–80 h

      The core problem-solving topics commonly assessed in software interviews.

      What this covers

      • Arrays & hashing — Frequency maps, prefix sums, duplicates.
      • Two pointers & sliding window — Pairs, subarrays and substrings in O(n).
      • Stacks & queues — Brackets, monotonic stacks, BFS queues.
      • Linked lists — Reversal, cycle detection, merging.
      • Trees & BST — Traversals, height, LCA, validation.
      • Graphs — BFS, DFS, topological sort, shortest paths.
      • Binary search — On sorted arrays and on the answer.
      • Dynamic programming — 1D and 2D DP, from climbing stairs to knapsack.

      What to practise

      • Follow one list end to end, not five
      • Say the brute force first, then improve it
      • One timed problem a day

      Common questions

      • What is the difference between BFS and DFS?
      • How does a hash map handle collisions?
      • Find the first non-repeating character in a string.

      Free resources

      Free courses

    3. 02.3Core C++

      Good to knowIntermediate8–12 h

      C++ language questions for C++ and systems roles.

      What this covers

      • Pointers & references — Differences and pitfalls.
      • Memory — Stack vs heap, RAII, smart pointers.
      • OOP in C++ — Virtual functions, vtables, constructors.
      • STL — Vectors, maps, iterators, algorithms.
      • Templates — Generic code basics.
      • Undefined behaviour — Common sources and how to avoid them.

      What to practise

      • Implement a small vector class
      • Rewrite raw-pointer code with smart pointers

      Common questions

      • What is a virtual function?
      • Difference between a pointer and a reference?
      • What is RAII?

      Free resources

      Free courses

  3. 03Game fundamentals

    The core of the role.

    1. 03.1Game development

      CoreIntermediate10–20 h

      Engines, game loops and the maths games use.

      What this covers

      • Game loop — Update, render, fixed vs variable time step.
      • An engine deeply — Unity (C#) or Godot (GDScript/C#).
      • Maths — Vectors, transforms, collisions.
      • Physics & input — Rigid bodies, raycasts, controls.
      • Optimisation — Draw calls, pooling, profiling.
      • Portfolio — Small finished games beat big unfinished ones.

      What to practise

      • Finish and publish two small games
      • Profile one game and fix a frame drop

      Common questions

      • How does a game loop work?
      • How would you detect a collision between two circles?

      Free resources

      • Unity Learn — Official game development tutorials (Free)
      • Godot documentation — Official docs for the free Godot engine (Free)
      • 3Blue1Brown — The maths behind neural nets and linear algebra, visually (Free)

      Free courses

    2. 03.2OOP

      CoreBeginner5–8 h

      Classes, objects and the four pillars, with your own examples.

      What this covers

      • Classes & objects — State, behaviour and constructors.
      • Encapsulation & abstraction — Hide data, expose a clean interface.
      • Inheritance — Reuse, is-a relationships, the diamond problem.
      • Polymorphism — Overloading vs overriding, dynamic dispatch.
      • Interfaces vs abstract classes — When to use which.
      • SOLID basics — Single responsibility and open/closed with examples.

      What to practise

      • Model a library or parking lot in classes
      • Explain each pillar with code you wrote

      Common questions

      • What is polymorphism? Give an example.
      • Abstract class vs interface?
      • What is the diamond problem?

      Free resources

      Free courses

    3. 03.3Low-level design

      Good to knowAdvanced8–12 h

      Class diagrams and design patterns for a small system.

      What this covers

      • Design patterns — Singleton, factory, strategy, observer.
      • Class diagrams — Classes, relationships, multiplicity.
      • SOLID in practice — Applying it to a real design.
      • Classic problems — Parking lot, vending machine, library.

      What to practise

      • Design a parking lot in classes
      • Design a vending machine

      Common questions

      • Design a parking lot system.
      • When would you use the Strategy pattern?

      Free resources

      Free courses

  4. 04Portfolio

    Finished games matter most.

    1. 04.1Projects & resume defense

      CoreIntermediate4–6 h

      Explaining what you built, why, and what you would change.

      What this covers

      • The problem — What it solves and for whom.
      • Your role — Exactly what you built yourself.
      • Architecture — A simple diagram: frontend, backend, database.
      • Hardest bug — What broke and how you found it.
      • Trade-offs — Why this stack; what you would change now.
      • Scale questions — What happens with 10x the users.

      What to practise

      • Prepare a 2-minute walkthrough per project
      • Be ready to draw its architecture

      Common questions

      • What was the hardest part of this project?
      • Why did you choose this tech stack?
      • How would it handle 10x more users?

      Free resources

      Free courses

    2. 04.2Git & version control

      Good to knowBeginner2–4 h

      Branches, merges and collaborating on code.

      What this covers

      • Commits & history — Small commits with clear messages.
      • Branching — Feature branches and pull requests.
      • Merge vs rebase — When to use which.
      • Resolving conflicts — Reading and fixing conflict markers.
      • Undoing safely — revert, reset and restore.

      What to practise

      • Contribute a small fix to an open-source repo
      • Practise resolving a merge conflict

      Common questions

      • Difference between merge and rebase?
      • How do you undo a pushed commit?

      Free resources

      • Pro Git book — The free official Git book (Free)
      • GitHub — Where your projects live (Free)
      • freeCodeCamp — Full curricula with projects, certificates at the end (Free)

      Free courses

  5. 05Practice

    Saying it out loud is a different skill.

    1. 05.1Technical mock interviews

      CoreIntermediate3–6 h

      At least two full coding mocks before the real one.

      What this covers

      • Thinking aloud — Narrate your approach before and while coding.
      • Clarifying questions — Confirm inputs, scale and edge cases first.
      • Handling hints — Take them gracefully and adapt.
      • "I don't know" — Say what you do know and how you would find out.
      • Review the recording — Fillers, pace, unclear explanations.

      What to practise

      • Do two peer mock interviews
      • Record one spoken mock and listen back

      Common questions

      • Walk me through your approach before you code.
      • How would you test this?

      Free resources

      Free courses

    2. 05.2Technical communication

      Good to knowBeginner2–3 h

      Explaining your thinking clearly in English.

      What this covers

      • Structure — Big picture first, then details.
      • Plain words — Explain without jargon.
      • Checking in — "Does that make sense so far?"
      • Written English — Clear emails and follow-ups.

      What to practise

      • Explain one project to a non-CS friend
      • Record a 2-minute explanation of your best project and listen back

      Common questions

      • Explain recursion to a 10-year-old.

      Free resources

      Free courses

  6. 06Company & final prep

    The last 48 hours.

    1. 06.1Company research

      CoreBeginner1–2 h

      The product, the role, the job description and recent news.

      What this covers

      • The business — What it sells and to whom.
      • The role — What the job description really asks for.
      • Recent news — Launches, results, announcements.
      • Interview format — The rounds, if the company shares them.
      • Your fit — Three reasons, matched to the job description.

      What to practise

      • Write 3 reasons you want this role
      • Match 3 JD lines to your experience

      Common questions

      • Why do you want to work here?
      • What do you know about our product?

      Free resources

    2. 06.2Questions to ask

      Good to knowBeginner30 min

      Two or three good questions for the end of the interview.

      What this covers

      • About the team — How work is planned and reviewed.
      • About growth — Mentoring, learning, the first 90 days.
      • About the product — What is hard right now.
      • What to avoid — Questions a quick search answers.

      What to practise

      • Write 5 questions, keep the best 3
      • Prepare one question about the team's own product

      Common questions

      • Do you have any questions for us?

      Free resources

    3. 06.3Final checklist

      CoreBeginner30 min

      Logistics, documents, setup and a calm night before.

      What this covers

      • Logistics — Time, timezone, link or address.
      • Documents — Resume copies, ID, certificates if asked.
      • Tech check — Camera, mic, internet, charger.
      • Night before — Sleep, light revision, no new topics.

      What to practise

      • Do a 5-minute tech check the day before
      • Lay out documents and clothes the night before

      Free resources

    4. 06.4Job & interview safety

      Good to knowBeginner15 min

      Spot fake offers, payment requests and fake interview links.

      What this covers

      • Payment requests — Real employers don't charge for jobs or training.
      • Email domains — Check it matches the company's own site.
      • OTPs & logins — Never share them with anyone.
      • Fake interview links — Care with unknown chat apps and downloads.
      • Reporting — The 1930 helpline and cybercrime.gov.in.

      What to practise

      • Check one recent offer against these rules
      • Confirm the opening is listed on the company's own careers page

      Free resources

Enter your email and the official page opens. Phone is optional.

We save your email, and your phone number if you add it, to send you this link and, if you tick the box, the weekly list. Under 18? Ask a parent or guardian first. How your details are used.

Open official page