City Storage Systems logo

City Storage Systems Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at City Storage Systems.

Showing 3 of 5
City Storage Systems logo
City Storage Systems

Software Engineer

Engineering · nearly a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Coding

First, there was a 15-minute recruiter screen, which was very direct. Then, a 60-minute live programming session with two engineers, where I was asked a real-world coding question.

Confirmed questions1 question
  • Could you design a menu parser?
City Storage Systems logo
City Storage Systems

Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Coding

The interview process wasn't worth the time; they didn't respect the candidate's time. First, there was a recruiter call, then a take-home assignment given with a week and a half deadline. I spent about 4-6 hours on it, but could have spent more time refining it. It wasn't super difficult, but had enough edge cases that it could get complex, especially if early decisions were poor. I submitted it on a Saturday, followed up a few days later and then again a week later. They said they were waiting for someone to grade it. A week after that, I got a generic rejection email stating they were moving forward with another candidate. I inquired about feedback on the assignment but received no response.

Confirmed questions1 question
  • Build a service
City Storage Systems logo
City Storage Systems

Software Engineer

Engineering

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Coding Behavioral

I applied online and a recruiter reached out. First was a recruiter screen, which was pretty weird and unprofessional. Then there was a tech screen with an engineer. They asked an easy coding question about OOPS class design. I finished coding with no bugs and the engineer seemed happy with my design. Then I was ghosted for two weeks. I scheduled a 30-minute meeting with the recruiter. They told me I didn't get the job, saying the engineer thought I made incorrect decisions during the interview. It was a surprise since I didn't get any indication of that during the interview. I suspect it might be related to my accent. I checked the engineer's LinkedIn, they've job-hopped a lot. I was just practicing for interviews anyway, especially after reading bad reviews about the company online. Who would want to work for that CEO anyway?

Confirmed questions2 questions
  • How would you design a menu parser for a large restaurant group?
  • Design a class for a menu parser.

City Storage Systems Software Engineer Interview Questions

Quoted word for word from City Storage Systems interview reports.

How would you design a menu parser for a large restaurant group?

Read reports

Formats, difficulty and experience

Across all 5 City Storage Systems interview reports.

Interview formats

Behavioral 37.5%
Coding 37.5%
Technical 25%

Interview difficulty

Easy 20%
Average 60%
Difficult 20%

Candidate experience

Positive 20%
Negative 80%