Resume Bullets: When to Use Sub-Bullets
The Sub-Bullet Decision
I review hundreds of resumes monthly. The pattern is clear: most candidates either avoid sub-bullets entirely or overuse them into chaos.
Sub-bullets are a tool. Like any tool, they solve specific problems. Use them wrong and they create clutter. Use them right and they add clarity to complex achievements.
The question is not whether to use sub-bullets. The question is when. For the complete methodology on structuring resume content for maximum impact, see our Ultimate Experience Translation Guide.
When Sub-Bullets Work
Sub-bullets solve one problem: a single achievement has multiple components that need explanation but cannot stand alone as separate bullets.
Scenario 1: Complex Project with Multiple Outcomes
The achievement is one thing (led a project) but the results span multiple dimensions.
Without sub-bullets (weak):
• Led platform migration project resulting in 40% cost reduction, 99.9% uptime improvement, and 3x faster deployment cycles while managing team of 8 engineers
This is dense. The reader cannot scan it quickly.
With sub-bullets (strong):
• Led platform migration from on-premise to AWS for 50M+ user application
- Reduced infrastructure costs by 40% ($2M annual savings)
- Improved uptime from 99.5% to 99.9%
- Decreased deployment time from 4 hours to 20 minutes
The main bullet establishes what you did. The sub-bullets prove the impact across three dimensions.
Scenario 2: Achievement with Scope and Scale Details
The achievement is significant, but the scope needs context to be impressive.
Without sub-bullets (loses context):
• Managed company rebrand including new visual identity, website redesign, and marketing materials
With sub-bullets (adds scale):
• Led complete company rebrand for Series B fintech startup
- Directed 4-person design team plus 2 external agencies
- Delivered 200+ assets across digital and print within 3-month timeline
The sub-bullets answer "how big?" and "how fast?" without cluttering the main achievement.
Scenario 3: Technical Implementation with Stack Details
For technical roles, sometimes the stack matters as much as the outcome.
Without sub-bullets (incomplete picture):
• Built real-time analytics dashboard used by 500+ enterprise customers
With sub-bullets (adds technical depth):
• Built real-time analytics dashboard serving 500+ enterprise customers
- Stack: React, D3.js, GraphQL, PostgreSQL with TimescaleDB
- Handles 10K events/second with sub-100ms query response
The sub-bullets add technical credibility without making the main bullet unreadable.
When Sub-Bullets Fail
Sub-bullets fail more often than they succeed. Here are the patterns to avoid.
Failure 1: Sub-Bullets That Repeat the Main Bullet
Bad:
• Increased sales revenue by 35%
- Grew sales by over one-third
- Revenue went up significantly
The sub-bullets add nothing. They restate what the main bullet already said. Delete them.
Failure 2: Sub-Bullets That Should Be Main Bullets
Bad:
• Contributed to product development
- Launched mobile app with 100K downloads in first month
- Redesigned checkout flow increasing conversion by 25%
- Built recommendation engine driving 15% of total revenue
These sub-bullets are stronger than the main bullet. Each deserves to be its own main bullet. The "contributed to product development" framing actually weakens them.
Better:
• Launched mobile app achieving 100K downloads in first month
• Redesigned checkout flow, increasing conversion by 25%
• Built recommendation engine driving 15% of total revenue
Failure 3: More Than Two Sub-Bullets
Bad:
• Managed marketing operations
- Oversaw email campaigns
- Managed social media accounts
- Coordinated with PR agency
- Handled event logistics
- Maintained CRM database
- Produced monthly reports
This is not bullet hierarchy. This is a nested list of duties. No sub-bullet stands out because there are too many.
If you need more than two sub-bullets, either consolidate or split into separate achievements.
Failure 4: Sub-Bullets Without a Strong Main Bullet
Bad:
• Various responsibilities in the role
- Managed budget of $500K
- Led team of 4 analysts
The main bullet is weak. The sub-bullets are doing all the work. Rewrite:
Better:
• Managed $500K annual budget and team of 4 analysts for market research division
Now it is one strong bullet instead of a weak hierarchy.
The Two Sub-Bullet Rule
After reviewing thousands of resumes, I established this rule: Maximum two sub-bullets per main bullet.
Why two?
One sub-bullet: Works for adding a single important detail (scope, secondary metric, technical context).
Two sub-bullets: Works for contrasting or complementing details (before/after, cost/time, qualitative/quantitative).
Three or more sub-bullets: Creates scanning problems. The eye loses track of hierarchy. The main bullet gets buried.
If you need three sub-bullets, ask: Can any of these stand alone as main bullets? Usually the answer is yes.
Formatting Sub-Bullets Correctly
Visual formatting determines whether sub-bullets clarify or confuse.
Indent Depth
Sub-bullets should be indented 0.25 to 0.5 inches beyond main bullets.
Too shallow (0.1 inch): Hierarchy is unclear. Sub-bullets look like main bullets.
Too deep (0.75+ inch): Wastes horizontal space. Text becomes cramped.
Just right (0.25-0.5 inch): Clear visual distinction without wasting space.
Bullet Symbol Differentiation
Use different symbols for different levels:
Main bullets: Solid circle (•) or solid square (■) Sub-bullets: Dash (-), hollow circle (○), or smaller solid circle
This visual distinction reinforces the hierarchy at a glance.
Consistent Formatting
Whatever style you choose, apply it consistently:
ATS Considerations
Most ATS systems handle standard sub-bullets correctly. However, some parsing issues can occur.
What Works
- One level of sub-bullets (main bullet → sub-bullet)
- Standard bullet symbols (•, -, ○)
- Standard indent formatting
- Text-based bullets (not graphics or icons)
What Breaks
- Multiple nesting levels (main → sub → sub-sub)
- Custom bullet symbols (★, ➤, ✓)
- Extreme indentation (1+ inch)
- Bullets created with graphics or text boxes
The Safe Approach
If you are uncertain about the ATS being used:
- Limit yourself to one level of sub-bullets
- Use standard symbols (• for main, - for sub)
- Keep indentation to 0.25-0.5 inches
- Test by copying your resume to plain text
If the hierarchy survives the plain text test (sub-bullets still appear indented or distinguished), it will parse correctly.
Role-Specific Guidance
Different roles have different sub-bullet conventions.
Technical Roles (Engineering, Data Science)
Sub-bullets work well for:
- Technical stack details under project achievements
- Performance metrics under system implementations
- Scale indicators under infrastructure work
Example:
• Rebuilt payment processing system handling $50M monthly volume
- Reduced transaction failures from 2.3% to 0.4%
- Tech: Stripe, PostgreSQL, Redis, Kubernetes
Business Roles (Product, Marketing, Operations)
Sub-bullets work well for:
- Multiple outcome dimensions (revenue + efficiency)
- Scope context (team size, budget, timeline)
- Before/after comparisons
Example:
• Launched customer loyalty program for 2M+ member base
- Increased repeat purchase rate from 23% to 41%
- Generated $4M incremental revenue in first year
Leadership Roles (Management, Executive)
Sub-bullets work well for:
- Team and budget scope under leadership statements
- Strategic outcomes under transformation initiatives
- Multi-dimensional impact under major decisions
Example:
• Led digital transformation initiative across 3 business units
- Managed $12M budget and cross-functional team of 45
- Achieved 30% operational efficiency gain within 18 months
Entry-Level Roles
Sub-bullets are usually unnecessary. Entry-level resumes should prioritize volume of distinct achievements over depth of detail. Use main bullets only unless an achievement truly requires supporting context.
The Decision Framework
Use this framework to decide whether an achievement needs sub-bullets.
Question 1: Can the main bullet stand alone?
If yes: The main bullet works. Sub-bullets are optional. If no: You need either sub-bullets or a rewrite.
Question 2: Are the supporting details subordinate or parallel?
If subordinate (supporting the main point): Use sub-bullets. If parallel (equally important achievements): Use separate main bullets.
Question 3: Will sub-bullets improve or slow scanning?
If the sub-bullets add clarity: Include them. If the sub-bullets add clutter: Remove them.
Question 4: Can you limit to two sub-bullets?
If yes: Proceed with sub-bullets. If no: Reconsider the structure. Split or consolidate.
Before and After Examples
Example 1: Overloaded Main Bullet
Before:
• Managed product launch including market research, competitive analysis, pricing strategy, go-to-market plan, sales enablement materials, and launch event coordination resulting in 150% of first-quarter targets
After:
• Led product launch achieving 150% of Q1 revenue targets ($3M)
- Developed pricing strategy based on competitive analysis of 12 market alternatives
- Created sales enablement package adopted by 40-person sales team
The main bullet now leads with the outcome. Sub-bullets add process context.
Example 2: Weak Hierarchy Hiding Strong Achievements
Before:
• Contributed to engineering team
- Reduced API latency by 60%
- Implemented caching layer serving 1M requests/day
After:
• Reduced API latency by 60% through implementation of distributed caching layer
• Scaled caching infrastructure to handle 1M+ daily requests with 99.9% hit rate
The achievements were strong enough to stand alone. No hierarchy needed.
Example 3: Appropriate Use of Sub-Bullets
Before:
• Managed annual budget
• Oversaw team of analysts
• Delivered cost savings
After:
• Managed $2.5M annual operating budget for analytics department
- Led team of 6 analysts across 3 time zones
- Identified $400K in cost savings through vendor consolidation
The budget management is the main responsibility. Team leadership and cost savings are supporting details that add scale and impact.
Frequently Asked Questions
Should I use sub-bullets on my resume?
Use sub-bullets sparingly for complex achievements that need supporting details. Most resume bullets should stand alone. If you need more than two sub-bullets, consider splitting into separate main bullets instead.
How many sub-bullets are too many?
More than two sub-bullets under a main bullet creates visual clutter. If an achievement needs three or more supporting points, break it into multiple main bullets or consolidate the information.
Do sub-bullets hurt ATS parsing?
Standard sub-bullets parse correctly in most ATS systems. However, deeply nested bullets (three levels or more) may cause parsing issues. Stick to one level of sub-bullets maximum.
When should I use sub-bullets vs separate bullets?
Use sub-bullets when details are subordinate to a main achievement (supporting metrics, scope, or context). Use separate bullets when each point can stand independently as a distinct accomplishment.
What indent should I use for sub-bullets?
Use 0.25 to 0.5 inches of additional indent for sub-bullets. This creates clear visual hierarchy without wasting horizontal space. Match the indent consistently throughout your resume.
Should sub-bullets have the same format as main bullets?
Sub-bullets should use a different bullet symbol (dash or hollow circle) than main bullets (solid circle). This visual distinction reinforces the hierarchy and improves scannability.
Final Thoughts
Sub-bullets are a precision tool. They clarify complex achievements that cannot be expressed in a single line. They fail when used as a dumping ground for responsibilities or when they bury strong achievements under weak framing.
The rule is simple: main bullet carries the headline achievement, sub-bullets add essential supporting context, and you never exceed two sub-bullets per main bullet.
When in doubt, test by removing the sub-bullets. If the main bullet stands strong alone, you probably do not need them. If the main bullet collapses without support, the sub-bullets are earning their place. For the philosophical foundation on why resume structure matters—proving value instead of listing biography—see our Experience Translation Manifesto.
