Jumps intopresentingdiagrams /code withoutexplaining whatit doesCan't answerbasics aboutthetechnologythey work withHasn't kept upto date withthe frameworkthey'reapplying forDoesn'texplain whattheir projectdoes(If Frontend)Can't explainmethods of statemanagement &its organization.Can'tcommunicatetheir role onpast projects"Sorry, I can'tactuallyshow you..."Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)"What doyou mean'test yourcode'?"EnjoysBlockchain/ Monads(hehe)Can'tcommunicatethe role they'dlike to have onfuture projectsDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Doesn'tknow whatthey'relooking for ina team"I've neverhad to dealwith errorrecovery"(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesDoes notcommenttheir codeCan't explainthe reasonsbehinddesigndecisionsDoes nothave aninterest inSoftwareShows uplate to theinterviewDidn'tbringdiagramsTries toshow codeas theirprojectGitHub filledwith forkswithout anycommitsInterested inshort-termemploymentJumps intopresentingdiagrams /code withoutexplaining whatit doesCan't answerbasics aboutthetechnologythey work withHasn't kept upto date withthe frameworkthey'reapplying forDoesn'texplain whattheir projectdoes(If Frontend)Can't explainmethods of statemanagement &its organization.Can'tcommunicatetheir role onpast projects"Sorry, I can'tactuallyshow you..."Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)"What doyou mean'test yourcode'?"EnjoysBlockchain/ Monads(hehe)Can'tcommunicatethe role they'dlike to have onfuture projectsDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Doesn'tknow whatthey'relooking for ina team"I've neverhad to dealwith errorrecovery"(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesDoes notcommenttheir codeCan't explainthe reasonsbehinddesigndecisionsDoes nothave aninterest inSoftwareShows uplate to theinterviewDidn'tbringdiagramsTries toshow codeas theirprojectGitHub filledwith forkswithout anycommitsInterested inshort-termemployment

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