Building your profile

How reviewers actually read profiles

A guild expert reviewing your application has a budget of roughly 15 to 20 minutes per candidate. They don't read your profile the way a recruiter reads a resume — they're looking for evidence that maps to their rubric criteria, and they're making a deliberate effort to form their opinion before seeing anyone else's vote.

That means three things for you as a candidate:

• The first 60 seconds count the most. Headline, current role, primary discipline, and top portfolio link are the first signals they collect. Everything else modifies that first impression.
• Evidence beats adjectives. Specific projects and outcomes get scored. Generic descriptions of skills do not.
• Structure is a favour to the reviewer. A profile that reads as a wall of text gets skimmed. A structured profile with clear sections gets read.

The headline

Your headline is one sentence — maybe twelve words — and it appears above the fold on every view of your profile. It should answer "what do you actually do?" as specifically as you can stand.

A bad headline: Experienced software engineer.
A better headline: Backend engineer focused on high-throughput payment systems.

Work history

The work history section is where most candidates waste space. Three principles:

• Recency matters more than totality. Five years at your current role is more relevant than a fifteen-year chronology. Trim the early jobs to one line each.
• Quantify when you can. "Reduced p95 latency by 40%" is a scored signal. "Worked on performance optimization" is not.
• Name real technologies. Stacks, frameworks, and specific products are keywords a reviewer can anchor on.

Links — LinkedIn, GitHub, portfolio

Add at least one external link. For most engineers, GitHub is the single most-clicked link. For designers, it's the portfolio. For candidates in non-public domains (security research, ML research), LinkedIn plus a personal site is usually enough.

What reviewers do with the links:

• They click through to check that the claims in your profile are consistent with public artifacts.
• For engineers, they often spot-check a recent repo to look at commit patterns and code quality.
• For designers, they look at the highest-rated piece on your portfolio and read its case study.

Application answers

Each job has its own screening questions in addition to the guild's general application questions. Your answers are the single most heavily weighted section of the review — experts score them against specific rubric criteria.

What works:

• Short, specific, structured. Lead with the answer, then the context, then the tradeoffs. Don't bury the point.
• Examples from real projects. Hypotheticals are weaker than actual stories, even when the actual stories are small.
• Honest about what you didn't know. Reviewers regularly rate "I was wrong about X, here's how I figured it out" above "I was right from the start."

What doesn't work:

• Long answers with no structure. Reviewers skim; they don't re-read.
• Copy-paste answers shared across applications. Experts notice, and they talk to each other.
• AI-generated answers. See the no-AI declaration — the penalty for breaches is a platform-wide suspension, not only a guild rejection.

Common pitfalls

• Inconsistent seniority signals. If your headline says "senior" but your experience bullets read as IC-level work, reviewers notice immediately.
• Missing the current role. Profiles without a current employer or self-employed status feel incomplete.
• Links to private resources. GitHub repos gated behind a private org, portfolio PDFs behind a password wall — these are effectively invisible to reviewers.
• Over-polishing. A profile that reads as thesaurus-assisted is less trusted than one that reads as honest. Clarity beats eloquence.