Round 1: Technical Coding (DSA-focused)
The interviewer asked me a coding problem commonly known as the "Two Sum" problem.
I was given:

An array of integers

A target value

Problem:

"Return the indices or values of two numbers from the array that add up to the target."

I discussed both brute-force and optimized approaches:

Brute-force: Nested loops with O(n²) time

Optimized: Using a HashMap for O(n) time
I wrote clean, working code and explained edge cases as well.

Round 2: Product-Based Case Study
The second part involved a real-world app case study.
I was presented with a problem scenario and asked:

"How would you design a feature in a utility-based mobile application?"

They were looking for:

My thought process

Feature planning

UI considerations

State management

Offline sync / caching

API integration strategy

I walked them through:

Choosing the right architecture (MVVM)

Using Flutter widgets efficiently

Preferred state management (Provider or Riverpod)

Handling API data and exceptions

Ensuring user-friendly error messages and retry logic

Overall Feedback:
They were evaluating:

Problem-solving skills

Code optimization

App architecture understanding

Real-world product thinking
The discussion was collaborative and practical, aligned with their domain of utility and field workforce applications.

Question

Round 1: Technical Coding (DSA-focused)
The interviewer asked me a coding problem commonly known as the "Two Sum" problem.
I was given:

An array of integers

A target value

Problem:

"Return the indices or values of two numbers from the array that add up to the target."

I discussed both brute-force and optimized approaches:

Brute-force: Nested loops with O(n²) time

Optimized: Using a HashMap for O(n) time
I wrote clean, working code and explained edge cases as well.

Round 2: Product-Based Case Study
The second part involved a real-world app case study.
I was presented with a problem scenario and asked:

"How would you design a feature in a utility-based mobile application?"

They were looking for:

My thought process

Feature planning

UI considerations

State management

Offline sync / caching

API integration strategy

I walked them through:

Choosing the right architecture (MVVM)

Using Flutter widgets efficiently

Preferred state management (Provider or Riverpod)

Handling API data and exceptions

Ensuring user-friendly error messages and retry logic

Overall Feedback:
They were evaluating:

Problem-solving skills

Code optimization

App architecture understanding

Real-world product thinking
The discussion was collaborative and practical, aligned with their domain of utility and field workforce applications.

Bynry