Solved abug minutesbefore ameetingMade a jokein a standupthatlightened themoodMentoredanengineerLed across-teameffortShared aplaylist orsong thatboostedproductivityLearned anew keyboardshortcut thatchanged yourlifeContributedto a highvisibilityfeatureWrote orimproveda TDDRevieweda PRTook on arole outsideyour comfortzoneAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleReducedtech debtin thecodebaseAsked “why”three times ina discussion tounderstanddeeper contextSuggested aprocesschange thatwas adopteda momentyou almostquit and whatyou learnedfrom itModeledvulnerability byadmitting youdidn’t knowsomethingAutomateda manualtaskLearned anon-technicalskill thathelped yourjobFound abetter way ofworking bywatchingsomeone elseAdvocatedforsomeoneelse’s ideaRepresentedthe team in aleadershipmeetingAdvocatedfor anengineer’spromotion orrecognitionShared ameme inthe teamchannelTook part ina book clubor studygroup atworkNamed afeature orinternaltoolPaired ondebuggingfor over anhour withoutgiving upAttended aconferenceorworkshopPresentedwork in ateam or org-wide demoParticipatedin ahackathonwithcolleaguesWrote adesigndocumentPaired withanotherengineer tosolve aproblemParticipatedin GED,won, andpushed it toprodParticipatedin a themedstandup ordress-up dayLeft morethan 15commentson a PRDiscovered aproductivityhack thatisn’t in thedocsHad a“Eureka!”moment whileshowering orcommutingUsed ananalogy toexplain a techconcept thatmade peoplelaughPresentedto more than10 people>3 timesBrokeprod (andfixed it!)Led aknowledgesharingsessionSolved abug minutesbefore ameetingMade a jokein a standupthatlightened themoodMentoredanengineerLed across-teameffortShared aplaylist orsong thatboostedproductivityLearned anew keyboardshortcut thatchanged yourlifeContributedto a highvisibilityfeatureWrote orimproveda TDDRevieweda PRTook on arole outsideyour comfortzoneAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleReducedtech debtin thecodebaseAsked “why”three times ina discussion tounderstanddeeper contextSuggested aprocesschange thatwas adopteda momentyou almostquit and whatyou learnedfrom itModeledvulnerability byadmitting youdidn’t knowsomethingAutomateda manualtaskLearned anon-technicalskill thathelped yourjobFound abetter way ofworking bywatchingsomeone elseAdvocatedforsomeoneelse’s ideaRepresentedthe team in aleadershipmeetingAdvocatedfor anengineer’spromotion orrecognitionShared ameme inthe teamchannelTook part ina book clubor studygroup atworkNamed afeature orinternaltoolPaired ondebuggingfor over anhour withoutgiving upAttended aconferenceorworkshopPresentedwork in ateam or org-wide demoParticipatedin ahackathonwithcolleaguesWrote adesigndocumentPaired withanotherengineer tosolve aproblemParticipatedin GED,won, andpushed it toprodParticipatedin a themedstandup ordress-up dayLeft morethan 15commentson a PRDiscovered aproductivityhack thatisn’t in thedocsHad a“Eureka!”moment whileshowering orcommutingUsed ananalogy toexplain a techconcept thatmade peoplelaughPresentedto more than10 people>3 timesBrokeprod (andfixed it!)Led aknowledgesharingsession

Career Pros - 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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
  1. Solved a bug minutes before a meeting
  2. Made a joke in a standup that lightened the mood
  3. Mentored an engineer
  4. Led a cross-team effort
  5. Shared a playlist or song that boosted productivity
  6. Learned a new keyboard shortcut that changed your life
  7. Contributed to a high visibility feature
  8. Wrote or improved a TDD
  9. Reviewed a PR
  10. Took on a role outside your comfort zone
  11. Answered a “how do I…” question in Slack/Teams that helped multiple people
  12. Reduced tech debt in the codebase
  13. Asked “why” three times in a discussion to understand deeper context
  14. Suggested a process change that was adopted
  15. a moment you almost quit and what you learned from it
  16. Modeled vulnerability by admitting you didn’t know something
  17. Automated a manual task
  18. Learned a non-technical skill that helped your job
  19. Found a better way of working by watching someone else
  20. Advocated for someone else’s idea
  21. Represented the team in a leadership meeting
  22. Advocated for an engineer’s promotion or recognition
  23. Shared a meme in the team channel
  24. Took part in a book club or study group at work
  25. Named a feature or internal tool
  26. Paired on debugging for over an hour without giving up
  27. Attended a conference or workshop
  28. Presented work in a team or org-wide demo
  29. Participated in a hackathon with colleagues
  30. Wrote a design document
  31. Paired with another engineer to solve a problem
  32. Participated in GED, won, and pushed it to prod
  33. Participated in a themed standup or dress-up day
  34. Left more than 15 comments on a PR
  35. Discovered a productivity hack that isn’t in the docs
  36. Had a “Eureka!” moment while showering or commuting
  37. Used an analogy to explain a tech concept that made people laugh
  38. Presented to more than 10 people >3 times
  39. Broke prod (and fixed it!)
  40. Led a knowledge sharing session