Took part ina book clubor studygroup atworkAdvocatedfor anengineer’spromotion orrecognitionLearned anon-technicalskill thathelped yourjobLeft morethan 15commentson a PRWrote adesigndocumentHad a“Eureka!”moment whileshowering orcommutingAutomateda manualtaskPresentedwork in ateam or org-wide demoContributedto a highvisibilityfeatureReducedtech debtin thecodebaseNamed afeature orinternaltoolShared aplaylist orsong thatboostedproductivityAsked “why”three times ina discussion tounderstanddeeper contextBrokeprod (andfixed it!)Found abetter way ofworking bywatchingsomeone elseParticipatedin GED,won, andpushed it toprodRevieweda PRa momentyou almostquit and whatyou learnedfrom itModeledvulnerability byadmitting youdidn’t knowsomethingMade a jokein a standupthatlightened themoodWrote orimproveda TDDLearned anew keyboardshortcut thatchanged yourlifePaired withanotherengineer tosolve aproblemLed across-teameffortMentoredanengineerSolved abug minutesbefore ameetingUsed ananalogy toexplain a techconcept thatmade peoplelaughTook on arole outsideyour comfortzoneLed aknowledgesharingsessionSuggested aprocesschange thatwas adoptedPaired ondebuggingfor over anhour withoutgiving upAdvocatedforsomeoneelse’s ideaParticipatedin ahackathonwithcolleaguesAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleRepresentedthe team in aleadershipmeetingParticipatedin a themedstandup ordress-up dayDiscovered aproductivityhack thatisn’t in thedocsShared ameme inthe teamchannelPresentedto more than10 people>3 timesAttended aconferenceorworkshopTook part ina book clubor studygroup atworkAdvocatedfor anengineer’spromotion orrecognitionLearned anon-technicalskill thathelped yourjobLeft morethan 15commentson a PRWrote adesigndocumentHad a“Eureka!”moment whileshowering orcommutingAutomateda manualtaskPresentedwork in ateam or org-wide demoContributedto a highvisibilityfeatureReducedtech debtin thecodebaseNamed afeature orinternaltoolShared aplaylist orsong thatboostedproductivityAsked “why”three times ina discussion tounderstanddeeper contextBrokeprod (andfixed it!)Found abetter way ofworking bywatchingsomeone elseParticipatedin GED,won, andpushed it toprodRevieweda PRa momentyou almostquit and whatyou learnedfrom itModeledvulnerability byadmitting youdidn’t knowsomethingMade a jokein a standupthatlightened themoodWrote orimproveda TDDLearned anew keyboardshortcut thatchanged yourlifePaired withanotherengineer tosolve aproblemLed across-teameffortMentoredanengineerSolved abug minutesbefore ameetingUsed ananalogy toexplain a techconcept thatmade peoplelaughTook on arole outsideyour comfortzoneLed aknowledgesharingsessionSuggested aprocesschange thatwas adoptedPaired ondebuggingfor over anhour withoutgiving upAdvocatedforsomeoneelse’s ideaParticipatedin ahackathonwithcolleaguesAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleRepresentedthe team in aleadershipmeetingParticipatedin a themedstandup ordress-up dayDiscovered aproductivityhack thatisn’t in thedocsShared ameme inthe teamchannelPresentedto more than10 people>3 timesAttended aconferenceorworkshop

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