G2I Software Engineer interview experience

The project came with a list of requirements and was estimated to take roughly 4–6 hours.

What stood out was the way they framed how scoring would work. I was warned not to hide behind very abstract frameworks; if the reviewer couldn’t clearly see code implementing each requirement, I’d get penalized even if the underlying framework technically handled it. That made the task feel less like “make it work” and more like “show your work” in a readable, explicit way. Overall, the process felt easy in difficulty, but with a clear expectation that the implementation should be directly inspectable.