(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesJumps intopresentingdiagrams /code withoutexplaining whatit does"I've neverhad to dealwith errorrecovery"EnjoysBlockchain/ Monads(hehe)Can'tcommunicatetheir role onpast projectsInterested inshort-termemploymentDoesn'tknow whatthey'relooking for ina teamCommunicatestoo little(answers adesign questionwith a fewwords)Can't explainthe reasonsbehinddesigndecisionsShows uplate to theinterviewHasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareCan'tcommunicatethe role they'dlike to have onfuture projectsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)Tries toshow codeas theirprojectGitHub filledwith forkswithout anycommitsDidn'tbringdiagrams"Sorry, I can'tactuallyshow you..."Does notcommenttheir codeCan't answerbasics aboutthetechnologythey work withDoesn'texplain whattheir projectdoes"What doyou mean'test yourcode'?"(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn't havequestions oftheir own(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesJumps intopresentingdiagrams /code withoutexplaining whatit does"I've neverhad to dealwith errorrecovery"EnjoysBlockchain/ Monads(hehe)Can'tcommunicatetheir role onpast projectsInterested inshort-termemploymentDoesn'tknow whatthey'relooking for ina teamCommunicatestoo little(answers adesign questionwith a fewwords)Can't explainthe reasonsbehinddesigndecisionsShows uplate to theinterviewHasn't kept upto date withthe frameworkthey'reapplying forDoes nothave aninterest inSoftwareCan'tcommunicatethe role they'dlike to have onfuture projectsCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)Tries toshow codeas theirprojectGitHub filledwith forkswithout anycommitsDidn'tbringdiagrams"Sorry, I can'tactuallyshow you..."Does notcommenttheir codeCan't answerbasics aboutthetechnologythey work withDoesn'texplain whattheir projectdoes"What doyou mean'test yourcode'?"(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn't havequestions oftheir own

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