"I've neverhad to dealwith errorrecovery"Can'tcommunicatethe role they'dlike to have onfuture projectsEnjoysBlockchain/ Monads(hehe)(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesShows uplate to theinterviewCan'tcommunicatetheir role onpast projectsCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you...""What doyou mean'test yourcode'?"Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Doesn'tknow whatthey'relooking for ina teamTries toshow codeas theirprojectDoesn't havequestions oftheir own(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn'texplain whattheir projectdoesHasn't kept upto date withthe frameworkthey'reapplying forInterested inshort-termemploymentCan't explainthe reasonsbehinddesigndecisionsJumps intopresentingdiagrams /code withoutexplaining whatit doesDoes notcommenttheir codeDoes nothave aninterest inSoftwareCommunicatestoo little(answers adesign questionwith a fewwords)GitHub filledwith forkswithout anycommitsDidn'tbringdiagrams"I've neverhad to dealwith errorrecovery"Can'tcommunicatethe role they'dlike to have onfuture projectsEnjoysBlockchain/ Monads(hehe)(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesShows uplate to theinterviewCan'tcommunicatetheir role onpast projectsCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you...""What doyou mean'test yourcode'?"Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Doesn'tknow whatthey'relooking for ina teamTries toshow codeas theirprojectDoesn't havequestions oftheir own(If Frontend)Can't explainmethods of statemanagement &its organization.Doesn'texplain whattheir projectdoesHasn't kept upto date withthe frameworkthey'reapplying forInterested inshort-termemploymentCan't explainthe reasonsbehinddesigndecisionsJumps intopresentingdiagrams /code withoutexplaining whatit doesDoes notcommenttheir codeDoes nothave aninterest inSoftwareCommunicatestoo little(answers adesign questionwith a fewwords)GitHub filledwith forkswithout anycommitsDidn'tbringdiagrams

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