Can'tcommunicatethe role they'dlike to have onfuture projectsDoesn'tknow whatthey'relooking for ina teamDoes notcommenttheir codeCan't explainthe reasonsbehinddesigndecisionsCommunicatestoo little(answers adesign questionwith a fewwords)(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn't havequestions oftheir ownCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you..."(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesEnjoysBlockchain/ Monads(hehe)Didn'tbringdiagrams"I've neverhad to dealwith errorrecovery"Interested inshort-termemploymentCan'tcommunicatetheir role onpast projectsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)GitHub filledwith forkswithout anycommits"What doyou mean'test yourcode'?"Shows uplate to theinterviewTries toshow codeas theirprojectHasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareDoesn'texplain whattheir projectdoesJumps intopresentingdiagrams /code withoutexplaining whatit doesCan'tcommunicatethe role they'dlike to have onfuture projectsDoesn'tknow whatthey'relooking for ina teamDoes notcommenttheir codeCan't explainthe reasonsbehinddesigndecisionsCommunicatestoo little(answers adesign questionwith a fewwords)(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn't havequestions oftheir ownCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you..."(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesEnjoysBlockchain/ Monads(hehe)Didn'tbringdiagrams"I've neverhad to dealwith errorrecovery"Interested inshort-termemploymentCan'tcommunicatetheir role onpast projectsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)GitHub filledwith forkswithout anycommits"What doyou mean'test yourcode'?"Shows uplate to theinterviewTries toshow codeas theirprojectHasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareDoesn'texplain whattheir projectdoesJumps intopresentingdiagrams /code withoutexplaining whatit does

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