LinkedIn, step by step
Steps 1–6 take about 4 hours in Month 1. Then post every two weeks. Your best asset is real proof: 1,500+ merged PRs since September 2024 on a live trading platform. Before you name internal projects, check with your manager what is public.
Photo
- Your face fills about 60% of the frame. Plain background, daylight.
- Smile and look at the camera. No sunglasses, no cropped group photo.
- Use the same photo on GitHub.
Banner (1584 × 396 px)
Make it free in Figma or Canva. Your name, one line about what you do, 3 keywords. Dark background, one accent color. Keep the bottom-left empty — your photo covers it.
Mohammad Mohsen Hosseini Building trading products for web and mobile TypeScript · React · Next.js · React Native
Headline
Up to 220 characters. Formula: role at company · what you build · what's next.
Use the "Today" version now. Switch to your path's version in Month 6, once you have proof.
Today: Software Engineer at Technance · React, Next.js, React Native · Building trading products for web and mobile Software Engineer path: Software Engineer at Technance · TypeScript, React, Node.js · Web, mobile and realtime trading systems Product Manager path: Product-minded Engineer at Technance · Turning user problems into shipped, measured features · 1,500+ PRs shipped Technical Product Manager path: Engineer → Technical Product Manager · 1,500+ PRs shipped at Technance · APIs, platforms and trading products
Custom URL and basics
- Profile → "Edit public profile & URL" → set linkedin.com/in/mowhcen, the same name as your GitHub.
- Add your location and industry.
- Contact info: add your GitHub and your live Pace link.
About
Four short paragraphs: what you do, proof with numbers, how you work, what's next. Fill in the [brackets]. Delete anything that is not public.
I build trading products at Technance: web apps in Next.js, a React Native mobile app, and the services behind them. Since September 2024 I've merged 1,500+ pull requests in a large TypeScript monorepo — trading screens, a mobile companion app, a help center service that replaced Zendesk, a Forex web app, and a Slack bot that runs our mobile releases. What I enjoy most is the whole path from a fuzzy problem to a shipped, measured feature: shaping the plan, building it, and making sure it lands well for users. Now I'm growing toward [your path]. I share what I learn here every two weeks. GitHub: github.com/mowhcen
Experience: Technance
Each bullet = action + what + result. Numbers win. Keep 4–6 bullets. Delete any you can't share.
[Your title] · Technance · [start month] 2024 – Present - Merged 1,500+ pull requests in a Turborepo TypeScript monorepo (Next.js, React, Expo React Native). - Built a help center service (Hono, Postgres, Drizzle) that replaced Zendesk Guide: articles, search, votes and an admin editor. - Shipped a Forex web app end to end: sign-in, a deposit flow embedded in a partner CRM, and the landing page. - Built a Slack release bot that posts every mobile build and drafts Play Store release notes. - Worked on realtime trading UI: order book, positions, TP/SL and TradingView charts. - [Add one result with a number: a faster page, fewer errors, more sign-ups.]
Skills
Add up to 50; pin the top 5 for your path.
- Software Engineer: TypeScript, React, Next.js, Node.js, System Design
- Product Manager: Product Discovery, Product Strategy, Roadmapping, A/B Testing, SQL
- Technical PM: Technical Product Management, API Design, System Design, Product Discovery, SQL
Featured
Pin 3 things: the live Pace site, your best post, and later your capstone case study.
Recommendations
Ask 2 people who saw your work up close: your lead, and one PM or designer. Make it easy — tell them what to mention.
Hi [name], I'm updating my LinkedIn as I grow toward [path]. Would you write a short recommendation? If it helps, you could mention [project] and how we worked together on [thing]. I'm happy to write one for you too. Thank you!
Open to work
Growing inside Technance? Skip it.
Looking outside? Turn it on for "recruiters only" (other people can't see it) and list the exact job titles you want.
Posting rhythm
One post every two weeks, about 20 minutes to write. Build in public: show the real chart and the real lesson.
Then 10 minutes a day: 3 thoughtful comments on posts by people in your target role. Comments grow your network faster than posts.
I'm starting a 6-month plan to grow from software engineer toward [your path]. Instead of a to-do list, I built a small tool for it: Pace — a roadmap that re-plans itself. If I fall behind, it measures my real pace, shows the new finish date, and tells me how many hours a week I'd need to catch up. React + TypeScript, runs fully in the browser, free to host on GitHub Pages. Live: [link] Code: [link] I'll share what I learn every two weeks. What's one thing you wish you'd learned earlier in your career?
Post ideas
- Month 1: kickoff — the plan and Pace
- Month 2: one lesson from a course, with an example
- Month 3: the honest chart after 3 months
- Month 4: demo of a tool you built
- Any month: teardown of a product you admire
- Month 5: halfway — what changed
- Month 6: capstone launch and case study