Wingify Interview Experience for Frontend Engineer [Off Campus]
Interview Experience
Getting the InterviewReferral - I approached an employee of Wingify using LinkedIn. He referred me for the position of Frontend Engineer.Interview ProcessRound 1 : Online ...
Full Details
Getting the Interview Referral - I approached an employee of Wingify using LinkedIn. He referred me for the position of Frontend Engineer. Interview Process
Round 1 Online javascript test on Interviewzen platform. In this platform there is no time limit, but the screen will be recorded, so your coding approach and time taken will be shared to the interviewer when you submit the code. There were total 5 questions related to problem solving and DOM querying to be solved using Javascript Question 1: Write an implementation of a function called "getScript" that fetches and executes a JavaScript file in the browser. Question 2 : Write an implementation of a function "value" which returns the value of the inner most function(nested functions was given). Question 3 : Write an implementation of a function called "flatten" that flattens a nested object. The method takes an object and returns a new flattened object. Question 4 : Write an implementation of a function "callAfter" that enables ANY function to be called after some specified duration. The output of the function should remain the same. Question 5 : Write an implementation of a function called generateSelector to generate a CSS selector path of a DOM element.
Round 2 It was a Google Hangout Round. I was asked to explain about one of the projects mentioned in the Resume. Then basic questions related to Web Development like http vs https method, get vs post request was asked. Then one final coding questions related to the event loop was asked. asked to tell about 1 of the project basic questions like http vs https, get vs post then one coding question related to javascript, related to event loop;
Round 3 (final technical round): This was also Google Hangout round. It started with discussion about my projects and other work that I mentioned in my resume. Then 2 Coding questions were asked. Question 1. To find 2 missing number in O(1)
space complexity Question 2. To Find nth node from the tail of the linked list. Then one final theoritical question related to Web Developement was asked and the questions was : Explain difference between document and window .
About This Question
This is a candidate experience report from a wingify interview for a frontend role during the phone screen round reported in 2020.
It covers the following topics: Linked List, Sql, Networking .
Difficulty rating: Easy
Topics
More Wingify Interview Questions
About Wingify Interview Reports
This question was reported by a candidate who interviewed at Wingify. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Wingify are the higher-signal extractions to take from this report.
For broader preparation context, the Wingify interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Wingify reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Wingify Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Wingify reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.