I applied through an employee referral. The process took 1 week. I interviewed at Cato Networks (Tel Aviv-Yafo) in Jun 2021
Interview
I got a phone call and I was invited for an interview. The interviewer was a nice person and told me about the technology in the company. Then he asked me to describe something I was working on.
Thank you for sharing your experience interviewing with us. We strive to make the candidate experience as enjoyable as possible and are very glad you had a positive one.
Other Senior Full Stack Developer interview reviews for Cato Networks
I applied online. The process took 3 weeks. I interviewed at Cato Networks (Tel Aviv-Yafo) in Jan 2024
Interview
1. HR screening.
2. Interview with a senior software engineer.
3. Interview with a team lead.
4. Second interview with a team lead at the office.
After the fourth interview I get a reject with a reason that the recruiting team cannot suggest me what I’m searching. Fair but why not to do it a few steps before when I already explained what I’m searching.
Interview questions [2]
Question 1
Implement LRU cache with increasing logical complexity and adding new steps for such cache.
After a quick chat with the recruting HR, I had a technial interview with a group manager and a dev team lead. Interviewers were nice and welcoming, talked about the company, about the group and the team and the role and a bit about what the role would be like. After that they wanted to hear a bit on me.
Interview questions [1]
Question 1
1. Tell about a project that you did and a bit deep dive and things that could have been improved or were problematic and how did you overcome it or how would you approve it. 2. Given the following code: /** * Handles events * Tries to send them 5 times before deleting * For example: * * 12:00 * 12:02 * 12:04 * 12:08 * 12:16 */ public class EventsHandler { /** * Is triggered every minute 12:00, 12:01, 12:02, 12:03... * @param events event to save */ public void handle(List events) { } /** * Tries to save an event in DB * @param event * @return true = event was saved successfully, false = event wasn't saved * */ private boolean saveEvent(Event event) { return DBUtil.saveEventToDB(event); } } Method saveEvent, can sometimes return false for events to failed to be saved in the db. In case an event failed to be saved we need to store it somewhere and manage it, so in the next round (handle method runs every minute), it will run all the events that failed in the previous round. In short implement retries for failed events (including storing them somewhere). You can use whatever you want. Implement the handle method so it can manage and save
