Paired withanotherengineer tosolve aproblemDiscovered aproductivityhack thatisn’t in thedocsFound abetter way ofworking bywatchingsomeone elseLed aknowledgesharingsessionBrokeprod (andfixed it!)Learned anew keyboardshortcut thatchanged yourlifeRepresentedthe team in aleadershipmeetingAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleParticipatedin ahackathonwithcolleaguesAttended aconferenceorworkshopModeledvulnerability byadmitting youdidn’t knowsomethingTook on arole outsideyour comfortzonePresentedto more than10 people>3 timesSuggested aprocesschange thatwas adoptedContributedto a highvisibilityfeatureParticipatedin a themedstandup ordress-up dayNamed afeature orinternaltoolReducedtech debtin thecodebaseAdvocatedforsomeoneelse’s ideaHad a“Eureka!”moment whileshowering orcommutingAdvocatedfor anengineer’spromotion orrecognitionMentoredanengineerUsed ananalogy toexplain a techconcept thatmade peoplelaughTook part ina book clubor studygroup atworkAutomateda manualtaskPaired ondebuggingfor over anhour withoutgiving upLeft morethan 15commentson a PRAsked “why”three times ina discussion tounderstanddeeper contextMade a jokein a standupthatlightened themooda momentyou almostquit and whatyou learnedfrom itPresentedwork in ateam or org-wide demoShared aplaylist orsong thatboostedproductivitySolved abug minutesbefore ameetingRevieweda PRParticipatedin GED,won, andpushed it toprodLed across-teameffortShared ameme inthe teamchannelLearned anon-technicalskill thathelped yourjobWrote adesigndocumentWrote orimproveda TDDPaired withanotherengineer tosolve aproblemDiscovered aproductivityhack thatisn’t in thedocsFound abetter way ofworking bywatchingsomeone elseLed aknowledgesharingsessionBrokeprod (andfixed it!)Learned anew keyboardshortcut thatchanged yourlifeRepresentedthe team in aleadershipmeetingAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleParticipatedin ahackathonwithcolleaguesAttended aconferenceorworkshopModeledvulnerability byadmitting youdidn’t knowsomethingTook on arole outsideyour comfortzonePresentedto more than10 people>3 timesSuggested aprocesschange thatwas adoptedContributedto a highvisibilityfeatureParticipatedin a themedstandup ordress-up dayNamed afeature orinternaltoolReducedtech debtin thecodebaseAdvocatedforsomeoneelse’s ideaHad a“Eureka!”moment whileshowering orcommutingAdvocatedfor anengineer’spromotion orrecognitionMentoredanengineerUsed ananalogy toexplain a techconcept thatmade peoplelaughTook part ina book clubor studygroup atworkAutomateda manualtaskPaired ondebuggingfor over anhour withoutgiving upLeft morethan 15commentson a PRAsked “why”three times ina discussion tounderstanddeeper contextMade a jokein a standupthatlightened themooda momentyou almostquit and whatyou learnedfrom itPresentedwork in ateam or org-wide demoShared aplaylist orsong thatboostedproductivitySolved abug minutesbefore ameetingRevieweda PRParticipatedin GED,won, andpushed it toprodLed across-teameffortShared ameme inthe teamchannelLearned anon-technicalskill thathelped yourjobWrote adesigndocumentWrote orimproveda TDD

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