Fetch Rewards software engineer candidates commonly report a take-home project first, often before any recruiter call, followed for some by a screen or engineer interview about their project and stack.
$135K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Fetch Rewards software engineer process as starting with a take-home project, often sent before they had spoken to anyone on the team. The brief is framed as a few hours of work, but candidates report spending anywhere from several hours to several days to finish it well. Reported tasks include a front-end app built on a provided API with login or authentication, pagination, filtering, sorting and favoriting. Another is a receipt-processing API built in the language and framework of your choice; in one case it was extended with points rules for a first-time user and for first and third receipts. Some briefs asked for public deployment, a public GitHub repo, a README and documentation, and one said not to use AI.
After submission, candidates who advanced describe two kinds of next step. One was a recruiter conversation about their background followed by a tech-team interview on experience and the stack. The other was a technical screen that mixed screening questions with improvements to the app they had built. One candidate was asked to modify their project live, for example adding sign-in error messages or showing query parameters in the URL without a reload. Later rounds were mentioned but not described firsthand.
Outcomes in this set are rejections, usually generic and without feedback. Several candidates report waits of about a week to well over two weeks despite a promised 24 to 48 hour review. Prepare by treating the take-home like production code and keeping notes on your design choices. Practice making small live extensions to your own app so you can defend and change it on the spot.
Synthesized from 17 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Fetch Rewards, Inc. process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Fetch Rewards, Inc.
Design a secure, real-time, scalable portfolio management system with notifications and caching.
| Question | |
|---|---|
| Rider Discount | |
| Receipt Scoring Microservices | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Closest SAT Scores | |
| Employee Salaries | |
| Top 3 Users | |
| Customer Orders | |
| Prime to N | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| String Shift | |
| Rolling Bank Transactions | |
| Flight Records | |
| Comments Histogram | |
| Random SQL Sample | |
| Weighted Keys | |
| Job Recommendation | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Upsell Transactions | |
| Retailer Data Warehouse | |
| Permutation Palindrome | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report receiving a take-home assignment first, often before any recruiter conversation. Reported tasks include a front-end app on a provided API with authentication, pagination and filtering, or a receipt-processing API. Stated estimates are a few hours, but candidates report spending much longer. Some briefs asked for public deployment, a GitHub repo and documentation.
Experiences differ here. Some candidates report no conversation at all before the assignment. One described a recruiter conversation about their background after submitting. Another described a hybrid screen that mixed screening questions with questions about improvements to their app.
Candidates who advanced describe an engineer-led conversation about their experience, the tech stack or their take-home. One was asked to modify the project on the spot, such as adding sign-in error messages or showing query parameters in the URL without a reload.
Candidates in this set report a rejection, commonly a generic email without feedback. Reported waits range from about a week to well over two weeks, and some follow-up emails went unanswered.
