
Proxify Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 57 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Proxify.
Software Engineer
Right after I applied, I had to take an online technical test. It was supposed to be 3 hours long and done under camera surveillance, no double screens, etc. They wanted it done by the end of the week, which meant I had to cancel my weekend plans. Honestly, asking for a 3h test on such short notice felt like a red flag, but I ignored it and aced the test with a perfect score on all 3 exercises. Then, I had a meeting with HR. Unfortunately, just two days later, they rejected my application without any explanation, even when I politely asked. That was another red flag.
- Would you be open to working part-time?
Senior Software Engineer
The interview process was really good and upfront. Every step was explained clearly, and I liked how professional and open everything was. The interviewers were friendly, and their questions made sense, giving me a good chance to show what I know and have done. I felt pretty good and like they cared during the whole thing, which shows the company tries to be nice and fair to everyone.
- Can you define clean code within the context of React?
- What strategies would you use to reduce latency when fetching temperature data?
- Describe your approach to managing an API request that has a 10-minute execution time.
Software Engineer
I applied for the job and then had a 30-minute call with a recruiter. After that, there was a 3-hour assessment, which felt a bit long. Following the assessment, I had a video interview where the interviewer was mostly quiet. They used Codility for a coding test, giving 80 minutes to solve 3 tasks. One task was multiple-choice React, another was a like/dislike button in React, and the third was a React pagination task. I'm pretty sure I got eliminated because of my score on the last task due to the unit tests and time limit, even though I did the first two perfectly. I don't think testing unit tests within a 30-minute timeframe is a good way to evaluate candidates and doesn't really prove anything. I'd rather have a free coding exercise that allows for better evaluation.
- Create a mini React app for a like/dislike button.
- Build a React component for pagination.
Proxify Software Engineer Interview Questions
Quoted word for word from Proxify interview reports.
“What is the significance of the 'key' prop when rendering lists in React?”
Read reports →“Could you build an image scroller using Intersection Observer, but without using lazy loading?”
Read reports →“What metrics are important when encountering only 4xx and 5xx error codes?”
Read reports →“Given a thermometer on a sky platform with a 5-minute latency for REST API temperature readings (which cannot be altered), what approach would you take to obtain the most accurate daily temperature?”
Read reports →“When is the optimal time to release new versions to production?”
Read report →“Could you explain the distinctions between uncontrolled and controlled inputs in React?”
Read report →“What are the strategies for handling APIs that return long responses?”
Read report →“What strategies would you use to reduce latency when fetching temperature data?”
Read report →“How would you address a situation where a weather app's data loading takes over 5 seconds due to a slow API?”
Read report →Formats, difficulty and experience
Across all 57 Proxify interview reports.