Interview questions
Flutter Interview Questions
17 Flutter interview questions on widgets, state, BuildContext, keys, hot reload and platform channels, with model-answer guidance for both sides.

What's here
17 Flutter interview questions, grouped into 4 areas: widgets and the widget tree, state management and data flow, performance and development workflow and platform integration, testing and architecture. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.
- Ask the candidate to explain a small widget tree and predict what rebuilds when state changes
- Probe state management answers with 'why that approach for this app?' rather than accepting a package name
- Include a keys question with a reorderable list example; it quickly separates experienced developers
Cohesyve finds, contacts and tests Flutter candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.
Preparing for this interview yourself? Practise it free →Flutter is Google's UI toolkit for building apps for mobile, web and desktop from one Dart codebase. These Flutter interview questions cover the widget model, state management, the widget tree and BuildContext, performance, platform integration and testing. Each question includes what a strong answer contains, so interviewers can assess Flutter developers consistently and candidates can check the depth of their understanding before the interview.
Widgets and the Widget Tree
Everything in a Flutter UI is a widget. These questions test whether the candidate understands what that means.
- 1
What does it mean that in Flutter 'everything is a widget'?
Why ask it
The core idea of the framework.What to look for
The UI is built from widgets that describe what their view should look like given their configuration and state. When state changes, the framework rebuilds the description and works out the minimal changes to the underlying render tree. Strong answers mention that widgets are lightweight, short-lived descriptions. - 2
What is the difference between a StatelessWidget and a StatefulWidget?
Why ask it
A basic question that reveals depth through follow-ups.What to look for
A stateless widget takes its configuration from its parent in final fields. A stateful widget creates a State object that persists between builds and holds mutable state. Good answers explain that the widget object itself is still recreated; the State is what lasts. - 3
What does setState do, and what happens if you change state without calling it?
Why ask it
Common source of bugs for newer developers.What to look for
setState tells the framework the State has changed so it reruns build. If a field changes without setState, build is not called and the UI does not update. Strong answers mention keeping setState calls small and not doing slow work inside them. - 4
What is BuildContext?
Why ask it
Misunderstanding BuildContext causes errors with themes, navigation and providers.What to look for
It represents the widget's location in the tree. Lookups such as Theme.of(context) use it to find the nearest relevant ancestor, which is why different parts of the tree can have different themes. Candidates should know the common error of using a context from above the widget they are trying to find. - 5
When do you need keys, and what problem do they solve?
Why ask it
Keys are a frequent source of subtle list bugs.What to look for
Keys control which widgets the framework matches up on rebuild. They matter for lists of same-type stateful widgets that get reordered, inserted or removed, so state stays attached to the right item. Global keys must be unique across the whole tree and can be used to reach a widget's state, but should be used sparingly.
Before the Flutter interviews, see who can do the work
Cohesyve finds and contacts Flutter candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.
State Management and Data Flow
How the candidate structures state as an app grows.
- 6
How does data flow through a Flutter widget tree?
Why ask it
Tests the mental model behind every state management approach.What to look for
State flows down to child widgets through constructor parameters; change notifications flow up through callbacks. Strong answers explain lifting state up to the nearest common ancestor and when that stops scaling. - 7
What options does Flutter offer for sharing state across many widgets?
Why ask it
Shows breadth and judgement.What to look for
Built-in tools such as InheritedWidget or InheritedModel, and ValueNotifier with listeners, plus community packages. package:provider builds on InheritedWidget; candidates may also name Riverpod or BLoC. The best answers explain how they choose based on app size, team familiarity and testability, rather than claiming one is always right. - 8
What is the difference between ephemeral state and app state?
Why ask it
Helps decide where state should live.What to look for
Ephemeral state belongs to one widget (a selected tab, an animation progress) and suits setState. App state is shared across screens or sessions (logged-in user, cart, preferences) and needs a shared approach. Candidates should avoid putting everything in global state. - 9
How do you handle asynchronous data such as a network request in the UI?
Why ask it
Almost every app loads remote data.What to look for
Futures and async/await, Streams for continuous data, FutureBuilder or StreamBuilder or state-management equivalents, and handling loading, error and empty states. Strong answers mention not creating the Future inside build, which would restart the request on every rebuild.
Performance and Development Workflow
How the candidate keeps apps smooth and works efficiently.
- 10
What is the difference between hot reload and hot restart?
Why ask it
Everyday tooling that candidates should understand properly.What to look for
Hot reload injects updated code and rebuilds the widget tree while keeping app state; it does not rerun main() or initState(). Hot restart reloads the code and restarts the app, losing state. Native code changes need a full restart. Both only work in debug mode. - 11
Why might a change not appear after a hot reload?
Why ask it
Tests deeper tooling knowledge.What to look for
Changes to main(), initState(), global variable or static field initialisers, enum-to-class changes, generic type declarations or native code are not picked up by hot reload. The fix is a hot restart or full restart. - 12
A scrolling list in your app is janky. How do you investigate and fix it?
Why ask it
Performance work is a common senior-level task.What to look for
Profiling in profile mode with DevTools, then fixes such as building list items lazily with a builder constructor, using const widgets where possible, avoiding expensive work in build, caching or resizing images, and limiting rebuilds to the widgets that actually change. - 13
Why do const constructors matter in Flutter?
Why ask it
A simple optimisation with a clear explanation.What to look for
Const widgets are created once at compile time and can be reused across rebuilds, which reduces work for the framework. Candidates should know when a widget can be const and use lint rules to enforce it.
Platform Integration, Testing and Architecture
How the candidate handles native features, quality and app structure.
- 14
How do you call platform-specific code, such as a native SDK, from Flutter?
Why ask it
Many real apps need native features.What to look for
Platform channels: a MethodChannel with a unique name, invoked from Dart and handled in Kotlin or Java on Android and Swift or Objective-C on iOS. Messages are asynchronous. Strong answers mention that MethodChannel is not type-safe and that Pigeon can generate type-safe code for both sides, or that an existing plugin may already exist. - 15
What kinds of tests do you write for a Flutter app?
Why ask it
Testing discipline separates maintainable apps from fragile ones.What to look for
Unit tests for logic, widget tests that pump widgets and check what renders and how they respond to taps, and integration tests that run the app on a device or emulator. They should explain how state management choices make testing easier or harder. - 16
How do you structure a medium-sized Flutter codebase?
Why ask it
Architecture affects how fast a team can work.What to look for
Separation between UI, state or view-model logic, and data or repository layers; feature-based folders; dependency injection for testability; and consistent conventions across the team. - 17
How do you handle navigation and deep links?
Why ask it
Navigation complexity grows fast in real apps.What to look for
Understanding of the Navigator, named or declarative routing (often with a routing package), passing arguments safely, and handling deep links into specific screens. Awareness of back-button behaviour on Android.
Running the interview well
- 1Ask the candidate to explain a small widget tree and predict what rebuilds when state changes
- 2Probe state management answers with 'why that approach for this app?' rather than accepting a package name
- 3Include a keys question with a reorderable list example; it quickly separates experienced developers
- 4Ask about a performance problem they fixed and how they measured it
- 5If the role needs native work, ask about platform channels and a real integration they built
- 6Score clear reasoning about trade-offs above familiarity with one particular package
Common questions
What Flutter topics come up most in interviews?
Widgets and the widget tree, StatelessWidget versus StatefulWidget, setState and lifecycle, BuildContext, keys, state management approaches, async data with Futures and Streams, performance, hot reload versus hot restart, platform channels and testing.
Do Flutter interviews include Dart questions?
Usually. Expect questions on Dart basics such as null safety, async and await, Futures and Streams, classes and mixins, and collections, because all Flutter code is written in Dart.
Which state management approach should I learn for interviews?
Understand the built-in tools first: setState, InheritedWidget and ValueNotifier. Then learn one widely used package well and be able to explain why you would choose it. Interviewers care more about your reasoning than the package you pick.
How should I prepare for a Flutter developer interview?
Build or revisit an app that loads remote data, manages shared state and has tests. Be ready to explain its structure, a performance issue you fixed and how you would add a native feature. Review the widget lifecycle and keys.
What is the difference between hot reload and hot restart in Flutter?
Hot reload updates the code and rebuilds the widget tree while keeping the app's state. Hot restart reloads the code and restarts the app, so state is lost. Changes to native code need a full restart.
Save these questions for the Flutter candidates who can do the work
Cohesyve takes your Flutter job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.
1,500+
assessments completed
50%
faster time-to-hire
5 min
from JD to assessment
14-day free trial · 10 candidates · Not charged until the trial ends
Preparing for a Flutter interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.
From the blog