Girmiti Software

I recently had the opportunity to interview with Girmiti Software for an Android Developer position (3–4 years of experience). Overall, the process was technically focused and covered a wide range of Android concepts.

Round 1: Technical Interview (30–40 minutes)

The interviewer started by introducing himself and then asked me to introduce myself. The discussion mainly focused on Android fundamentals and practical development experience. Some of the topics covered were:

• MVVM architecture and its implementation
• Android architecture and framework layers
• Application launch flow
• ViewModel and its lifecycle
• Services and adding headers to network requests
• State hoisting in Jetpack Compose
• Dagger/Hilt and Dependency Injection
• Room migrations and their importance
• Coroutine scopes and switching between scopes
• Different ways to update the UI
• Alternatives to ViewModel for handling data during process death

The interviewer was professional, and the discussion was engaging. About 30 minutes after the interview, HR informed me that I had cleared the first round.

Round 2: CEO Discussion

My second-round interview was initially scheduled for one day but had to be rescheduled because the CEO was occupied in another meeting. The next day, the discussion began with a brief introduction and quickly moved toward my experience with POS SDKs.

Since I mentioned having hands-on experience with POS SDKs, the interviewer asked in-depth questions about NFC APIs, payment gateways, POS SDK methods, NFC enablement, and communication protocols. These questions went deeper than the level of experience I had with POS integrations, and I wasn’t able to answer several of them confidently. The pace of the interview was quite fast, which made it challenging to think through the answers.

Unfortunately, I wasn’t selected after the second round. Looking back, I realized I should have been more transparent about the depth of my POS SDK experience instead of simply saying I had hands-on experience. Overall, it was a good learning experience that highlighted the importance of understanding every technology listed on your resume in depth. The interview covered practical Android concepts along with domain-specific knowledge, making it a valuable experience for anyone preparing for similar roles.

The first technical round was well-structured, and the interviewer was professional and respectful.

However, my experience in the second round with the CEO was quite different. The interview felt more like a rapid-fire Q&A than a technical discussion. Questions were asked one after another with very little time to think or explain my approach. The interaction came across as rushed, making it difficult to have a meaningful technical conversation.

While I respect that every interviewer has their own style, I personally didn’t find this interview format to be a positive candidate experience. Constructive discussions often reveal a candidate’s abilities better than testing how quickly they can respond under pressure.