portfolio mini-projects
zero experience? build proof in a weekend. complete one brief, export to pdf, and link it in your resume + linkedin.
how this works
pick one role, follow the template, create proof of your skills
pick your role
choose customer support, admin/ops, project assistant, or marketing assistant
follow the brief
copy templates, fill with your details, work through the scenario
export & share
save as pdf, add to resume, link in linkedin featured section
reference in interviews
walk them through your process and show your thinking
help-center article + bug report
turn a user problem into two assets: a clear help article and a precise bug report
the scenario
user message: "i can't reset my password. it says 'invalid email' after i click the link."
context: addresses containing "+" fail (e.g., alex+notes@mail.com)
environment: web v1.4.2 • chrome 126 • windows 10 • time 14:23 cet
what you'll create
- help-center article with clear steps and workarounds
- bug report that developers can act on immediately
- customer reply template for similar issues
copy these templates
help-center article template
reset your password (web)
when to use: if you can't log in and need a new password
- go to "forgot password" on the sign-in page
- enter your email exactly as you use it to sign in
- open the email "reset your password" (arrives in ~2 minutes)
- click "reset password", set a new password (8+ characters)
workaround: if your email includes a + (like name+notes@gmail.com), enter it without the +... part (name@gmail.com)
still stuck? check spam folder. no email after 5 minutes? contact support with subject "password reset"
bug report template
password reset fails for addresses containing '+'
- environment: web v1.4.2 • chrome 126 • windows 10
- severity: medium (subset blocked; workaround exists)
- steps to reproduce: 1) sign-in → "forgot password" 2) enter user+test@gmail.com 3) submit
- expected: request accepted; reset email sent
- actual: client validation rejects address as "invalid email"
- technical notes: POST /api/reset returns 400 EMAIL_INVALID
- suggested fix: update email regex to accept "+" per RFC 5322
customer reply template
hi <first name>,
thanks for flagging this. some emails with a + can show "invalid email". quick workaround: try the same address without the "+..." part.
we're shipping a fix for this - i'll update you once it's live. if it still doesn't work, reply here and i can reset it for you manually.
thanks for your patience!
<your name>
success checklist
- article solves the issue without needing agent help
- bug report has complete reproduction steps
- customer reply is calm, clear, and helpful
- workaround is clearly explained
- technical details are accurate for developers
how to present this
"authored a help-center article and dev-ready bug report that reduced repeat tickets on a password-reset flow; collaborated asynchronously to ship a fix"
clean messy data + weekly status report
transform chaotic spreadsheet data into a reliable system with clear reporting
the messy data
Task ID,Owner,Due,status,Priority,hours_est,hours_spent
1, alex, 9/2/25, done, high, 3, 2.5
2, , 2025-09-05, In progress, MED, 4,
3, JAMIE, 09-04-2025, todo, low, 1, 0
4, alex, 2025/09/01, ToDo, HIGH, 2, 3
4, alex, 2025/09/01, ToDo, HIGH, 2, 3
5, taylor, 2025-08-31, blocked, med, , 0.5what you'll create
- cleaned dataset with consistent formatting
- validation rules to prevent future errors
- status dashboard with key metrics
- weekly report template for stakeholders
cleanup steps
- remove duplicate entries (task ID 4)
- standardize owner names (capitalize, handle blanks)
- convert all dates to yyyy-mm-dd format
- normalize status values and priority levels
- add calculated fields for overdue and variance
formulas to add
calculated columns
days overdue (column H):
=IF(AND($D2<>"done",$C2<>""), TODAY()-DATEVALUE($C2), "") effort variance (column I):
=IFERROR($G2-$F2,"") status summary pivot:
create pivot table showing counts by status and owner
weekly status report
weekly status report
week of: <yyyy-mm-dd>
overview: 5 active tasks • 1 blocked on assets • average overdue: 1.3 days
by status:
- todo: <count>
- in progress: <count>
- blocked: <count>
- done: <count>
risks & blockers:
- <task> - waiting on <dependency> - due <date>
next week focus:
- <priority 1>
- <priority 2>
- <priority 3>
success checklist
- all data is clean and consistently formatted
- validation rules prevent future errors
- formulas calculate useful metrics automatically
- report clearly communicates status and risks
- next steps are actionable and prioritized
how to present this
"standardized operations sheet with validation rules and formulas; created weekly status template that improved team visibility and reduced status meeting time"
project plan: contact form feature
break down a feature request into tasks, timeline, and risk management
the feature request
feature: "contact us" form (name, email, message fields)
requirements: auto-reply confirmation, inbox copy to support, google sheets logging
constraints: 7-day deadline, 1 developer (part-time), must be mobile-friendly
project breakdown
work breakdown structure (wbs)
1. discovery & planning
- confirm field requirements and validation rules
- research spam prevention options (recaptcha)
- define success criteria and acceptance tests
2. design & setup
- ui mockups for form and success/error states
- email template design for auto-reply
- google sheets structure for logging
3. development
- front-end form with validation
- backend endpoint for form processing
- email integration and templates
- sheets api integration
4. testing & launch
- functionality testing (valid/invalid inputs)
- mobile responsiveness check
- email deliverability testing
- deployment and monitoring setup
7-day timeline
| day | task | owner | done when |
|---|---|---|---|
| 1 | confirm scope + create mockups | pm | stakeholder approval |
| 2 | form ui + validation logic | dev | basic form working |
| 3 | backend endpoint + email setup | dev | test email received |
| 4 | sheets integration + logging | dev | data appears in sheet |
| 5 | qa testing + mobile check | pm | all test cases pass |
| 6 | bug fixes + final polish | dev | ready for production |
| 7 | deploy + documentation | pm | live + handoff complete |
acceptance criteria
- form submission: valid submit shows success message, sends auto-reply in <2 minutes
- validation: invalid email shows inline error, no request sent to server
- logging: every submission creates timestamped row in google sheet
- notifications: support inbox receives formatted email with subject "new contact from <name>"
- mobile: form is fully functional and well-formatted on mobile devices
- spam protection: recaptcha prevents automated submissions
risks & mitigations
risk: spam floods support inbox
mitigation: implement recaptcha + rate limiting (max 3 submissions per hour per ip)
risk: email deliverability issues
mitigation: use verified sender domain, test with gmail/outlook, include fallback notification
risk: google sheets quota exceeded
mitigation: implement error handling, set up monthly archiving of old entries
risk: developer availability reduced
mitigation: prioritize core functionality first, move nice-to-haves to phase 2
success checklist
- work breakdown is complete and logical
- timeline is realistic given constraints
- acceptance criteria are testable and specific
- major risks identified with practical mitigations
- handoff documentation planned
how to present this
"created comprehensive project plan for contact form feature including wbs, 7-day timeline, acceptance criteria, and risk mitigation strategies; coordinated cross-functional delivery"
content repurposing + utm tracking
transform one piece of content into platform-native posts with measurable tracking
source content
"getting a first remote job isn't about sending 100 resumes. it's about showing proof. create one small project per week, track your applications, and learn time-zone fluency so teams can rely on you."
platform adaptations
linkedin post
hook: you don't need experience. you need proof.
body:
- one mini-project per week ←’ learn fast
- a simple application tracker ←’ show you work systematically
- time-zone fluency ←’ teams can rely on you
call to action: grab the free jumpstart kit - simple steps, real results
link: [site]/resources/jumpstart-kit?utm_source=linkedin&utm_medium=social&utm_campaign=jumpstart&utm_content=proof_post
why this works: linkedin prefers professional advice with actionable steps. bullet format scans well in feed.
instagram reel caption
caption:
first remote job in 30 days? start here 👇
• mini-projects ←’ proof without experience
• application tracker ←’ stay organized
• timezone statement ←’ show reliability
save this post and tag a friend who's job searching
free starter kit in bio ✨
visual concept: split screen showing "100 applications" vs "1 project" with checkmarks and progress indicators
alt text: "remote job tips - proof over volume"
twitter thread
thread:
1/ you don't win remote jobs with 100 applications. you win with proof.
2/ do 1 mini-project per week (support article, ops spreadsheet, project plan)
3/ track applications in a simple sheet - follow up systematically
4/ write availability statements in their timezone - show you understand remote work
5/ free kit with templates ←’ [site]/resources/jumpstart-kit?utm_source=twitter&utm_medium=social&utm_campaign=jumpstart&utm_content=thread
why this works: twitter threads perform well with numbered tips. each tweet can stand alone but builds to cta.
utm tracking plan
| platform | utm_source | utm_medium | utm_campaign | utm_content |
|---|---|---|---|---|
| social | jumpstart | proof_post | ||
| social | jumpstart | reel_tips | ||
| social | jumpstart | thread_proof |
tracking goal: measure which platform drives most kit downloads and identify highest-converting content themes
success checklist
- each post fits the platform's native style and format
- clear call-to-action with trackable utm links
- content is scannable and actionable
- utm parameters follow consistent naming convention
- messaging consistent but platform-optimized
how to present this
"repurposed long-form content into 3 platform-native posts with utm tracking; created content calendar system for measuring cross-platform performance and identifying top-converting themes"
ready to create your proof?
pick one project above, spend 2-3 hours this weekend, and you'll have job-ready portfolio pieces to show employers.