AlgoInsight

Free lesson · The Job Search System

The About Section: Your Professional Story

Easy10 min readjob-searchcareerresume

The About Section: Your Professional Story

Student: Olena, I've updated my headline. Now what about the About section? Mine is currently empty.

Olena: An empty About section is one of the most common mistakes I see. LinkedIn's data shows that profiles with completed About sections receive significantly more search appearances, because LinkedIn's algorithm uses the About section text for search matching. An empty About section means you're invisible for searches that rely on context beyond your headline and title.

But the About section is also where most people go wrong - they either copy-paste their resume summary (which is redundant) or write a wall of text that nobody reads. Let me show you how to write an About section that does actual work.

What the About Section Is (and Isn't)

Your About section is NOT your resume summary. Your resume lives on your profile as separate experience entries. The About section serves a different purpose - it's the one place on LinkedIn where you speak in first person, in your own voice, and tell a story that your resume can't.

Your About section IS:

Student: How long should it be?

Olena: 150 to 300 words. LinkedIn shows the first 3 lines (about 300 characters) before the "see more" fold. Those first 3 lines need to hook the reader - if they don't, nobody clicks "see more." The rest of the section provides depth for the people who do.

The Three-Part About Section Structure

graph TD
    A["PART 1: The Hook<br/>First 3 lines (above the fold)<br/>Who you are + what makes you<br/>interesting in 2 sentences"] --> B["PART 2: The Story<br/>Your professional narrative<br/>What you build, why it matters,<br/>what problems you solve<br/>3-5 sentences"]
    B --> C["PART 3: The Signal<br/>What you're looking for<br/>Technologies, domains, interests<br/>2-3 sentences + keyword block"]

    style A fill:#ff6b6b,color:#fff
    style B fill:#339af0,color:#fff
    style C fill:#51cf66,color:#fff

This diagram shows the three-part About section structure. Part 1 is the Hook - the first 3 lines above the fold that tell who you are and what makes you interesting in 2 sentences. Part 2 is the Story - your professional narrative explaining what you build, why it matters, and what problems you solve, in 3 to 5 sentences. Part 3 is the Signal - what you're looking for, including technologies, domains, and interests, in 2 to 3 sentences plus a keyword block.

Part 1: The Hook (Above the Fold)

This is the most critical part because it's the only part most people read. The first 3 lines need to answer: "Who is this person, and why should I keep reading?"

Bad hook: "Passionate software engineer with 5 years of experience seeking new opportunities. I love to code and solve problems."

Good hook: "I build the systems that move money. For the last five years, I've designed payment processing infrastructure that handles millions of transactions daily - the kind of systems where a bug doesn't just cause a crash, it causes people to lose money."

The good hook does three things: it's specific (payment processing), it establishes scale (millions of transactions), and it creates intrigue (the stakes are real). A recruiter reading this wants to know more.

Student: How do I make my work sound that interesting? I build CRUD APIs.

Olena: Find the stakes. Every system has users who depend on it. Your CRUD APIs serve a product that people use. What happens when those APIs fail? What's the scale? What decisions have you made that weren't obvious? "I build the API layer that powers a healthcare scheduling platform serving 2,000 clinics. When our APIs go down, patients can't book appointments - so I design for reliability first."

Even seemingly mundane work has stakes when you connect it to the people who depend on it.

The hook writing process: If you're stuck, try this exercise. Answer these three questions: (1) Who uses the things I build? (2) What happens when the things I build don't work? (3) What's the most technically interesting problem I've solved recently? Your hook lives at the intersection of these three answers.

For example, an engineer who builds internal tooling might answer: (1) "200 engineers use my CI/CD pipeline daily," (2) "When it breaks, nobody can deploy," (3) "I reduced build times from 45 minutes to 8 minutes." Their hook: "I build the infrastructure that 200 engineers depend on to ship code every day. When my systems are fast, the whole company moves faster - last quarter, I cut build times by 82%, which translated to roughly 1,500 engineering hours saved."

That's a compelling hook for work that most people would describe as "I maintain CI/CD pipelines."

Part 2: The Story (Your Professional Narrative)

This is where you tell your career story in a way your resume can't. The resume shows what you did and where. The About section shows how you think about your work.

Effective approaches:

The specialist story: "I specialize in distributed systems - specifically the problems that emerge when you try to maintain consistency across data centers that are 5,000 miles apart. At DataCorp, I designed a cross-region replication system that cut data recovery time from 4 hours to 12 minutes. Before that, at StartupX, I built the event-driven architecture that lets us process 500K events per minute."

The transition story: "I started my career as a financial analyst at PwC, building Excel models and analyzing market data. Somewhere along the way, I realized I was spending more time automating my own workflows in Python than doing actual analysis. That was the signal. I taught myself to code, built production applications, and transitioned to full-time engineering. My financial background gives me a perspective that most engineers lack - I understand the business context behind the systems I build."

The builder story: "I'm an engineer who cares about the full lifecycle - not just writing code, but understanding why we're building it, how users interact with it, and what happens when it breaks at 3am. I've shipped systems at startup scale (12-person team, move fast, wear every hat) and enterprise scale (Amazon, 300-person org, design reviews, operational excellence). I bring the best of both worlds."

Part 3: The Signal (What You're Looking For)

The final section of your About tells the reader what you want next. This serves two audiences: recruiters who want to know if you're open to opportunities, and hiring managers who want to know if your interests align with their team.

Example signal section: "I'm most interested in backend infrastructure roles at companies solving complex distributed systems problems - payments, real-time data, or platform infrastructure. Currently exploring opportunities in the Bay Area and open to remote."

Below this, add a keyword block - a line of technologies and skills that serves as additional search bait:

"Technologies: Java, Go, Python, AWS (EC2, S3, Lambda, SQS), Kubernetes, Docker, PostgreSQL, Redis, Kafka, Terraform, gRPC"

Student: Won't that keyword block look weird at the bottom of my About section?

Olena: It's a standard convention on engineering LinkedIn profiles. Recruiters expect it. Think of it as the "skills" line at the bottom of your resume - it's functional, not decorative. Some engineers format it as a labeled list: "Languages: Java, Go, Python | Cloud: AWS, GCP | Infrastructure: Kubernetes, Docker, Terraform | Data: PostgreSQL, Redis, Kafka." This is clean, scannable, and packed with searchable keywords.

The keyword block should include technologies you work with regularly and can discuss confidently in an interview. Don't list technologies you used once three years ago - if a recruiter finds you through a Terraform search and you can't discuss Terraform in detail, the mismatch will cost you credibility in the conversation.

How often should you update the About section? At minimum, review it every 6 months. Update it whenever your professional focus changes - new technology stack, new domain, new role, new career goals. If you start actively job searching, update it immediately to include what you're looking for. If you land a new role, update it to reflect your current position and remove the "open to opportunities" language.

Tip: The keyword block at the end of your About section is free SEO. LinkedIn's search algorithm indexes your entire About section. A clean line of technologies at the bottom ensures your profile appears in searches for specific skills even if those skills aren't prominently featured in your headline or experience section. Think of it as the skills section of your resume, but for LinkedIn search.

Writing Tone and Voice

Student: How formal should the About section be?

Olena: First person, conversational, professional. Not a cover letter. Not a text message. Imagine you're introducing yourself to a senior engineer at a conference - confident, specific, human.

Avoid:

Warning: Don't copy your resume summary into your About section. Recruiters and hiring managers often read both your resume and your LinkedIn profile. If the About section is identical to the resume summary, it feels lazy and provides no additional information. The About section should tell the parts of your story that the resume CAN'T tell - the why, the how-you-think, the what-you-want-next.

Career-Stage-Specific About Sections

For new grads: Lead with what excites you about engineering and what you've built. Your About section compensates for thin work experience. "I just graduated from [University] where I spent the last two years obsessed with systems programming. My senior thesis involved building a custom memory allocator that reduced allocation latency by 40% compared to glibc malloc. I'm looking for backend or systems roles where I can work on performance-critical infrastructure."

For career switchers: Lead with the transition narrative. Own it confidently. "Three years ago, I was a financial analyst. Today, I'm a software engineer building data-intensive applications. The transition wasn't accidental - I realized that the problems I loved solving (data analysis, process optimization, automation) were engineering problems dressed in business clothes."

For experienced engineers: Lead with your domain and your philosophy. "After 8 years building distributed systems at [Company A] and [Company B], I've developed a strong point of view: the best systems aren't the cleverest - they're the ones that fail gracefully. I specialize in designing infrastructure that's boring in production, because boring means reliable."

For international candidates: Lead with your global perspective and current authorization. "Software engineer with 9 years of experience across Lagos, London, and Amsterdam, now based in the Bay Area. I've built data platforms processing billions of events daily at Booking.com and Netflix. My cross-continental experience gives me a perspective on engineering for global scale that few engineers have."

Common About section mistakes to avoid:

The resume dump. Pasting your resume bullets directly into the About section creates redundancy. A recruiter who reads your About section and then scrolls to your experience finds the same information twice. The About section should complement your experience, not repeat it - it tells the why and how-you-think, while experience tells the what.

The technology laundry list. "I work with Java, Python, Go, Rust, TypeScript, React, Angular, Vue, Node.js, Spring Boot, Django, Flask, AWS, GCP, Azure, Kubernetes, Docker, Terraform..." This isn't an About section - it's a skills section in disguise. Save the exhaustive tech list for the keyword block at the bottom.

The philosophical essay. "Software engineering is the art of turning human needs into digital solutions. In a world increasingly defined by technology, I believe that the role of the engineer is..." Stop. Nobody reads abstract philosophy on LinkedIn. Lead with something concrete about your specific work and experience.

The empty section. The worst option. An empty About section tells the recruiter one of two things: you don't care about your professional presence, or you couldn't figure out what to say about yourself. Neither interpretation helps you.

graph TD
    A["Career Stage"] --> B["New Grad<br/>Lead with: What you've built<br/>and what excites you"]
    A --> C["Career Switcher<br/>Lead with: The transition story<br/>framed as intentional"]
    A --> D["Experienced<br/>Lead with: Your domain<br/>and engineering philosophy"]

    B --> E["'I just built X.<br/>I'm looking for Y.'"]
    C --> F["'I transitioned from X to Y.<br/>Here's why and what I bring.'"]
    D --> G["'After N years doing X,<br/>here's what I believe.'"]

    style B fill:#339af0,color:#fff
    style C fill:#fcc419,color:#000
    style D fill:#51cf66,color:#fff

This diagram shows how to approach the About section by career stage. New grads lead with what they've built and what excites them - the format is I just built X and I'm looking for Y. Career switchers lead with the transition story framed as intentional - the format is I transitioned from X to Y and here's why. Experienced engineers lead with their domain and engineering philosophy - the format is after N years doing X, here's what I believe about engineering.

Important: Your About section should change when your goals change. If you're happily employed and not looking, your About section can be a general professional introduction. When you start actively searching, update it to include what you're looking for. When you land a new role, update it again. The About section is a living document, not a permanent fixture.

Interview: The About Section and "Tell Me About Yourself"

Your About section and your interview "Tell Me About Yourself" answer should tell the same story. If your About section frames you as a distributed systems specialist, your interview answer should reinforce that framing. Consistency between your LinkedIn presence and your verbal self-presentation creates credibility. Inconsistency creates doubt.

Exercise: Starter: Write your About section using the three-part structure (Hook, Story, Signal). Keep it to 200 words. Read the first 3 lines - would you click "see more" if you saw this on someone else's profile? If not, rewrite the hook.

Intermediate: Find 5 About sections you admire from engineers in your target domain. Copy their structure (not their words). Notice what makes them compelling - specificity, stakes, personality, clarity. Use those techniques in your own section.

Advanced: Write two versions of your About section - one for when you're passively open (employed but would consider the right opportunity) and one for when you're actively searching. The passive version focuses on what you do and how you think. The active version adds what you're looking for and what kind of company excites you. Save both. Switch between them as your job search status changes.

Student: I actually feel excited to write my About section now. It feels like a chance to say something my resume can't.

Olena: That's exactly what it is. In the next topic, we're building out your experience, Featured section, and projects on LinkedIn - the sections that mirror your resume but work differently on this platform.

Let's go.

Back to The Job Search System