Brokeprod (andfixed it!)Took part ina book clubor studygroup atworka momentyou almostquit and whatyou learnedfrom itLed aknowledgesharingsessionLearned anon-technicalskill thathelped yourjobLeft morethan 15commentson a PRMentoredanengineerParticipatedin ahackathonwithcolleaguesPresentedwork in ateam or org-wide demoRepresentedthe team in aleadershipmeetingAdvocatedforsomeoneelse’s ideaAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleAutomateda manualtaskModeledvulnerability byadmitting youdidn’t knowsomethingParticipatedin GED,won, andpushed it toprodAsked “why”three times ina discussion tounderstanddeeper contextReducedtech debtin thecodebaseHad a“Eureka!”moment whileshowering orcommutingRevieweda PRPaired withanotherengineer tosolve aproblemShared aplaylist orsong thatboostedproductivityTook on arole outsideyour comfortzoneDiscovered aproductivityhack thatisn’t in thedocsWrote orimproveda TDDPaired ondebuggingfor over anhour withoutgiving upUsed ananalogy toexplain a techconcept thatmade peoplelaughPresentedto more than10 people>3 timesAdvocatedfor anengineer’spromotion orrecognitionParticipatedin a themedstandup ordress-up dayLearned anew keyboardshortcut thatchanged yourlifeSolved abug minutesbefore ameetingMade a jokein a standupthatlightened themoodFound abetter way ofworking bywatchingsomeone elseWrote adesigndocumentLed across-teameffortNamed afeature orinternaltoolAttended aconferenceorworkshopSuggested aprocesschange thatwas adoptedShared ameme inthe teamchannelContributedto a highvisibilityfeatureBrokeprod (andfixed it!)Took part ina book clubor studygroup atworka momentyou almostquit and whatyou learnedfrom itLed aknowledgesharingsessionLearned anon-technicalskill thathelped yourjobLeft morethan 15commentson a PRMentoredanengineerParticipatedin ahackathonwithcolleaguesPresentedwork in ateam or org-wide demoRepresentedthe team in aleadershipmeetingAdvocatedforsomeoneelse’s ideaAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleAutomateda manualtaskModeledvulnerability byadmitting youdidn’t knowsomethingParticipatedin GED,won, andpushed it toprodAsked “why”three times ina discussion tounderstanddeeper contextReducedtech debtin thecodebaseHad a“Eureka!”moment whileshowering orcommutingRevieweda PRPaired withanotherengineer tosolve aproblemShared aplaylist orsong thatboostedproductivityTook on arole outsideyour comfortzoneDiscovered aproductivityhack thatisn’t in thedocsWrote orimproveda TDDPaired ondebuggingfor over anhour withoutgiving upUsed ananalogy toexplain a techconcept thatmade peoplelaughPresentedto more than10 people>3 timesAdvocatedfor anengineer’spromotion orrecognitionParticipatedin a themedstandup ordress-up dayLearned anew keyboardshortcut thatchanged yourlifeSolved abug minutesbefore ameetingMade a jokein a standupthatlightened themoodFound abetter way ofworking bywatchingsomeone elseWrote adesigndocumentLed across-teameffortNamed afeature orinternaltoolAttended aconferenceorworkshopSuggested aprocesschange thatwas adoptedShared ameme inthe teamchannelContributedto a highvisibilityfeature

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