Didn'tbringdiagramsHasn't kept upto date withthe frameworkthey'reapplying for"Sorry, I can'tactuallyshow you..."EnjoysBlockchain/ Monads(hehe)(If Frontend)Can't explainmethods of statemanagement &its organization.(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabases"What doyou mean'test yourcode'?"Does notcommenttheir codeDoesn't havequestions oftheir ownCan't explainthe reasonsbehinddesigndecisionsCan'tcommunicatethe role they'dlike to have onfuture projectsGitHub filledwith forkswithout anycommits"I've neverhad to dealwith errorrecovery"Jumps intopresentingdiagrams /code withoutexplaining whatit doesTries toshow codeas theirprojectCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)Doesn'texplain whattheir projectdoesDoesn'tknow whatthey'relooking for ina teamShows uplate to theinterviewCan't answerbasics aboutthetechnologythey work withDoes nothave aninterest inSoftwareCan'tcommunicatetheir role onpast projectsInterested inshort-termemploymentCommunicatestoo little(answers adesign questionwith a fewwords)Didn'tbringdiagramsHasn't kept upto date withthe frameworkthey'reapplying for"Sorry, I can'tactuallyshow you..."EnjoysBlockchain/ Monads(hehe)(If Frontend)Can't explainmethods of statemanagement &its organization.(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabases"What doyou mean'test yourcode'?"Does notcommenttheir codeDoesn't havequestions oftheir ownCan't explainthe reasonsbehinddesigndecisionsCan'tcommunicatethe role they'dlike to have onfuture projectsGitHub filledwith forkswithout anycommits"I've neverhad to dealwith errorrecovery"Jumps intopresentingdiagrams /code withoutexplaining whatit doesTries toshow codeas theirprojectCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)Doesn'texplain whattheir projectdoesDoesn'tknow whatthey'relooking for ina teamShows uplate to theinterviewCan't answerbasics aboutthetechnologythey work withDoes nothave aninterest inSoftwareCan'tcommunicatetheir role onpast projectsInterested inshort-termemploymentCommunicatestoo little(answers adesign questionwith a fewwords)

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