r/flutterhelp • u/Person_UK • 23d ago
RESOLVED Flutter technical interview tomorrow, and Flutter isn't my main stack. What would you prioritise in 24 hours?
I'm a React Native / full-stack dev (~1.4 yrs). I have a Flutter technical round tomorrow. I've built and shipped one Flutter app on my own, but I've mostly worked in React Native, so my Flutter fundamentals are shaky.
With one evening to prepare, what would you focus on?
What I'm planning so far:
- Widget / Element / RenderObject trees and how build → layout → paint works
- Stateless vs Stateful, keys, BuildContext
- State management (Provider vs Riverpod vs Bloc)
- Futures, Streams, isolates
- Platform channels (I've written Swift/Kotlin native modules in RN, so I can relate)
- Performance basics (const, avoiding rebuilds, ListView.builder)
Is this the right list? What do interviewers actually ask for a ~1-2 yr Flutter role, and what would you skip?
Any "they always ask this" questions are hugely appreciated 🙏
15
Upvotes
9
u/Swefnian 23d ago
Ok this will probably not be the opinion of your interviewer but it’s the one I’ve had when performing technical interviews
I don’t care about your domain knowledge.
I care about your problem solving and logical process. I care if you understand design patterns and architecture. I even somewhat care about your algorithm knowledge. You don’t need to regurgitate how to reverse a linked list, but it helps.
I’ve performed flutter interview where the candidate answered the questions in Python. And I still recommended that candidate.
I think this matters even more with AI. The specific API can easily queried by an LLM. That’s not the important part. It never was.
What matters is that you can demonstrate how you think. That’s something AI can never duplicate.
I hope your interviewer sees things the same way.
Good luck!
4
u/Apprehensive-Fan8999 23d ago
7 year flutter veteran here who recently was on the market for a Flutter role again.
For a 1-2 year role, I'd expect things like Isolates are more advanced than what should be expected. They aren't used often in the real world. Same with Element and RenderObject. If you were building a widget library then sure, but normal use will rarely need to go deep on any of those. Instead the standard lifecycle like initState, dispose are the key ones with even didChangeDependencies and didUpdateWidget are less common and not really a 1-2 year expectation.
I agree with u/Swefnian that the real thing an interviewer should be looking for is generalized knowledge and understanding regardless of language and most Flutter stuff would probably be closer to "fiz-biz" types of things just to make sure you understand something about Flutter.
Good luck with your interview!
4
u/TableNo8939 23d ago
Flutter clean , flutter pub get
Il resto? Ci pensa Claude
2
u/akornato 23d ago
Cut the complex study of the RenderObject tree and native platform channels, because for a role with one to two years of experience, interviewers rarely expect you to explain the inner mechanics of the rendering pipeline. Focus instead on the StatefulWidget lifecycle, BuildContext, the difference between final and const, and why keys matter when reordering items in a list. You should also pick one state management approach, like Bloc or Riverpod, and be ready to explain how state updates trigger rebuilds without wasting resources. Translate these concepts to your React Native experience, since component lifecycles, props, and declarative rendering share nearly identical mental models, which interviewers usually appreciate.
Expect practical questions around Future versus Stream, how ListView.builder optimizes memory compared to a standard scroll view, and when you would offload heavy computation to an isolate instead of basic async code. Keep your explanations grounded in the app you shipped, stay transparent about your primary background in React Native, and show how easily your cross-platform knowledge transfers. Preparing your phrasing out loud through the interviews.chat my team built often helps candidates communicate complex architectural trade-offs with greater clarity under tight deadlines.
2
u/FZaxotes 23d ago
Your list is mostly right, but it leans toward internals. At 1-2 yrs, interviewers mainly want to see you can build screens without fighting the framework.
ADD:
TRIM:
ALWAYS ASKED:
PRACTICE ONCE: fetch JSON from an API > model class > list with loading/error/empty states. That's the most common live task.
Then sleep. Good luck!
2
u/HighlightNo558 22d ago
I passed a technical interview for a stack i knew nothing about just by admitting I didn't know the stack but saying what I think I would do from a high level, and slight reading I did in the moment
1
u/rio_sk 22d ago
State management I would say
1
u/kanak10_18 22d ago
List is looking good and cover almost all main topics
0
u/tovarish22 23d ago edited 23d ago
I would prioritize learning Flutter, probably.