Positioning Frameworks
Purpose: Micro-niche identification and positioning statement design for engineer self-branding. Read when: POSITION mode — user needs niche analysis, differentiation strategy, or positioning statement.
Tech × Domain × Perspective Framework
The core positioning model. Engineers differentiate by occupying a unique intersection of three dimensions:
Three Dimensions
| Dimension | Question | Examples |
|---|---|---|
| Tech | What technology stack do you specialize in? | Rust, Kubernetes, React, ML/LLM, Observability |
| Domain | What industry or problem space? | FinTech, HealthTech, EdTech, Gaming, DevTools |
| Perspective | What unique viewpoint do you bring? | Performance-obsessed, DX-first, Security-minded, Accessibility advocate |
Intersection Analysis Template
Tech: [Your primary technology/stack]
Domain: [Your industry/problem space]
Perspective: [Your unique angle/philosophy]
───────────────────────────────────────
Niche: [Tech] × [Domain] × [Perspective]
Example: "Rust × FinTech × Performance-obsessed"
= "金融サービス向け高速処理システムをRustで構築する専門家"Specificity Ladder
Move DOWN for stronger positioning:
| Level | Example | Strength |
|---|---|---|
| L0 (Generic) | "フルスタックエンジニア" | ❌ No differentiation |
| L1 (Tech only) | "Reactエンジニア" | △ Crowded |
| L2 (Tech + Domain) | "FinTech向けReactフロントエンド" | ○ Better |
| L3 (Full intersection) | "金融規制対応UIをReactで構築するアクセシビリティ専門家" | ◎ Strong niche |
Rule: Target L2 minimum, L3 ideal. L0 is an anti-pattern (AP-3).
Positioning Statement Templates
One-Line Format
[Name]は[Domain]領域で[Tech]を活用し、[Perspective]のアプローチで[成果/価値]を実現するエンジニアです。Extended Format (3-sentence)
1. [具体的な専門領域と技術スタック]を持つエンジニアです。
2. [Domain]において[具体的な成果・実績]を達成してきました。
3. [Perspective]を重視し、[提供する独自価値]を追求しています。Elevator Pitch Format (30-second)
[課題/状況の描写]。
私は[Tech]を使って[Domain]の[具体的な問題]を解決しています。
特に[Perspective]にこだわり、[定量的な成果]を実現してきました。
現在は[次の目標/取り組み]に注力しています。Niche Validation Checklist
Before committing to a niche, validate:
| # | Check | Question | Pass Criteria |
|---|---|---|---|
| 1 | Demand | Is there demand in this field? | Jobs, projects, or communities exist |
| 2 | Credibility | Can you back it with track record? | 2+ concrete projects or contributions |
| 3 | Passion | Can you sustain it for 2+ years? | Self-motivated continuous learning |
| 4 | Uniqueness | Are there few competitors in the same position? | Fewer than 10 at the L3 intersection |
| 5 | Storytelling | Do you have stories to tell? | 3+ concrete narratives |
| 6 | Growth | Is the field growing? | Trend is rising or stable |
Minimum: 4/6 pass to proceed. If < 4, adjust dimensions.
Competitive Differentiation Analysis
Personal SWOT Template
| Positive | Negative | |
|---|---|---|
| Internal | Strengths: Technical skills, experience, track record, network | Weaknesses: Areas lacking experience, weak spots |
| External | Opportunities: Market trends, untapped niches | Threats: Increasing competition, technology obsolescence |
Differentiation Matrix
Compare against 3-5 peers in your target niche:
| Factor | You | Peer A | Peer B | Peer C |
|-----------------|-----|--------|--------|--------|
| Tech depth | | | | |
| Domain expertise| | | | |
| Content output | | | | |
| Community role | | | | |
| Unique angle | | | | |Rate each 1-5. Your positioning should emphasize dimensions where you score highest relative to peers.
Niche Pivot Strategy
When shifting positioning (e.g., career change, new tech stack):
Gradual Transition (Recommended)
Phase 1 (Month 1-3): Bridge content — connect old expertise to new domain
Phase 2 (Month 4-6): Dual positioning — maintain old authority while building new
Phase 3 (Month 7-12): Shift emphasis — new niche becomes primary, old becomes backgroundBridge Content Examples
| From | To | Bridge Topic |
|---|---|---|
| Backend → Frontend | "バックエンドエンジニアが語るフロントエンドパフォーマンス" (A backend engineer's take on frontend performance) | |
| Web → ML | "Webエンジニアが実務で使うML基盤構築" (Building ML infrastructure from a web engineer's perspective) | |
| Individual → Manager | "テックリードが学んだエンジニアリングマネジメント" (Engineering management lessons from a tech lead) |
Rule: Never abandon existing authority abruptly. Bridge content lets you carry your audience.
Positioning Anti-Patterns
| Anti-Pattern | Signal | Fix |
|---|---|---|
| Generic Expert | "I can do everything" (e.g. "何でもできます") | Apply Tech×Domain×Perspective framework |
| Tech-Only Identity | "I'm a Rust engineer" (e.g. "Rustエンジニアです") — no domain/perspective | Add domain and perspective dimensions |
| Trend Chaser | Positioning changes with every hype cycle | Commit to a niche for 12+ months |
| Copycat Position | Identical to a well-known engineer | Find your unique perspective angle |
| Aspirational Fraud | Positioning based on desired, not actual expertise | Base on current achievements, add growth goals separately |