About you

What I know about you and where it came from. I use it to pick ideas, match your voice and know what to leave out. Change anything — you have the final say.

One thing that would help me most:

Help me understand your professional background.

Upload your CV and I'll read your roles, history and skills, so you don't have to type them.

Background

Who you've been professionally. I know what you do. Your CV would fill in the history.

Good Upload CV
Role

Frontend Engineer

You told me
Summary

Builds React products and AI-assisted developer tooling. Works remotely. Likes to talk about how engineering work is changing, from inside the work.

You told me

Your CV would fill in your history, education and projects.

Expertise and interests

What you know well. What I'll look for in what you share.

Strong
You told me
  • React
  • TypeScript
  • AI-assisted development
  • Product engineering
  • Frontend performance

Also interested in

  • Mentoring junior developers

Your goal on LinkedIn

I'll pick ideas that work toward it.

Strong

Become known as an expert

What you want to be known for

Where you're heading — your CV only says where you've been. Focused enough to own.

Strong
  • AI-era software engineering
  • Remote work
  • Engineering thinking

Who you want to reach

Shapes my examples, language and depth. Clear enough to write for.

Strong
  • Engineers
  • Founders
  • Technical leaders

Your writing voice

How you naturally write. A couple more samples and I'll match you more closely.

Good

What I noticed in your writing

  • Most code review comments I leave aren't about code.
  • I used to think that made me slow.
  • It takes two minutes.
  • Who calls this?

What you've given me

  • Most code review comments I leave aren't about code. They're about what the code assumes. Who calls this? What happens when the list is empty? Why is this here and not there? I used to think that made me slow. Now I think it's the job.

    Added

  • I stopped writing tickets for myself last month. I write a short note instead: what I'm changing, why, and what I'm unsure about. It takes two minutes. It's the most useful thing I read the next morning.

    Added

⌘↵ to add · I only learn from it, I never post it

Writing preferences

Your explicit choices. They add to what I learn from your edits — they don't replace it. Your choices. I still learn from your edits.

Strong
Tone
Length
Emoji
Approach

In your words

Never in a post

Topics and details I keep out of everything I suggest. I'll keep these out of every draft.

Strong
  • Client and company names
  • List posts and tool roundups
  • Engagement bait (“Agree?”)

Stories I can use

Personal experiences you're happy to see in posts. I only use what you add here — I won't invent any.

⌘↵ to add

What I've learned from you

From what you share, the ideas you develop or skip, and how you edit my drafts. Archive anything I got wrong.