(If Frontend)Can't explainmethods of statemanagement &its organization.Does nothave aninterest inSoftwareDidn'tbringdiagramsCan'tcommunicatetheir role onpast projects"What doyou mean'test yourcode'?"Jumps intopresentingdiagrams /code withoutexplaining whatit doesShows uplate to theinterviewHasn't kept upto date withthe frameworkthey'reapplying forCan't answerbasics aboutthetechnologythey work with(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)Can't explainthe reasonsbehinddesigndecisions"I've neverhad to dealwith errorrecovery"Does notcommenttheir codeCan'tcommunicatethe role they'dlike to have onfuture projectsInterested inshort-termemploymentTries toshow codeas theirprojectCommunicatestoo little(answers adesign questionwith a fewwords)Doesn't havequestions oftheir ownDoesn'tknow whatthey'relooking for ina team"Sorry, I can'tactuallyshow you..."GitHub filledwith forkswithout anycommitsDoesn'texplain whattheir projectdoes(If Frontend)Can't explainmethods of statemanagement &its organization.Does nothave aninterest inSoftwareDidn'tbringdiagramsCan'tcommunicatetheir role onpast projects"What doyou mean'test yourcode'?"Jumps intopresentingdiagrams /code withoutexplaining whatit doesShows uplate to theinterviewHasn't kept upto date withthe frameworkthey'reapplying forCan't answerbasics aboutthetechnologythey work with(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)Can't explainthe reasonsbehinddesigndecisions"I've neverhad to dealwith errorrecovery"Does notcommenttheir codeCan'tcommunicatethe role they'dlike to have onfuture projectsInterested inshort-termemploymentTries toshow codeas theirprojectCommunicatestoo little(answers adesign questionwith a fewwords)Doesn't havequestions oftheir ownDoesn'tknow whatthey'relooking for ina team"Sorry, I can'tactuallyshow you..."GitHub filledwith forkswithout anycommitsDoesn'texplain whattheir projectdoes

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