
G2i Frontend 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
Candidate interview experiences
First-hand accounts from people who interviewed at G2i.
Frontend Developer
The interview was pretty straightforward. It involved 12 live coding questions, split evenly between Typescript and React.js. My interviewer was a really nice guy, and I actually enjoyed the experience. We discussed topics like re-rendering and the inner workings of JavaScript.
- How do you prevent re-rendering?
- Can you explain how JavaScript works?
- We went through 12 live coding questions, covering both Typescript and React.js.
Frontend Developer
It was basically just a RLHF review test, you get 11 minutes total to review some code, leave your comments, and then upload a video of yourself explaining your review.
- Could you review this code and provide an RLHF review?
Front End Developer
Applied through StackOverflow and was later contacted via email about a technical test and an initial interview with HR/recruiter. This person gave a company intro and clarified doubts about the code test, which had unclear instructions and UI details. It also included many links to company coding standards, a Javascript book, React docs, and Node.js info (though Node wasn't relevant to the test). I asked the interviewer for clarification on expectations, and they said I had 'freedom to do the test the way you want'. We ended the call confirming a second interview with a technical person to discuss the test, which I found odd since the code hadn't been reviewed yet. The test involved building a simple questionnaire app where users select answers, proceed, and see a final score. My solution was accurate, well-structured, met UI requirements, and avoided overkill logic, extra dependencies (except react-router), bad practices, or warnings. After submitting, the second interview, scheduled a few days later, was canceled without explanation. I had to email twice for reasons, and eventually received a rejection stating the application was denied because I didn't include eslint, prettier, tests, state management, or typechecking. These reasons were unexpected and unfair, as they weren't specified in the instructions. While I use these tools professionally, they're usually not required in tests unless stated, as tests should focus on logic and skills, not production readiness. State management wasn't necessary, and assuming candidates will follow unspecified 'standards' or opinions is unreasonable. I believe the reviewer focused on personal preferences rather than company needs, potentially dismissing good candidates due to an egocentric approach, possibly indicating the company seeks specific personalities over genuine talent.
- Can you talk about your experience?
G2i Frontend Engineer Interview Questions
Quoted word for word from G2i interview reports.
“What are the specifics of setTimeout()'s default 4ms throttle and its execution timing relative to Promises, even with a 0ms delay?”
Read reports →“How do you prevent re-rendering?”
Read reports →“Can you determine the output of this code snippet: console.log(1) console.log(setTimeout(() => { return 2; }, 0)); console.log(Promise.resolve(3)); console.log(4);?”
Read reports →“Given two RLHF code examples, explain what they do and how they function.”
Read reports →“Can you explain how JavaScript works?”
Read report →“Could you review this code and provide an RLHF review?”
Read report →“Can you talk about your experience?”
Read report →Formats, difficulty and experience
Across all 5 G2i interview reports.