Interview questions: Flutter

Q1. Widget, Element and RenderObject?

Model answer: "Widgets are immutable descriptions of UI, cheap to create. Elements are the long-lived instances in the element tree that hold a widget's place and, for stateful widgets, its State. RenderObjects do layout and painting. When I rebuild, Flutter compares new widgets with the elements and updates only what changed, which is why rebuilding is cheap."

Q2. StatelessWidget versus StatefulWidget, and the lifecycle?

Model answer: "A StatelessWidget depends only on its constructor arguments. A StatefulWidget has a State object that survives rebuilds: initState runs once for setup, build runs on every rebuild, didUpdateWidget when the parent passes new arguments, and dispose for cleanup. I call setState to rebuild after changing state and check mounted after awaits."

Q3. What is BuildContext?

Model answer: "It is a handle to a widget's location in the element tree. I use it to look up inherited data such as Theme.of(context), MediaQuery and providers, and for navigation. A context from below a provider can find it; one from above cannot, which explains ProviderNotFound errors."

Q4. When do you need keys?

Model answer: "Keys preserve identity when widgets of the same type move, are inserted or removed in a list, so state stays with the right item. I use ValueKey with an id for list items and Dismissible; GlobalKey only when I must reach a widget's state, like a FormState."

Q5. Hot reload versus hot restart?

Model answer: "Hot reload injects changed code and re-runs build methods while keeping state. Hot restart restarts the Dart code and resets state. Changes to main, initState of existing widgets, global initialisers, native code or packages need a restart or full rebuild."

Q6. Explain Flutter's layout model.

Model answer: "Constraints go down, sizes go up, the parent sets the position. Each widget receives min and max constraints and chooses a size within them. Overflow errors come from children wanting more than they are allowed, fixed with Expanded or Flexible, wrapping, scrolling or responsive layouts; a ListView inside a Column needs Expanded because the Column gives unbounded height."

Q7. How do you choose state management?

Model answer: "setState for ephemeral state. For shared state, Provider for simpler apps, Riverpod for compile-safe, testable providers, and Bloc for large teams wanting strict event-to-state structure. The key is consistency and keeping business logic out of widgets so it can be unit tested."

Q8. How do you make a Flutter app fast?

Model answer: "Measure in profile mode with DevTools first. Then use const widgets, keep build methods light, split widgets to reduce rebuild scope, use ListView.builder, cache and resize images, and move heavy work to isolates. Test on a budget Android phone."

Take-home assignments

• Typical brief: fetch a list from an API, show details, maybe search or favourites, in 2 to 4 days.
• Reviewers look for: clean folders and layering (UI, state, data), loading/error/empty states, responsive layout, sensible state management, some unit and widget tests, and a clear README.
• Test on a small phone and in landscape; handle no internet.
• Keep it simple and finished rather than ambitious and broken; list improvements you would make with more time.

Common interview mistakes

• Saying "setState rebuilds the whole app".
• Not knowing why a ListView in a Column crashes.
• Over-engineering a take-home with five layers and no tests.
• Not asking clarifying questions about requirements.