Build · Break · Fix · Explain
10-Day Salesforce Project Sprint
Build real Salesforce applications from scratch, strengthen your development skills, and learn to explain your projects confidently in interviews.
New to Salesforce Development?
Follow in order: Project 1 → 2 → 3 → 4 → 5
Already Know Salesforce?
Jump ahead: Project 3 → 4 → 5
How It Works
- Pick a project matching your level
- Follow the Day 1 to Day 10 breakdown (roughly 1–2 hours a day)
- Build it yourself in a free Developer Org — don't copy the solution blindly
- Answer the Mini Interview Challenge at the end of each project
- Post it on LinkedIn and tag SFInterviewPro to get featured on the Wall of Builders
💡 When you click "Share on LinkedIn," add a line about what you built, then type @SFInterviewPro in your post to tag us — LinkedIn requires this to be typed manually, links can't auto-tag.
The 5 Projects
Project 1: Recruitment Tracker
Data Modeling · Validation Rules · Flow · Reports
Scenario: An HR team is tracking job openings and candidates in spreadsheets. Build a Salesforce app that manages postings, candidates, and hiring stages.
Day-by-Day
- Day 1–2: Create custom objects (Job Posting, Candidate) with relationships and fields
- Day 3–4: Build page layouts, record types, validation rules for screening steps
- Day 5–6: Build a Record-Triggered Flow to auto-notify the hiring manager on stage change
- Day 7–8: Build a Screen Flow for interview scheduling
- Day 9: Build a dashboard showing open positions and pipeline by stage
- Day 10 — Portfolio Day: Screenshot your build, record a 3-min demo, write your design decisions, add it to your resume, and share on LinkedIn
By Day 10 You'll Have
✅ Candidate management system ✅ Automated interview scheduling
✅ Recruitment pipeline tracking ✅ Validation rules for data quality
✅ Reports and dashboard ✅ Automated hiring manager notifications
What You'll Learn
- When to use a Lookup vs Master-Detail relationship
- How Record-Triggered Flows traverse related records
- How to protect data quality with Validation Rules
- How to explain your automation choices in an interview
🎤 Interview Challenge — Can You Explain It in 60 Seconds?
• "Why did you use a Flow instead of a Workflow Rule here?"
• "What happens if 500 candidates get imported at once?"
• "How would you extend this for region-specific hiring stages?"
Resume-Ready Line
"Designed and implemented a Salesforce recruitment management solution using custom objects, validation rules, Flow automation, reports and dashboards."
Project 2: Automated Approval Engine
Approval Processes · Flow · Record Locking · Reports
Scenario: A company needs discount approvals on Opportunities to route automatically based on discount percentage and region, instead of manual email chains.
- Day 1–2: Map the business rule (discount thresholds, approver hierarchy)
- Day 3–4: Build a multi-step Approval Process with dynamic approver routing
- Day 5–6: Add Approval History related list and email alerts
- Day 7–8: Build a Flow to lock/unlock records during approval
- Day 9: Build a report showing average approval turnaround time
- Day 10 — Portfolio Day: Write a one-page case study, screenshot the flow, record a demo, and share on LinkedIn
🎯 By Day 10 You'll Have
✅ Multi-step approval engine ✅ Dynamic approver routing
✅ Record locking during approval ✅ Turnaround-time report
🎤 Interview Challenge — Can You Explain It in 60 Seconds?
"Why did you use record locking? What happens if two approvers act at the same time? How would you handle a re-submission after rejection?"
Resume line: "Built an automated multi-step approval engine with dynamic routing, record locking, and turnaround-time reporting."
Project 3: Repeat Order LWC Widget
Apex · LWC · Wire Service · Bulkification
Scenario: Sales reps want to quickly re-order previously purchased products for a customer without rebuilding a quote from scratch.
- Day 1–2: Design data model (past Order, Order Product, Account relationship)
- Day 3–4: Build Apex controller to fetch a customer's last 90 days of orders
- Day 5–6: Build LWC modal with a searchable, selectable product list
- Day 7–8: Add "Create New Order" logic with quantity editing
- Day 9: Add error handling, loading spinners, toast notifications
- Day 10 — Portfolio Day: Write test classes (90%+ coverage), document the component, record a demo, and share on LinkedIn
🎯 By Day 10 You'll Have
✅ Working Repeat Order LWC ✅ Bulk-safe Apex controller
✅ 90%+ test coverage ✅ Polished UX with error handling
🎤 Interview Challenge — Can You Explain It in 60 Seconds?
"Why wire service over an imperative call here? How does your controller stay bulk-safe? What breaks if 10,000 orders exist for one account?"
Resume line: "Developed a Lightning Web Component enabling reps to re-order from purchase history, backed by a bulkified Apex controller."
Project 4: Executive Dashboard with Filters and Export
SOQL · LWC · Aggregate Queries · CSV Export
Scenario: A sales VP wants a single screen answering: where does the pipeline stand, which deals are stuck, and who are the top reps this quarter.
- Day 1–2: Define KPIs and build underlying reports/report types
- Day 3–4: Build an LWC with SOQL aggregate queries for pipeline by stage/territory
- Day 5–6: Add dynamic filters (date range, territory, owner)
- Day 7–8: Add CSV export functionality
- Day 9: Style with SLDS, conditional formatting for at-risk deals
- Day 10 — Portfolio Day: Record a walkthrough of each metric, document the build, and share on LinkedIn
🎯 By Day 10 You'll Have
✅ Executive pipeline dashboard ✅ Dynamic filters
✅ CSV export ✅ At-risk deal highlighting
🎤 Interview Challenge — Can You Explain It in 60 Seconds?
"Why aggregate SOQL instead of pulling all records into Apex? How do you avoid hitting governor limits at scale? Why a Lightning Datatable here?"
Resume line: "Built an executive sales dashboard with dynamic filters and CSV export, surfacing pipeline health across territories."
Project 5: Duplicate Detection and Merge System
Batch Apex · Fuzzy Matching · LWC · Data Quality
Scenario: A company's Account database has thousands of duplicate records from years of manual entry. Build a system to detect and resolve them.
- Day 1–2: Set up native Duplicate Rules and Matching Rules as baseline
- Day 3–4: Build a custom Apex batch job using fuzzy string matching
- Day 5–6: Build an LWC review screen with merge/ignore actions
- Day 7–8: Build merge logic (reassign child records before merge)
- Day 9: Add a scheduled batch to re-scan weekly, log results
- Day 10 — Portfolio Day: Document data quality improvement with before/after counts, record a demo, and share on LinkedIn
🎯 By Day 10 You'll Have
✅ Batch-driven dedup system ✅ Fuzzy-match scoring logic
✅ Merge review LWC ✅ Weekly scheduled re-scan
🎤 Interview Challenge — Can You Explain It in 60 Seconds?
"Why aren't native Duplicate Rules enough here? How do you safely reassign child records before a merge? How would you tune your match threshold to avoid false positives?"
Resume line: "Built a batch-driven duplicate detection and merge system using fuzzy matching, reducing duplicate Account records significantly."
Track Your Progress
Copy this checklist into your notes app and check off each day. Screenshot it on Day 10 and post it on LinkedIn.
Day 1 □ Day 2 □ Day 3 □ Day 4 □ Day 5 □
Day 6 □ Day 7 □ Day 8 □ Day 9 □ Day 10 □
🏆 Finished the Project?
You've built it. Now prove you can explain it.
① Record your demo
② Share your build on LinkedIn
③ Add it to your resume
④ Get featured on the Wall of Builders
⑤ Try a Mock Interview on your project
Wall of Builders
Shoutout to the builders who've completed projects so far:
Share your solution on LinkedIn and tag @SFInterviewPro to get your name added here too.
FAQ
Is this really free?
Yes, completely free, no signup, no paywall. Same as everything else on sfinterviewpro.com.
Do I need a paid Salesforce org?
No. You can build these projects using a free Salesforce Developer Edition org (signup.salesforce.com). Some advanced features, like Project 5's batch processing, may need to be adapted to the limits of your org.
What if I get stuck?
Try for a day first, then check the solution page once it's live. Struggling through it is where the real learning happens.
Can I submit a project I built differently than the solution?
Absolutely. There's no single right answer. Share whatever you built, that's the point of a portfolio.
Do I have to do them in order?
No, pick whichever matches your current skill level. Beginners should start with Project 1 or 2.
New project drops every week. Bookmark this page.
Explore the full course library at sfinterviewpro.com