Automateda manualtaskWrote orimproveda TDDAttended aconferenceorworkshopPaired ondebuggingfor over anhour withoutgiving upPresentedto more than10 people>3 timesParticipatedin a themedstandup ordress-up dayShared ameme inthe teamchannela momentyou almostquit and whatyou learnedfrom itSuggested aprocesschange thatwas adoptedLeft morethan 15commentson a PRModeledvulnerability byadmitting youdidn’t knowsomethingLed across-teameffortLearned anew keyboardshortcut thatchanged yourlifeDiscovered aproductivityhack thatisn’t in thedocsAdvocatedforsomeoneelse’s ideaHad a“Eureka!”moment whileshowering orcommutingNamed afeature orinternaltoolPaired withanotherengineer tosolve aproblemAsked “why”three times ina discussion tounderstanddeeper contextContributedto a highvisibilityfeatureRevieweda PRParticipatedin ahackathonwithcolleaguesLearned anon-technicalskill thathelped yourjobSolved abug minutesbefore ameetingAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleShared aplaylist orsong thatboostedproductivityWrote adesigndocumentTook on arole outsideyour comfortzoneBrokeprod (andfixed it!)Found abetter way ofworking bywatchingsomeone elseUsed ananalogy toexplain a techconcept thatmade peoplelaughAdvocatedfor anengineer’spromotion orrecognitionMentoredanengineerReducedtech debtin thecodebaseRepresentedthe team in aleadershipmeetingTook part ina book clubor studygroup atworkMade a jokein a standupthatlightened themoodParticipatedin GED,won, andpushed it toprodPresentedwork in ateam or org-wide demoLed aknowledgesharingsessionAutomateda manualtaskWrote orimproveda TDDAttended aconferenceorworkshopPaired ondebuggingfor over anhour withoutgiving upPresentedto more than10 people>3 timesParticipatedin a themedstandup ordress-up dayShared ameme inthe teamchannela momentyou almostquit and whatyou learnedfrom itSuggested aprocesschange thatwas adoptedLeft morethan 15commentson a PRModeledvulnerability byadmitting youdidn’t knowsomethingLed across-teameffortLearned anew keyboardshortcut thatchanged yourlifeDiscovered aproductivityhack thatisn’t in thedocsAdvocatedforsomeoneelse’s ideaHad a“Eureka!”moment whileshowering orcommutingNamed afeature orinternaltoolPaired withanotherengineer tosolve aproblemAsked “why”three times ina discussion tounderstanddeeper contextContributedto a highvisibilityfeatureRevieweda PRParticipatedin ahackathonwithcolleaguesLearned anon-technicalskill thathelped yourjobSolved abug minutesbefore ameetingAnswered a“how do I…”question inSlack/Teamsthat helpedmultiple peopleShared aplaylist orsong thatboostedproductivityWrote adesigndocumentTook on arole outsideyour comfortzoneBrokeprod (andfixed it!)Found abetter way ofworking bywatchingsomeone elseUsed ananalogy toexplain a techconcept thatmade peoplelaughAdvocatedfor anengineer’spromotion orrecognitionMentoredanengineerReducedtech debtin thecodebaseRepresentedthe team in aleadershipmeetingTook part ina book clubor studygroup atworkMade a jokein a standupthatlightened themoodParticipatedin GED,won, andpushed it toprodPresentedwork in ateam or org-wide demoLed 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. Automated a manual task
  2. Wrote or improved a TDD
  3. Attended a conference or workshop
  4. Paired on debugging for over an hour without giving up
  5. Presented to more than 10 people >3 times
  6. Participated in a themed standup or dress-up day
  7. Shared a meme in the team channel
  8. a moment you almost quit and what you learned from it
  9. Suggested a process change that was adopted
  10. Left more than 15 comments on a PR
  11. Modeled vulnerability by admitting you didn’t know something
  12. Led a cross-team effort
  13. Learned a new keyboard shortcut that changed your life
  14. Discovered a productivity hack that isn’t in the docs
  15. Advocated for someone else’s idea
  16. Had a “Eureka!” moment while showering or commuting
  17. Named a feature or internal tool
  18. Paired with another engineer to solve a problem
  19. Asked “why” three times in a discussion to understand deeper context
  20. Contributed to a high visibility feature
  21. Reviewed a PR
  22. Participated in a hackathon with colleagues
  23. Learned a non-technical skill that helped your job
  24. Solved a bug minutes before a meeting
  25. Answered a “how do I…” question in Slack/Teams that helped multiple people
  26. Shared a playlist or song that boosted productivity
  27. Wrote a design document
  28. Took on a role outside your comfort zone
  29. Broke prod (and fixed it!)
  30. Found a better way of working by watching someone else
  31. Used an analogy to explain a tech concept that made people laugh
  32. Advocated for an engineer’s promotion or recognition
  33. Mentored an engineer
  34. Reduced tech debt in the codebase
  35. Represented the team in a leadership meeting
  36. Took part in a book club or study group at work
  37. Made a joke in a standup that lightened the mood
  38. Participated in GED, won, and pushed it to prod
  39. Presented work in a team or org-wide demo
  40. Led a knowledge sharing session