Can't explainthe reasonsbehinddesigndecisionsJumps intopresentingdiagrams /code withoutexplaining whatit doesCan'tcommunicatetheir role onpast projectsShows uplate to theinterviewDoes notcommenttheir code(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn'texplain whattheir projectdoes"I've neverhad to dealwith errorrecovery"Communicatestoo little(answers adesign questionwith a fewwords)Interested inshort-termemploymentCan'tcommunicatethe role they'dlike to have onfuture projectsGitHub filledwith forkswithout anycommitsCan't answerbasics aboutthetechnologythey work with(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabases"What doyou mean'test yourcode'?"Doesn't havequestions oftheir ownCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)"Sorry, I can'tactuallyshow you..."Hasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareTries toshow codeas theirprojectDoesn'tknow whatthey'relooking for ina teamEnjoysBlockchain/ Monads(hehe)Didn'tbringdiagramsCan't explainthe reasonsbehinddesigndecisionsJumps intopresentingdiagrams /code withoutexplaining whatit doesCan'tcommunicatetheir role onpast projectsShows uplate to theinterviewDoes notcommenttheir code(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn'texplain whattheir projectdoes"I've neverhad to dealwith errorrecovery"Communicatestoo little(answers adesign questionwith a fewwords)Interested inshort-termemploymentCan'tcommunicatethe role they'dlike to have onfuture projectsGitHub filledwith forkswithout anycommitsCan't answerbasics aboutthetechnologythey work with(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabases"What doyou mean'test yourcode'?"Doesn't havequestions oftheir ownCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)"Sorry, I can'tactuallyshow you..."Hasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareTries toshow codeas theirprojectDoesn'tknow whatthey'relooking for ina teamEnjoysBlockchain/ Monads(hehe)Didn'tbringdiagrams

LE Senior Interview Sins Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Can't explain the reasons behind design decisions
  2. Jumps into presenting diagrams / code without explaining what it does
  3. Can't communicate their role on past projects
  4. Shows up late to the interview
  5. Does not comment their code
  6. (If Frontend) Can't explain methods of state management & its organization.
  7. Doesn't explain what their project does
  8. "I've never had to deal with error recovery"
  9. Communicates too little (answers a design question with a few words)
  10. Interested in short-term employment
  11. Can't communicate the role they'd like to have on future projects
  12. GitHub filled with forks without any commits
  13. Can't answer basics about the technology they work with
  14. (If Backend) Can't explain pros / cons of SQL vs NoSQL Databases
  15. "What do you mean 'test your code'?"
  16. Doesn't have questions of their own
  17. Can't communicate succinctly (answers a yes / no question with a thesis)
  18. "Sorry, I can't actually show you..."
  19. Hasn't kept up to date with the framework they're applying for
  20. Does not have an interest in Software
  21. Tries to show code as their project
  22. Doesn't know what they're looking for in a team
  23. Enjoys Blockchain / Monads (hehe)
  24. Didn't bring diagrams