Flutter Developer Intern

• How much experience do you have with this technology?
• Are you flexible to work the 6 AM shift?
• Are you available to join immediately?

Design a screen using Flutter with proper state management like Riverpod or Bloc. The screen should have the following features: display a list of users, allow the user to click on a particular user, and redirect to a details screen showing the selected user’s information. The app should fetch data from an API—no static data should be used. The application should follow an architectural pattern, and the code should be modular and readable.

Ninja is now bored with numbers and is now playing with characters but hates when he gets repeated characters. Ninja is provided a string, and he wants to return the first unique character in the string.The string will contain characters only from the English alphabet set, i.e., ('A' - 'Z') and ('a' - 'z'). If there is no non-repeating character, print the first character of the string. If there is no non-repeating character, return the first character of the string.

1. What is the difference between a StatelessWidget and a StatefulWidget? When would you choose one over the other?
2. How do you handle API calls in Flutter? Where should the API logic be written in a properly structured app?
3. What is the purpose of BuildContext in Flutter? Why is it important for navigation and theme access?
4. How would you prevent multiple API calls when a widget rebuilds?
   (Hint: Consider initState, caching, or state management.)
5. What is the difference between FutureBuilder and using Provider for API handling? When would you prefer one over the other?
6. How would you structure a scalable Flutter project?

Problem Statement:
Design a multi-step user registration form in Flutter.

The app should:

• Have multiple screens (Step 1, Step 2, Step 3).
• Allow the user to navigate forward and backward between screens.
• Preserve all previously entered data when navigating between screens.
• Submit the complete form at the end.

Requirements:

Step 1 – Basic Info:

• Name
• Email
• Phone number

Step 2 – Address Info:

• Street
• City
• State
• Zip Code

Step 3 – Additional Info:

• Gender
• Date of Birth
• Accept Terms checkbox

Navigation Rules:

• The user can go forward (Next).
• The user can go backward (Back).
• No data should be lost when navigating.
• Final submission should contain all data from all steps.

Expected Architectural Approach:
You should:

• Use a centralized state management solution (Provider / Riverpod / Bloc).
• Maintain a single form model object, e.g., UserFormModel.
• Store all fields in this model.
• Each screen should read and update the shared state.
• Do NOT store form data inside individual screens only.