Led aknowledgesharingsessionRepresentedthe team in aleadershipmeetingAdvocatedforsomeoneelse’s ideaWrote orimproveda TDDTook on arole outsideyour comfortzoneNamed afeature orinternaltoolAttended aconferenceorworkshopHad a“Eureka!”moment whileshowering orcommutingSolved abug minutesbefore ameetingLeft morethan 15commentson a PRPresentedwork in ateam or org-wide demoPaired ondebuggingfor over anhour withoutgiving upLearned anon-technicalskill thathelped yourjobParticipatedin GED,won, andpushed it toprodAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleModeledvulnerability byadmitting youdidn’t knowsomethingAutomateda manualtaskShared ameme inthe teamchannelAdvocatedfor anengineer’spromotion orrecognitionFound abetter way ofworking bywatchingsomeone elsea momentyou almostquit and whatyou learnedfrom itPaired withanotherengineer tosolve aproblemLed across-teameffortReducedtech debtin thecodebaseContributedto a highvisibilityfeatureMade a jokein a standupthatlightened themoodTook part ina book clubor studygroup atworkDiscovered aproductivityhack thatisn’t in thedocsParticipatedin ahackathonwithcolleaguesSuggested aprocesschange thatwas adoptedRevieweda PRMentoredanengineerUsed ananalogy toexplain a techconcept thatmade peoplelaughShared aplaylist orsong thatboostedproductivityLearned anew keyboardshortcut thatchanged yourlifeAsked “why”three times ina discussion tounderstanddeeper contextPresentedto more than10 people>3 timesParticipatedin a themedstandup ordress-up dayBrokeprod (andfixed it!)Wrote adesigndocumentLed aknowledgesharingsessionRepresentedthe team in aleadershipmeetingAdvocatedforsomeoneelse’s ideaWrote orimproveda TDDTook on arole outsideyour comfortzoneNamed afeature orinternaltoolAttended aconferenceorworkshopHad a“Eureka!”moment whileshowering orcommutingSolved abug minutesbefore ameetingLeft morethan 15commentson a PRPresentedwork in ateam or org-wide demoPaired ondebuggingfor over anhour withoutgiving upLearned anon-technicalskill thathelped yourjobParticipatedin GED,won, andpushed it toprodAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleModeledvulnerability byadmitting youdidn’t knowsomethingAutomateda manualtaskShared ameme inthe teamchannelAdvocatedfor anengineer’spromotion orrecognitionFound abetter way ofworking bywatchingsomeone elsea momentyou almostquit and whatyou learnedfrom itPaired withanotherengineer tosolve aproblemLed across-teameffortReducedtech debtin thecodebaseContributedto a highvisibilityfeatureMade a jokein a standupthatlightened themoodTook part ina book clubor studygroup atworkDiscovered aproductivityhack thatisn’t in thedocsParticipatedin ahackathonwithcolleaguesSuggested aprocesschange thatwas adoptedRevieweda PRMentoredanengineerUsed ananalogy toexplain a techconcept thatmade peoplelaughShared aplaylist orsong thatboostedproductivityLearned anew keyboardshortcut thatchanged yourlifeAsked “why”three times ina discussion tounderstanddeeper contextPresentedto more than10 people>3 timesParticipatedin a themedstandup ordress-up dayBrokeprod (andfixed it!)Wrote adesigndocument

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