Some personal news: this week I started as Senior Product Manager at Meridian Health.

I will be leading the patient-scheduling team, working on the problem that first pulled me into health tech: the 40 minutes it can take to book a 10 minute appointment.

Before looking ahead, a thank you. To my team at Corebridge, you taught me what good looks like, and your standards are coming with me.

Day 3 and already deep in the roadmap. If you work on scheduling or patient access, I would love to compare notes.

Why it works: the news is line one, the work is described in the writer's own words, and the gratitude names one team and one lesson. Nothing here could be copied into anyone else's announcement.

New title, same mission: as of this month I am Engineering Manager at Halbrook.

The honest version of this news is that a team performed well enough that someone had to be promoted, and I was standing closest. I will spend the next year trying to deserve it.

To Priya, who told me two years ago to stop hoarding the hard problems and start teaching them: this one is yours too.

Why it works: promotions risk reading as self-congratulation, so the post hands the credit away and keeps the humility concrete instead of performed. Promotions also have their own etiquette around updating your profile; our guide to announcing a promotion on LinkedIn covers it with examples.

After nine years of teaching high school science, I have started as a Customer Success Manager at Lumen Analytics.

The jump is smaller than it looks on paper. My job was explaining complex systems to skeptical audiences and catching confusion before it became failure. That is this job too; the audience just got older.

Thank you to the mentors who reviewed my applications and told me the truth about what was not ready. You shortened this switch by months.

If you are a teacher wondering whether your skills transfer: they do, and my messages are open.

Why it works: a career change announcement has to answer "why does this make sense" in one paragraph, and this one does it by naming the transferable skill instead of claiming transferability in the abstract.

I started my first analyst role this week: Data Analyst at Novara Logistics.

I will be building reporting for the operations team, which is exactly the work I retrained for.

Two people made the difference while I was switching fields: the mentors who reviewed my projects and told me the truth about what was not good enough yet. You know who you are, and it worked.

If you are mid-career and eyeing analytics, my messages are open. I kept every note from the switch.

Why it works: no apology for being new, no inflated title, and the close turns the announcement into something useful for the people a step behind.