Interested inshort-termemploymentDidn'tbringdiagrams(If Frontend)Can't explainmethods of statemanagement &its organization.Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Can'tcommunicatetheir role onpast projectsGitHub filledwith forkswithout anycommitsJumps intopresentingdiagrams /code withoutexplaining whatit does"Sorry, I can'tactuallyshow you..."Can'tcommunicatethe role they'dlike to have onfuture projects"What doyou mean'test yourcode'?"Communicatestoo little(answers adesign questionwith a fewwords)Does notcommenttheir codeDoesn't havequestions oftheir ownEnjoysBlockchain/ Monads(hehe)Can't answerbasics aboutthetechnologythey work with"I've neverhad to dealwith errorrecovery"Can't explainthe reasonsbehinddesigndecisionsDoesn'texplain whattheir projectdoesDoes nothave aninterest inSoftware(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesTries toshow codeas theirprojectHasn't kept upto date withthe frameworkthey'reapplying forShows uplate to theinterviewDoesn'tknow whatthey'relooking for ina teamInterested inshort-termemploymentDidn'tbringdiagrams(If Frontend)Can't explainmethods of statemanagement &its organization.Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)Can'tcommunicatetheir role onpast projectsGitHub filledwith forkswithout anycommitsJumps intopresentingdiagrams /code withoutexplaining whatit does"Sorry, I can'tactuallyshow you..."Can'tcommunicatethe role they'dlike to have onfuture projects"What doyou mean'test yourcode'?"Communicatestoo little(answers adesign questionwith a fewwords)Does notcommenttheir codeDoesn't havequestions oftheir ownEnjoysBlockchain/ Monads(hehe)Can't answerbasics aboutthetechnologythey work with"I've neverhad to dealwith errorrecovery"Can't explainthe reasonsbehinddesigndecisionsDoesn'texplain whattheir projectdoesDoes nothave aninterest inSoftware(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesTries toshow codeas theirprojectHasn't kept upto date withthe frameworkthey'reapplying forShows uplate to theinterviewDoesn'tknow whatthey'relooking for ina team

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