Your Gmail Avatar Is Part of Your Job Search
Put a recognizable photo on the Gmail account you use for your job search. Then follow the link in your signature and ask whether it leads to work you're proud to explain.
I've been coaching engineers one-on-one in our Discord. We look at the resume, the Icebreaker, the projects, and the person behind them. Nikhil's story stayed with me.
He has worked on Amazon Connect and Walmart Marketplace. He's trying to establish his career after the COVID years, in a market shaped by layoffs. His Walmart contract ended in a layoff. The names on his resume make the path look cleaner than it felt to live.
He described expecting his work to speak for itself inside his team. He would do the work, and people would see it. That expectation hadn't worked in his favor.
I understand it. You're already working hard. Packaging yourself can feel like time stolen from becoming a better engineer. But someone who hasn't worked beside you needs a way to recognize you, understand your contribution, and inspect it.
Put One Small Thing in Order
Choosing an avatar is a little like making your bed. It puts one small thing in order and gives you a place to begin. You don't remake your profile every morning; you build the habit of noticing what needs care.
Google says your picture can appear beside your name and in notifications to other Gmail users. Use a recent, recognizable photo, a consistent name, and a signature with one useful link.
A missing avatar tells me very little about your engineering. It does give us a useful prompt: where else might the introduction be unfinished? A broken demo? A README that never explains what the project does? A portfolio describing who you were two years ago?
Fixing the picture won't get you hired. Following that thread can make the work you've already done easier to discover and evaluate.
In a small experiment with mock LinkedIn profiles, people rated profiles with a photo as more competent. It measured impressions, not engineering ability or job offers. Presentation can open a conversation; the work has to sustain it.
Turn Care Into a Routine
Personal branding starts with a question: what do you want people to be able to count on you for?
If the answer is thoughtful engineering, make that visible in ordinary choices. Keep your links working. Explain a tradeoff. Correct an outdated claim. Each small action gives you another reason to believe you're becoming the engineer you want to be.
Give the profiles you use a clear job:
- LinkedIn: a recognizable photo, a clear direction, and a concrete contribution.
- GitHub: a complete profile and a few pinned projects with readable READMEs and working examples.
- Portfolio: one strong story showing the problem, your decisions, and the evidence.
- Gmail: a consistent identity and a short path to that story.
Set aside fifteen minutes after your weekly project review. Open those links as a stranger would. Repair one gap and record one improvement. Attach the routine to something you already do so it survives the weeks when motivation doesn't.
Compare this week's work with your own last week. Someone else's polished career is a poor measure of your progress. A clearer explanation, a working example, or a corrected mistake is something you can actually build on.
Give the Habit Something Worth Showing
Keeping everything tidy can become a comfortable way to avoid difficult work. Your portfolio needs to grow because your ability is growing.
Choose a problem you care enough about to stay with when it gets awkward. Then practice the thing you want to become good at. If you want to improve at debugging, reproduce a failure and investigate it. If you want to learn system design, build a small system and test where it breaks.
For Nikhil, I'd start with one contribution he can explain from experience. A list of technologies gives me ingredients. I want to know what he made with them.
Write one page:
- The situation: who had the problem, and what happened before you started?
- Your contribution: what did you personally change? Credit the team for the rest.
- The decision: what alternatives did you consider, and what did your choice cost?
- The evidence: show a demo, diagram, test, or measurement with its baseline.
- The limit: what remains unfinished, and what would you try next?
For private work, use an anonymized diagram or recreate a small example. Label what you recreated and what you shipped.
Now give the page to another engineer. Can they run the example? Can they explain your decision back to you? Where do they stop understanding? Use that feedback to choose your next practice session. Fix the weak point, test again, and update the story.
That's how a portfolio becomes a record of learning. You have something specific to say because you've done something specific and let it be questioned. A quiet engineer can do this in writing. I'm comfortable talking, so I have to watch my own tendency to confuse enthusiasm with evidence.
Let AI Help You Keep the Habit
AI makes the housekeeping cheaper. Use it to check links, suggest README structure, or turn a five-minute explanation into a draft. Build a workflow you can repeat:
The tension is that AI can make the story sound finished before the work is. A polished draft can hide the very gap you need to practice.
Read it against the artifact. Remove invented results, exaggerated ownership, and explanations you can't defend. Keep the decision you struggled with, the mistake you corrected, and the limit you still haven't solved. Those details give us a real conversation to have.
Use AI during learning, too: ask for a critique or an unfamiliar failure case. Then make a prediction, run the experiment, and explain what changed your mind. If you can't explain a generated solution, investigating it is your next assignment.
Working smarter should leave you more energy for the hard parts: judgment, experiments, feedback, and revision. A profile that makes promises your work can support is a brand you can keep improving.
Start With One Thing
If your experience is stronger than the story your profiles tell, book a one-on-one coaching session. Bring one piece of work we can inspect.
You can also join Auteurs, our free Discord, and start with resume-crit, or get the free coaching notes by email.
Start with the avatar. Follow the link. Fix one gap. Learn something difficult enough to give you a new story. Come back next week and do it again.
Further Reading
- 12 Rules for Life: An Antidote to Chaos — Jordan B. Peterson: personal responsibility, progress against your previous self, and truthful speech.
- Atomic Habits — James Clear: small routines that reinforce the person you want to become.
- Ultralearning — Scott H. Young: direct practice, feedback, and taking responsibility for your learning.