Hire Flutter developers in Nepal: what to check first

To hire Flutter developers in Nepal well, test the work around the widgets, not the widgets. Check that a candidate writes clean, null-safe Dart, can explain their state management choice, has written native code for iOS and Android, writes tests, has shipped a signed release, and knows how to find a slow frame. Then pay for a short test task and read the code yourself.

A CV that says "Flutter" tells you little. Building a screen that looks right in a demo is the easy part. The skills below are the ones that decide whether the app still works after its third release.

What should a Flutter developer know about Dart?

Flutter is written in Dart, so start there.

Ask about null safety first. Dart has enforced sound null safety since Dart 3, released in May 2023, and types are non-nullable by default. A good candidate can tell you when they reach for ?, when late is justified, and why a codebase full of ! is a warning sign. Each ! is a promise that a value is never null, and the app crashes when the promise is wrong.

Also ask how they handle async code: Future, async/await, streams, and what happens to a pending request when the user leaves the screen. Network errors and slow connections are normal on mobile, and the answer tells you whether they have handled them in a real app.

Which state management approach, and why?

There is no correct answer to "which state management do you use?" and that is the point of asking it. Flutter's own state management options page lists setState, ValueNotifier, InheritedWidget and a long list of community packages, and says the best choice depends on the app's complexity, the team's preferences and the problem at hand.

So ask for the reasoning, not the package name. Useful follow-ups:

• When is setState enough, and when did you move past it?
• Where does business logic live in your last app: in widgets, or somewhere you can test without a UI?
• If you joined a codebase that uses a different package from your favourite, what would you do?

A candidate who says they would rewrite it to their preferred package on day one is telling you something about how they'll treat your codebase.

Can they write native code for iOS and Android?

Sooner or later a business app needs something Flutter does not cover out of the box: a payment SDK, a hardware feature, a vendor library that only ships for Android and iOS. Flutter talks to native code through platform channels, with the native side written in Kotlin or Java on Android and Swift or Objective-C on iOS. The same page points to Pigeon, a package that generates type-safe code for those messages.

You do not need every developer on the team to be strong here. You do need at least one person who has opened the android and ios folders, written a method channel, and fixed a Gradle or CocoaPods build error without deleting the folder and starting over. Ask them to describe the last native issue they solved.

How do they test a Flutter app?

The Flutter testing overview describes three kinds of tests:

Test type	What it checks	Trade-off, per the Flutter docs
Unit	One function, method or class, with dependencies mocked	Quick and cheap to maintain, lowest confidence
Widget	One widget's UI and interaction	Quick, more confidence, more upkeep
Integration	The whole app or a large part, on a real device or emulator	Highest confidence, slowest, most upkeep

The docs say a well-tested app has many unit and widget tests plus enough integration tests to cover the important use cases. Ask a candidate which of the three they have written, for what, and how they mocked the network. "We tested manually" is honest, but it is not the answer you want from the person who will own your app.

Have they shipped a release, not just a build?

Running an app on your own phone is very different from getting a signed build through Google Play and App Store review. Questions that separate the two:

• Signing. Can they explain the difference between the upload key they hold and the app signing key Google holds under Play App Signing? Google's docs say a lost upload key can be reset, so the real question is who holds it and where. That one is an ownership question as much as a skills one, and we cover it in who should own your app store accounts.
• Flavors. Have they set up separate staging and production builds? Flutter's flavors let each build carry its own app name, icon, API endpoint and feature flags, so testers never touch live data.
• Store review. Have they handled a rejection from either store and resubmitted? Ask what the rejection was for.

A developer who has done all three has shipped. One who hasn't may still be a good hire, but plan for someone else to own releases.

Do they know how to find and fix slow screens?

Flutter's Impeller renderer is the default on iOS and on Android API 29 and above, and on iOS it is the only renderer. A faster renderer still can't save a list that rebuilds every row on each scroll, so the question is whether the developer can find problems in their own code.

Ask how they would find a janky screen. The answer you want mentions Flutter DevTools by name: the performance view to see which frames are slow, the CPU profiler to see why, and the memory and network views for leaks and chatty APIs. Test in profile mode on a real mid-range Android phone, not in debug mode on a developer's laptop emulator. A candidate who has done this will describe a specific screen and what was wrong with it.

Do they build for accessibility?

It is cheap to check. Flutter's accessibility guidance asks you to test with TalkBack on Android and VoiceOver on iOS, keep the UI usable at large text sizes, and aim for a contrast ratio of at least 4.5:1. Flutter also has an Accessibility Guideline API for widget tests that checks tap target size, labels on tappable elements and text contrast.

Ask a candidate to open an app they built with the largest system font size turned on, and watch what happens to the layout.

How do you run a paid test task?

Interviews tell you what someone knows. A test task tells you how they work. Keep it short, pay for it, and make it look like your real app rather than a puzzle.

1. Write a small brief. One or two screens that load data from a public API, handle loading, empty and error states, and keep some state between screens.
2. Ask for tests and a README. At least a few unit and widget tests, and instructions to run the project from a fresh clone.
3. Have it delivered as a Git repository. Read the commit history as well as the final code. Small, described commits show how the person works day to day.
4. Run it yourself, on a real Android phone if you can, with slow network and large text turned on.
5. Review it with the candidate. Ask why they chose their state management approach and what they would change with more time. The answers matter more than the code.

If no one on your side reads Dart, ask an independent developer to review the task before you decide. Without that review, the test tells you only that the app ran.

Hiring individual developers is a different decision from hiring an agency. If you are weighing an outside company instead, the questions in choosing a mobile app company in Nepal apply. And if you haven't settled on Flutter yet, read Flutter vs React Native first, because the answer changes who you hire.

Frequently asked questions

What are good Flutter developer interview questions?

Ask about their reasoning, not definitions. Why they chose a state management approach on their last project, how they would add a native SDK, which tests they wrote and why, and how they found the last slow screen they fixed. Anyone can memorise what a StatelessWidget is.

Should a Flutter developer also know Kotlin or Swift?

Not fluently, but they should be able to read and change native code in the android and ios folders. At least one person on a Flutter team needs to be comfortable there, because native integrations and build errors land in those folders.

How long should a paid test task take?

Short enough to fit around a candidate's current job. Agree the scope and the payment in writing before they start, and keep the brief the same for every candidate so the results are comparable.

Can I hire Flutter developers in Nepal from Australia?

Yes, and the checks above are the same. The extra work is in agreeing working hours, code ownership and how releases are approved across the two countries, so put those in writing at the start.

Building with a Flutter team

EK Ra Sunya builds Flutter apps through our mobile development services. Travel Quoter's iOS and Android apps are one example. If you'd rather work with a team than hire one developer at a time, or you want a second opinion on a test task, get in touch.