Snapmint

I interviewed with Snapmint for an SDE-1 Android role. The process consisted of two virtual rounds followed by a final onsite round in Gurugram.

Round 1: DSA

The round included three easy-to-medium coding problems based on two-pointer techniques and hash maps. The interviewer was friendly, and the discussion ended on a positive note.

Round 2: Android

The discussion covered:

• Kotlin coroutines and structured concurrency in depth
• Output-based multithreading and coroutine questions, with an emphasis on explaining the execution order and reasoning behind each answer
• Kotlin and Jetpack Compose fundamentals
• Previous projects and the technical decisions made while building them

Round 3: Hiring Manager (Onsite)

The final round included:

• Reasons for considering a job change
• High-level and low-level design for an e-commerce application, including product-listing APIs
• A problem-solving question involving a circle divided into nine equal sectors: how to calculate a rotation that stops the indicator exactly on the fourth sector, and how to retain the selected sector when an Activity is recreated after a configuration change
• Fragment lifecycle transitions across different navigation scenarios
• A detailed discussion of previous work and experience

The state-restoration question was specifically about surviving configuration changes. That means transient UI state, such as state owned by a ViewModel, SavedStateHandle, or Compose’s rememberSaveable, rather than a guarantee of durable storage after the app’s data is cleared.

Outcome

The interviews were engaging, and I felt they went well. However, I did not receive a final decision or clear feedback from the hiring team. Fortunately, I already had another offer, so the lack of communication did not affect my decision.

Candidates invest significant time in interview preparation. Even a brief update or closure helps create a more positive candidate experience, and clear communication should be valued by both sides.

I wish the team at Snapmint all the best.

Shared by Utkarsh Saxena on GitHub. View his LinkedIn profile.