Impact & Experience Builder
Learn to write measurable, clear experiences. It autosaves locally on your device.
Why this matters
Your experience should show action + metric + result. We’ll compare good vs bad, practice sorting, then write your own.
What employers look for first
- Action verbs (Developed, Optimized, Led)
- Metrics (% / time / $ / users)
- Results (what improved and how it mattered)
Good vs Bad
Compare examples to see what works.
GOOD Example
Software Engineering Intern
Tech Solutions Inc. • Jun 2024 – Aug 2024
- Built a React/Node dashboard that cut support time by 35%
- Implemented REST APIs for 10,000+ DAU
- Optimized PostgreSQL queries, improving load time by 50%
Skills: JavaScript, React, Node.js, PostgreSQL, Git
Why it works
- Specific + measurable
- Strong verbs
- Clear tools used
BAD Example
Intern
Some Company • Summer 2024
- Worked on code projects
- Helped the team with tasks
- Learned a lot about development
Skills: Coding, Computers, Hard worker
Why it doesn’t work
- Vague, no metrics
- Weak verbs
- No outcome or impact
Interactive: Sort Good vs Bad
Drag each card into the correct column.
Score: 0 / 0
GOOD
Drop the good ones here
BAD
Drop the bad ones here
Write your experience
Start with a brief summary, then add experiences using verbs, metrics, and results.
Experiences
Tip: Use the Action → Metric → Result format. Example: “Optimized SQL queries, reducing latency by 50% and increasing weekly retention by 12%.”
Preview
