Does notcommenttheir codeHasn't kept upto date withthe frameworkthey'reapplying forCan'tcommunicatetheir role onpast projects(If Frontend)Can't explainmethods of statemanagement &its organization.Interested inshort-termemploymentCan'tcommunicatethe role they'dlike to have onfuture projectsDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Doesn'texplain whattheir projectdoes"What doyou mean'test yourcode'?"Didn'tbringdiagramsShows uplate to theinterviewDoesn'tknow whatthey'relooking for ina teamGitHub filledwith forkswithout anycommitsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)"Sorry, I can'tactuallyshow you..."Tries toshow codeas theirprojectDoes nothave aninterest inSoftwareCan't answerbasics aboutthetechnologythey work with"I've neverhad to dealwith errorrecovery"Jumps intopresentingdiagrams /code withoutexplaining whatit does(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan't explainthe reasonsbehinddesigndecisionsDoes notcommenttheir codeHasn't kept upto date withthe frameworkthey'reapplying forCan'tcommunicatetheir role onpast projects(If Frontend)Can't explainmethods of statemanagement &its organization.Interested inshort-termemploymentCan'tcommunicatethe role they'dlike to have onfuture projectsDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Doesn'texplain whattheir projectdoes"What doyou mean'test yourcode'?"Didn'tbringdiagramsShows uplate to theinterviewDoesn'tknow whatthey'relooking for ina teamGitHub filledwith forkswithout anycommitsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)"Sorry, I can'tactuallyshow you..."Tries toshow codeas theirprojectDoes nothave aninterest inSoftwareCan't answerbasics aboutthetechnologythey work with"I've neverhad to dealwith errorrecovery"Jumps intopresentingdiagrams /code withoutexplaining whatit does(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan't explainthe reasonsbehinddesigndecisions

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