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

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