Can't answerbasics aboutthetechnologythey work withCan't explainthe reasonsbehinddesigndecisionsShows uplate to theinterviewCan'tcommunicatetheir role onpast projectsCan'tcommunicatethe role they'dlike to have onfuture projects"Sorry, I can'tactuallyshow you..."Jumps intopresentingdiagrams /code withoutexplaining whatit doesDoesn'tknow whatthey'relooking for ina teamCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)Didn'tbringdiagrams(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesInterested inshort-termemploymentDoes nothave aninterest inSoftwareGitHub filledwith forkswithout anycommitsDoesn'texplain whattheir projectdoes"I've neverhad to dealwith errorrecovery"(If Frontend)Can't explainmethods of statemanagement &its organization."What doyou mean'test yourcode'?"Hasn't kept upto date withthe frameworkthey'reapplying forTries toshow codeas theirprojectDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Does notcommenttheir codeCan't answerbasics aboutthetechnologythey work withCan't explainthe reasonsbehinddesigndecisionsShows uplate to theinterviewCan'tcommunicatetheir role onpast projectsCan'tcommunicatethe role they'dlike to have onfuture projects"Sorry, I can'tactuallyshow you..."Jumps intopresentingdiagrams /code withoutexplaining whatit doesDoesn'tknow whatthey'relooking for ina teamCan'tcommunicatesuccinctly(answers a yes /no question witha thesis)EnjoysBlockchain/ Monads(hehe)Didn'tbringdiagrams(If Backend)Can't explainpros / cons ofSQL vs NoSQLDatabasesInterested inshort-termemploymentDoes nothave aninterest inSoftwareGitHub filledwith forkswithout anycommitsDoesn'texplain whattheir projectdoes"I've neverhad to dealwith errorrecovery"(If Frontend)Can't explainmethods of statemanagement &its organization."What doyou mean'test yourcode'?"Hasn't kept upto date withthe frameworkthey'reapplying forTries toshow codeas theirprojectDoesn't havequestions oftheir ownCommunicatestoo little(answers adesign questionwith a fewwords)Does notcommenttheir code

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