Doesn'texplain whattheir projectdoesCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you..."Tries toshow codeas theirprojectDoes nothave aninterest inSoftwareShows uplate to theinterviewCommunicatestoo little(answers adesign questionwith a fewwords)Can'tcommunicatetheir role onpast projectsGitHub filledwith forkswithout anycommitsDidn'tbringdiagramsEnjoysBlockchain/ Monads(hehe)Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)"I've neverhad to dealwith errorrecovery"Doesn't havequestions oftheir ownDoesn'tknow whatthey'relooking for ina team(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesJumps intopresentingdiagrams /code withoutexplaining whatit doesDoes notcommenttheir codeHasn't kept upto date withthe frameworkthey'reapplying for(If Frontend)Can't explainmethods of statemanagement &its organization.Can't explainthe reasonsbehinddesigndecisions"What doyou mean'test yourcode'?"Can'tcommunicatethe role they'dlike to have onfuture projectsInterested inshort-termemploymentDoesn'texplain whattheir projectdoesCan't answerbasics aboutthetechnologythey work with"Sorry, I can'tactuallyshow you..."Tries toshow codeas theirprojectDoes nothave aninterest inSoftwareShows uplate to theinterviewCommunicatestoo little(answers adesign questionwith a fewwords)Can'tcommunicatetheir role onpast projectsGitHub filledwith forkswithout anycommitsDidn'tbringdiagramsEnjoysBlockchain/ Monads(hehe)Can'tcommunicatesuccinctly(answers a yes /no question witha thesis)"I've neverhad to dealwith errorrecovery"Doesn't havequestions oftheir ownDoesn'tknow whatthey'relooking for ina team(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesJumps intopresentingdiagrams /code withoutexplaining whatit doesDoes notcommenttheir codeHasn't kept upto date withthe frameworkthey'reapplying for(If Frontend)Can't explainmethods of statemanagement &its organization.Can't explainthe reasonsbehinddesigndecisions"What doyou mean'test yourcode'?"Can'tcommunicatethe role they'dlike to have onfuture projectsInterested inshort-termemployment

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