Cheat sheet · Software Engineer Career and Interview Playbook

Career Playbook cheat sheet

The three steps of interview preparation: a one-page resume of numbers, a 12-week coding study plan, and mock interviews with a scoring sheet and a mistake log. Built on one public guide, so treat it as one experienced view, not a rule.

Read the full series →

blogs · jp-blogs.vercel.app/cheatsheets/series/career

Resume layoutLesson 0 →

OrderSectionRule
1Headline + summaryHeadline under 10 words, summary under 50
2Contact InformationName, personal email and phone, city, LinkedIn
3SkillsLanguages: JS | TS | Python, grouped
4Work ExperienceNewest first, Company, Place | Title | MM/YYYY - MM/YYYY
5EducationGPA only if above 3.50 / 4.00
6ProjectsAt least 2, linked to GitHub
  • One page. A few best achievements beat many average ones. Students and under 3 years: Education first.
  • Design for a short, distracted read. No symbols in headings.
  • List only skills you could discuss for ten minutes.

The bullet formulaLesson 0 →

[Accomplishment]: [Action]
  that resulted in [outcome]

Check: Action + Scope + Result

Start with a strong verb. Scope = users, requests, team size.

BeforeAfter
Improved application performance.Cut orders API p95 from 900 ms to 350 ms with an index and a Redis cache.
Migrated database.Led a 200 GB MySQL to PostgreSQL move, 10 minutes planned downtime; wrote the runbook.
Helped the team with deployments.Built a pipeline that deploys on merge: release time 2 hours to 15 minutes.

Tip: Use only numbers you can explain: how measured, when, compared to what. Prefer before and after. No metric? Use scope. Never round up.

File format and ATSLesson 0 →

  • Write in Word or Google Docs, export a PDF with selectable text. No headers or footers, 0.5 inch margins.
  • Fonts: Arial, Calibri or Garamond, 10 pt or more. No design tools or online builders.
  • Spell out abbreviations once (Amazon Web Services and AWS).
  1. Plain-text test: copy all text, paste into a plain file.
  2. Missing points, wrong characters or sections out of order mean you fix the file.
  3. Repeat on every export.
ClaimStatus
An ATS auto-rejects by ruleThe guide's claim, not verified
Some rank by keyword countThe guide's claim, not verified
Copy keywords from the postOnly where true; do not stuff

What to cut, final checksLesson 0 →

CutWhy
Duties with no resultSays nothing about what changed
"Hard-working, passionate"Show it with a bullet
Columns, icons, skill barsParsing risk, no information
Old or unrelated jobsHides the strong lines
  • Keep the best 3 to 5 bullets per recent job.
  • Cover letter: under one page, do not repeat the resume, tell one relevant story.
  • Links must open when logged out. Have someone else check spelling and dates.

Study-plan numbersLesson 1 →

WhatThe handbook says
A coding round30 to 45 minutes
Bare minimumAbout 30 hours
Well preparedAbout 100 hours
Holistic planAbout 3 months, about 11 hours a week
Start mocksAt about 60% through the plan
  • Breadth-first: revise all topics, then mix. For about a month.
  • Depth-first: one topic at a time, high priority first. For short time.
  • Depth, then breadth: for more than a month. It keeps earlier topics fresh.

Watch out: Aimless grinding (30 minutes a question, 160 questions in 3 weeks) may not build retention. Keep estimates conservative.

The 12-week scheduleLesson 1 →

WeekTopics (priority)Hours
1Array, String, Hash table, Recursion11
2Sorting and searching, Matrix, Linked list, Queue, Stack11
3Tree, Graph (high); Heap, Trie (mid)14
4Interval, Dynamic programming, Binary, Math, Geometry10
5 to 1275 mixed questions; mocks from about week 711 a week

Tip: Working full time? 6 hours a week for 6 months can beat 11 for 3. The shape matters: topic, practise, mix, mock.

Practise a topic, weekly routineLesson 1 →

  1. Learn the idea; trace the example by hand.
  2. Solve one question cold with a 30 to 40 minute timer, thinking aloud.
  3. Stuck: smaller example, then a hint, then the solution. Note the hint.
  4. Read a good solution; compare time and space.
  5. Write a one-line pattern note, e.g. "sorted + pair sum: two pointers".
  6. Re-solve it days later without looking.
DayWhat
Mon, TueStudy the topic, 3 to 4 questions
Wed2 questions from last week, no notes
Thu3 mixed questions, timed
FriRead the mistake log, redo 2 old mistakes
WeekendMock (from week 7) or 2 timed questions

What interviewers scoreLesson 2 →

DimensionStrongWeak
CommunicationOrganised, easy to followCodes at once, near silent
Problem solvingClarifies, optimises, few hintsDisorganised, wrong approach
Technical skillClean, working codeMany errors, no solution
TestingNormal and corner cases, finds own bugsCalls it done despite bugs

Tip: Three of four are about how you work, so they can be practised. Bands: strong hire, hire, no hire, strong no hire.

Before, during, after codingLesson 2 →

Before
Clarifying questions, more examples, pick an approach
While
High-level structure first, narrate decisions, not keystrokes
After
Test with your examples, state time and space cost
Stuck: 1
Draw the problem and its states
Stuck: 2
Solve by hand, then turn the rules into code
Stuck: 3
More examples, split the problem, try common tools

Tip: Last ten minutes: test two normal and two edge cases (empty, one element, duplicates, huge). If unfinished, explain the missing parts.

Run a mock, keep a mistake logLesson 2 →

  1. Take turns as interviewer and candidate; use an unseen problem and the real time limit.
  2. Interviewer stays silent while you think, and counts the hints given.
  3. Score on the sheet in writing, then talk for 10 minutes.
  4. Write the lessons in the mistake log.
14 Oct  Merge intervals
Went wrong:  forgot to sort first
Root cause:  jumped to code
Next time:   plan first: "sort?" step 1

Log the cause, not the symptom. Count causes monthly.

  • Fix the lowest line on the sheet this week.
  • Record yourself once: you hear silences and "um".

Interview one-linersLesson 2 →

QuestionShort answer
Resume length?One page; best achievements first.
A strong bullet?Action, scope, result with a number.
Plain-text test?Paste into a text file; nothing missing or garbled.
When to start mocks?At about 60% through the plan.
What is scored?Communication, problem solving, skill, testing.
Bad round?Write it in the log. One round is one data point.

A cheat sheet is a reminder, not a teacher. Each card links to the lesson that explains it step by step.