• Go to your local Election Office and ask for a copy of the voting records for your district for the past 3 elections where the job that you want was on the ballot.
• Compile a list of people who voted in every single one of those last 3 elections and group them by neighborhood.
• Look up the results of the past 3 elections to see how many votes they needed to actually win.
• Spend all day every day traveling around from neighborhood to neighborhood and knocking on everyone's doors based on that list you made in the earlier bullet point to ask them to sign a petition to get you on the ballot.
• Assuming you got enough signatures, do another go-around to remind them to vote for you and to thank them for their signatures.
• Make some sort of tangible paper thing that you can leave on everyone's doors or give to them in person that covers the main point(s) that you think will convince those "good voters" to vote for you.
• Call or e-mail as many of those people as you can in the final week of the campaign to remind them why they should vote for you and ask them to remind their friends, family, or neighbors to vote for you as well.
• Cross your fingers and hope for the best.

Love Stole the Day fucked around with this message at 03:49 on Jan 5, 2020

• Stay in the current org, which is the company's primary revenue center, with managers who I either don't know or don't have as much trust built up with, under a new VP who had an awkward first impression of me, to do the tech equivalent of janitorial/waterboy work for teams that didn't think much of us before the re-org but are extremely competent at their jobs. Career growth would involve: becoming an expert in their domain and finding opportunities among the table scraps of work they leave for me to do. So, I'd have to work my way up, reputation-wise, and I'd stay close the coding stuff.
  
• Move to the new domain, under a director I like, in an (IC) Tech Lead Software Engineer role, with the verbal promise of a promotion at mid-year if I can deliver at least decent results to make it easier for her to justify it to the new VP (i.e. the same deal as last time, which worked out). Career growth would involve: convincing the leaders of other orgs' engineering teams to prioritize migrating off the old stuff and onboarding onto the new stuff that we didn't make, and giving those teams the support they need after they onboard. So, I'd be getting further away from code compared to the above option.
  
• Same as the second bullet point, above... but instead it'd be in a Technical Product Manager role instead of a Software Engineer role. The director thinks I'd do well in that career track, but I'm wary and skeptical of it because even though I get along very well with PMs... I think there's a bigger need for people to actually do the work, than there is for people to organize the people doing the work... and I'm good at actually doing the work, so I think I'd contribute more as a Tech Lead. I almost wish I could have both roles at the same time, if I'd also get both compensation packages!
  

Love Stole the Day fucked around with this message at 21:08 on Feb 1, 2024