If you’ve been feeling stuck with your AI/ML career, heads up:

I’ve been making lots of cool changes to the AI/ML Career Launchpad, and I've decided to cap new sign-ups so I can give my full attention to the members already inside while we roll out the new experience in September.

So if you've been thinking about this one for a while, now's your window. Doors close Sept. 1st.

The AI/ML Career Launchpad is my group coaching community for people building AI/ML careers who are looking for a structured path and ongoing support.

Inside you get:

Core membership is $39/month. Guided is $129/month and adds weekly live calls with me. If you don’t love it in the first 14 days I’ll give you a full refund. So you might as well check it out. ;)

I’m not sure when I’ll be ready to open up to new sign-ups, so if you’ve been thinking about it, now’s your chance. Learn more here.

This week, we’re doing a comprehensive breakdown of everything AI Engineers need to know about AI security.

We’ll cover:

You can read the full blog version here.

I’ve spent the last four years working as a career coach, and a big part of that work is helping people figure out how to talk about the work they’ve done.

When we review resumes, we’re looking for the biggest accomplishments from their past roles and figuring out how to highlight them effectively. When we practice interviews, we spend a lot of time turning past projects into stories that show they’re ready for the job they want next.

And one thing trips people up all the time is simply forgetting what they did. Ooph.

Of course most of us remember the general idea, but the details like “why this model?” or “what metrics did it move and how much?” are easy to blank on.

You’ve probably experienced a smaller version of this when writing a self-assessment for a performance review. You sit down and think to yourself, “I know I did some cool stuff this year but I have no idea what...” 🫠

This is annoying when it happens before a performance review, but it’s way worse when (surprise!) there are layoffs and you find yourself looking for a new job… and you don’t have access to the docs and code you need to figure this stuff out.

Luckily, this is extremely easy to prevent (well, not the layoff itself, but the rest of it).

Keep a running log of your work.

Make it a habit to record three things:

To make this really easy, set up a simple agent that pulls your docs, Git commits, Jira, and Slack and writes a weekly summary of your progress.

And this isn’t only useful for some hypothetical future job search. You can use that summary as the starting point for your 1:1s with your manager. Over time, you also have a record you can use when you’re making the case for a promotion or bigger scope.

Make sure to save anonymized versions to your personal files on a regular basis (obviously don’t store company data, but it’s fine to say generally what you built and the result).

This will be invaluable next time you’re up for promotion, preparing for a performance review, updating your resume, or preparing for interviews. It’s worth the 15 minutes it’ll take to set up an automation with Claude Code to do this. You’ll be glad you did it before you needed it.

Forwarded this email? Sign up here.

Follow me on YouTube | Instagram | X | LinkedIn | TikTok

Note: This email may contain affiliate links. If you make a purchase I may make a small commission, at no cost to you. Thank you for your support!