What is the Ramp Backend Challenge?
Q1: What exactly is the Ramp Backend Challenge?
The Ramp Backend Challenge is a detailed assessment aimed at gauging a candidate's skills in backend development. This challenge is integrated into the hiring process for backend engineers at Ramp and focuses on real-world problem-solving abilities, along with debugging proficiency.
Q2: What components make up the Ramp Backend Challenge?
Several components characterize this challenge:
1. Starter Code: Candidates receive starter code that contains multiple bugs. The main task is to identify and rectify these bugs without introducing any external dependencies.
2. Independent Bugs: Each bug can be resolved independently, allowing candidates to prioritize based on their preference. However, some bugs may require fixing others first to be testable.
3. Technical Stack: Although the challenge utilizes React and TypeScript, knowledge of TypeScript isn't essential. Candidates can opt to disregard TypeScript files and focus solely on JavaScript.
4. Submission Format: There's a specific format for submission, typically involving a ZIP file containing the modified src folder and an email.txt file with the candidate's email address.
Why Exclude TypeScript Knowledge?
Q3: What's the rationale behind excluding TypeScript knowledge in the challenge?
Excluding TypeScript knowledge from the challenge serves several purposes: - Relevance to Job Role: If TypeScript isn't a core requirement for the position, omitting it ensures candidates are assessed on skills pertinent to their prospective role. - Emphasis on Essential Skills: The focus shifts more towards fundamental backend development capabilities like problem identification, database interaction, and system design comprehension. - Wider Candidate Spectrum: By not including TypeScript, the challenge becomes more approachable for a diverse array of candidates, thereby attracting varied technical backgrounds. - Real-World Application: The task involves resolving issues related to database queries and data retrieval—critical competencies for a backend developer in a financial context.
Core Skills Focus in the Challenge
Q4: Which core skills does this challenge emphasize?
The challenge zeroes in on fundamental backend development proficiencies such as: - Identifying Problems: Recognizing existing bugs within the provided code. - Database Querying: Managing effective database queries to ensure optimal data retrieval. - System Comprehension: Grasping overall system architecture and implementing necessary enhancements. - Debugging Techniques: Employing tools like console logs and DevTools for bug resolution.
Submission Guidelines and Best Practices
Q5: What are the specific submission guidelines for this challenge?
Adhering to submission guidelines is essential for maintaining an orderly evaluation process:
- Folder Structure Compliance: Ensure that both src folder and email.txt are correctly positioned within ramp-fe-challenge-solved directory.
- Complete Folder Compression: Compress entire folder (not just its contents) before submission.
- Original Work Emphasis: Candidates must produce original work; plagiarism will not be tolerated.
Note that these guidelines closely mirror best practices observed in software developer staffing platforms or freelance programming websites.
- Clarity ensures candidates know what's expected of them
- A precise submission format guarantees consistency
An emphasis on original work allows fair assessment
Plus, permitting candidates to work within familiar environments showcases their true capabilities
Example Bug and Debugging Tips
Example Bug Description
Employees Filter Not Available During Loading More Data
Part 1 : Filter Delay
- Reproduction Steps:
- Open DevTools to watch simulated network requests
Refresh page & quickly open Filter by employee dropdown
Expected Behavior : It should stop showing Loading employees.. as soon as employees request succeeds
Actual Behavior : It stops showing Loading employees.. only after paginatedTransactions request succeeds
Part 2 : View More Button Issue
Reproduction Steps:
Click View more button & wait for new data load
Repeat this process multiple times
Expected Behavior : View More button should disappear when there’s no more data to load
Actual Behavior : View More button remains visible & clickable leading page crash
Debugging Tips
To tackle such bugs effectively:
1) Understand all described bugs before starting
2) Reproduce each bug by following provided steps
3) Use development tools (like console logs) effectively
4) Focus on clean solutions (while not required; it’ll make your work stand out)
5) Ensure all fixes are made using vanilla HTML/CSS/JS (per stated requirements)
Summary Succeeding in The Ramp Backend Challenge
The key to succeeding at this backend coding assessment lies in systematic approaches towards debugging & problem solving! By comprehending nature of each bug present; utilizing available development tools efficiently; focusing upon clean solutions—candidates can navigate through successfully!
And don’t forget—following submission guidelines closely will ensure your work gets properly evaluated!
