Tries toshow codeas theirprojectCan't explainthe reasonsbehinddesigndecisionsDoesn'texplain whattheir projectdoes(If Frontend)Can't explainmethods of statemanagement &its organization.Jumps intopresentingdiagrams /code withoutexplaining whatit doesInterested inshort-termemploymentDoesn'tknow whatthey'relooking for ina team"What doyou mean'test yourcode'?"Communicatestoo little(answers adesign questionwith a fewwords)GitHub filledwith forkswithout anycommitsShows uplate to theinterview"I've neverhad to dealwith errorrecovery"Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Hasn't kept upto date withthe frameworkthey'reapplying for(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan'tcommunicatetheir role onpast projectsEnjoysBlockchain/ Monads(hehe)Can't answerbasics aboutthetechnologythey work withDoes nothave aninterest inSoftwareDoes notcommenttheir codeDoesn't havequestions oftheir own"Sorry, I can'tactuallyshow you..."Can'tcommunicatethe role they'dlike to have onfuture projectsDidn'tbringdiagramsTries toshow codeas theirprojectCan't explainthe reasonsbehinddesigndecisionsDoesn'texplain whattheir projectdoes(If Frontend)Can't explainmethods of statemanagement &its organization.Jumps intopresentingdiagrams /code withoutexplaining whatit doesInterested inshort-termemploymentDoesn'tknow whatthey'relooking for ina team"What doyou mean'test yourcode'?"Communicatestoo little(answers adesign questionwith a fewwords)GitHub filledwith forkswithout anycommitsShows uplate to theinterview"I've neverhad to dealwith errorrecovery"Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Hasn't kept upto date withthe frameworkthey'reapplying for(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan'tcommunicatetheir role onpast projectsEnjoysBlockchain/ Monads(hehe)Can't answerbasics aboutthetechnologythey work withDoes nothave aninterest inSoftwareDoes notcommenttheir codeDoesn't havequestions oftheir own"Sorry, I can'tactuallyshow you..."Can'tcommunicatethe role they'dlike to have onfuture projectsDidn'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. Tries to show code as their project
  2. Can't explain the reasons behind design decisions
  3. Doesn't explain what their project does
  4. (If Frontend) Can't explain methods of state management & its organization.
  5. Jumps into presenting diagrams / code without explaining what it does
  6. Interested in short-term employment
  7. Doesn't know what they're looking for in a team
  8. "What do you mean 'test your code'?"
  9. Communicates too little (answers a design question with a few words)
  10. GitHub filled with forks without any commits
  11. Shows up late to the interview
  12. "I've never had to deal with error recovery"
  13. Can't communicate succinctly (answers a yes / no question with a thesis)
  14. Hasn't kept up to date with the framework they're applying for
  15. (If Backend) Can't explain pros / cons of SQL vs NoSQL Databases
  16. Can't communicate their role on past projects
  17. Enjoys Blockchain / Monads (hehe)
  18. Can't answer basics about the technology they work with
  19. Does not have an interest in Software
  20. Does not comment their code
  21. Doesn't have questions of their own
  22. "Sorry, I can't actually show you..."
  23. Can't communicate the role they'd like to have on future projects
  24. Didn't bring diagrams