Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Can'tcommunicatetheir role onpast projectsCan'tcommunicatethe role they'dlike to have onfuture projectsCan't explainthe reasonsbehinddesigndecisionsDoesn'tknow whatthey'relooking for ina teamGitHub filledwith forkswithout anycommits(If Frontend)Can't explainmethods of statemanagement &its organization.Didn'tbringdiagramsEnjoysBlockchain/ Monads(hehe)Tries toshow codeas theirproject(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesHasn't kept upto date withthe frameworkthey'reapplying for"Sorry, I can'tactuallyshow you..."Doesn'texplain whattheir projectdoesCan't answerbasics aboutthetechnologythey work withJumps intopresentingdiagrams /code withoutexplaining whatit does"What doyou mean'test yourcode'?""I've neverhad to dealwith errorrecovery"Interested inshort-termemploymentCommunicatestoo little(answers adesign questionwith a fewwords)Does nothave aninterest inSoftwareDoes notcommenttheir codeDoesn't havequestions oftheir ownShows uplate to theinterviewCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)Can'tcommunicatetheir role onpast projectsCan'tcommunicatethe role they'dlike to have onfuture projectsCan't explainthe reasonsbehinddesigndecisionsDoesn'tknow whatthey'relooking for ina teamGitHub filledwith forkswithout anycommits(If Frontend)Can't explainmethods of statemanagement &its organization.Didn'tbringdiagramsEnjoysBlockchain/ Monads(hehe)Tries toshow codeas theirproject(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesHasn't kept upto date withthe frameworkthey'reapplying for"Sorry, I can'tactuallyshow you..."Doesn'texplain whattheir projectdoesCan't answerbasics aboutthetechnologythey work withJumps intopresentingdiagrams /code withoutexplaining whatit does"What doyou mean'test yourcode'?""I've neverhad to dealwith errorrecovery"Interested inshort-termemploymentCommunicatestoo little(answers adesign questionwith a fewwords)Does nothave aninterest inSoftwareDoes notcommenttheir codeDoesn't havequestions oftheir ownShows uplate to theinterview

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