Then, for each project you're considering, place a checkmark next to the value that it has a high likelihood of fulfilling. 

This could mean working on particular projects within the organization which like external visibility (e.g. Android) rather than projects which don't (e.g. AdWords)

@mckaywrigley I have a bunch of questions I ask. What would you build for yourself? What did previous companies you've worked for need? What are you an expert in? What have you noticed recently that seemed broken? If you were going to build something just for fun, what would it be?

Thus my first piece of advice: if you have the choice between multiple jobs, all else being equal, pick the one where you are able to show what you've worked on.

Instead, especially in the early days of consulting, you’re chasing the greatest possible surface area of distinct clients in an attempt to better understand the interplay of what you’re good at, what people will pay for and who you want to be.

You don't have to optimize for "sexy" projects. You know, sexy projects: I don't know how to describe them but I know it when I see it. Most engineering work isn't intrinsically sexy. I would, however, optimize for impact and visibility.