Taro Logo

Senior Software Engineer Interview Experience

January 1, 2024
Negative ExperienceNo Offer

Process

The process for me started with completing a code challenge as part of the application.

After that, I spoke with their internal recruiter.

Then came the first round technical interview, where you have about 40 minutes to build a calendar app from scratch.

It took four days to receive a rejection from the recruiter.

I asked for any specific feedback from the team but was told there was nothing specific.

Questions

Calendar App

Implement a clone of Google Calendar’s day view that allows creating, editing, and deleting events.

Specifications:

  • Show the date for the day at the top, as well as 24 1-hour blocks in one column. Labels for hours should be displayed on the left beside each block.

  • Events are rectangles that span one or multiple blocks.

    • Assume event start/end times are EXACTLY on the hour (e.g., 2pm-5pm, but don’t need to handle 2:03pm-5:07pm).
  • Add a header below today’s date with 3 inputs at the top of the page. The header has 3 inputs (start time, end time, name) and a button to save.

    • The header is always visible.
    • Saving creates the event and clears the input fields.
    • The start time input’s default value is populated by the hour corresponding to which empty cell was clicked on.
  • Clicking an existing event should autofill the header inputs to edit event details (start time, end time, and name only).

    • The start/end/name inputs are default populated by the event’s current details.
    • On save button click, the calendar updates.
    • When editing an existing event, there should be a button to delete the event.
    • Deleting an event clears the input fields.

Notes:

  • Primary goal is functionality, not styling. Don’t worry about copying Google Calendar styles.

  • It may be easier to use numbers instead of Date to represent time.

General:

  • You can use Google to look up documentation, articles, and code examples.

  • You may install and use libraries for data fetching, styling, and state management.

  • TypeScript is not required.

Was this helpful?

Interview Statistics

The following metrics were computed from 15 interview experiences for the Ramp Senior Software Engineer role in United States.

Success Rate

0%
Pass Rate

Ramp's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive7%
Neutral20%
Negative73%

Candidates reported having very negative feelings for Ramp's Senior Software Engineer interview process in United States.

Ramp Work Experiences