- Fri Dec 05, 2025 11:26 am#10343
Preparing for the Flutter Application Developer Position at Tanvir Construction Ltd.
1. Understand the Role and Company Context
- Study the company’s main business (construction) and its sister concern (TCL Informatix). Knowing that the mobile apps will interact with ERP/HRM systems helps you anticipate domain‑specific requirements.
- The role is full‑time, on‑site at the TCL Head Office, so be ready for regular office hours and occasional collaboration meetings with the Django backend team.
2. Technical Skill Checklist
| Area | What to Review/Practice | How to Demonstrate |
||||
| Flutter & Dart | • Core widgets, layout (Row, Column, Flex, Stack) <br>• Navigation (Navigator 2.0, named routes) <br>• State management options (Provider, Bloc, Riverpod, SetState) <br>• Custom paint & animations | Build a small multi‑screen demo app that uses at least two state‑management techniques and showcases animations. |
| UI/UX | • Responsive design (MediaQuery, LayoutBuilder) <br>• Adaptive widgets for Android & iOS <br>• Consistent theming (ThemeData) | Include screenshots of the demo app on different screen sizes and platforms in your portfolio. |
| API Integration | • REST client (http, dio) <br>• JSON serialization (json_serializable, built_value) <br>• Error handling & retry logic | Connect the demo app to a public API (e.g., JSONPlaceholder) and show loading, success, and error states. |
| Authentication & Security | • Token‑based auth (JWT, OAuth2) <br>• Secure storage (flutter_secure_storage) <br>• HTTPS & certificate pinning basics | Implement a mock login flow that stores a token securely and attaches it to subsequent API calls. |
| Architecture | • Clean Architecture principles <br>• Layered folder structure (presentation, domain, data) <br>• Dependency injection (get_it) | Re‑organize your demo project following clean architecture; mention this organization in your README. |
| Performance | • Profiling with DevTools <br>• Reducing widget rebuilds (const, AutomaticKeepAlive) <br>• Lazy loading & pagination | Record a short video (or screenshots) of DevTools showing frame rendering time before and after optimization. |
| Offline & Caching | • local storage options (shared_preferences, Hive, sqflite) <br>• Data caching strategies | Add a simple offline‑first list that caches API results locally. |
| Testing | • Unit tests (test, mockito) <br>• Widget tests (flutter_test) <br>• Integration tests (integration_test) | Provide a test suite in your repo with at least one test of each type. |
| Version Control | • Git branching (feature, develop, master) <br>• Pull request workflow on GitHub | Keep your demo project in a public GitHub repo with a clear commit history and a PR that merges a new feature. |
| CI/CD | • GitHub Actions basics <br>• Codemagic or similar for Flutter builds | Add a simple GitHub Actions workflow that runs `flutter test` and builds an APK. |
| Firebase (optional but valued) | • Auth, Firestore, Cloud Messaging basics | If you have time, integrate Firebase Auth into your demo for the login flow. |
| Python/Django basics | • Understanding of REST endpoints, authentication mechanisms | Read the Django REST Framework documentation; be ready to discuss how you would consume its APIs from Flutter. |
3. Portfolio & GitHub Preparation
- Create a public GitHub repository for the demo project described above.
- Include a concise README: project purpose, tech stack, architecture diagram, how to run, and screenshots / video demo.
- Highlight any additional side projects that involve Flutter, CI/CD pipelines, or integration with backend services.
4. CV and Application Materials
- Update your CV to list:
• Education (B.Sc. in CSE/Software Engineering/ICT)
• 1–2 years of Flutter experience, naming specific apps or modules you built.
• Explicit mention of state‑management libraries, testing, CI/CD, and any Firebase work.
• Soft skills: teamwork, communication, problem‑solving.
- Add a “Technical Skills” section with bullet points for Flutter, Dart, Git, CI/CD tools, Firebase, Python/Django basics, HTML/CSS.
- Provide a 3–5 line summary of your most recent project, focusing on: problem solved, key Flutter features used, integration with backend, and outcome (e.g., performance gains, user adoption).
5. Interview Preparation
*Technical Questions*
- Be ready to explain the difference between Provider and Bloc, and why you would choose one over the other in a given scenario.
- Prepare to discuss clean architecture: what each layer contains, how dependencies flow, and benefits for large teams.
- Expect coding exercises: building a small UI component, parsing JSON, or writing a unit test on the spot.
*System Design*
- Sketch a high‑level design for a mobile HRM app that syncs employee data with a Django ERP backend. Include authentication flow, offline sync, and push notification handling.
*Behavioral Questions*
- Provide examples of collaborating with backend developers to resolve API mismatches.
- Talk about a time you identified a performance bottleneck and how you resolved it.
- Show how you handled tight deadlines while maintaining code quality and test coverage.
6. Practical Steps Before the Deadline (January 3 2026)
1. Two weeks prior – Finish the demo app, push to GitHub, add CI workflow, and verify it builds on both Android and iOS simulators.
2. One week prior – Polish the README, generate screenshots/video, and ensure the repository is public and accessible.
3. Three days prior – Tailor your CV to the job description, double‑check the tech‑stack list, and write the 3‑5 line project summary.
4. Day before – Review common Flutter interview questions, rehearse explaining your architecture decisions, and prepare a few questions for the interviewers (e.g., “How does the mobile team coordinate with the ERP developers?”).
5. Submission day – Send the application email/portal attachment with CV, cover letter (optional), GitHub/portfolio link, and project summary. Keep a copy of the sent email for reference.
7. Additional Tips
- Practice explaining technical concepts in simple terms; the employer may value clear communication with non‑technical stakeholders.
- Familiarize yourself with the Google Play Console and Apple App Store submission steps, even if you won’t perform the final release yourself.
- Keep an eye on Flutter’s release notes; being aware of recent stable releases demonstrates ongoing learning.
Following this structured preparation plan will showcase both the depth of your Flutter expertise and your readiness to integrate smoothly with Tanvir Construction Ltd.’s ERP/HRM ecosystem. Good luck!
1. Understand the Role and Company Context
- Study the company’s main business (construction) and its sister concern (TCL Informatix). Knowing that the mobile apps will interact with ERP/HRM systems helps you anticipate domain‑specific requirements.
- The role is full‑time, on‑site at the TCL Head Office, so be ready for regular office hours and occasional collaboration meetings with the Django backend team.
2. Technical Skill Checklist
| Area | What to Review/Practice | How to Demonstrate |
||||
| Flutter & Dart | • Core widgets, layout (Row, Column, Flex, Stack) <br>• Navigation (Navigator 2.0, named routes) <br>• State management options (Provider, Bloc, Riverpod, SetState) <br>• Custom paint & animations | Build a small multi‑screen demo app that uses at least two state‑management techniques and showcases animations. |
| UI/UX | • Responsive design (MediaQuery, LayoutBuilder) <br>• Adaptive widgets for Android & iOS <br>• Consistent theming (ThemeData) | Include screenshots of the demo app on different screen sizes and platforms in your portfolio. |
| API Integration | • REST client (http, dio) <br>• JSON serialization (json_serializable, built_value) <br>• Error handling & retry logic | Connect the demo app to a public API (e.g., JSONPlaceholder) and show loading, success, and error states. |
| Authentication & Security | • Token‑based auth (JWT, OAuth2) <br>• Secure storage (flutter_secure_storage) <br>• HTTPS & certificate pinning basics | Implement a mock login flow that stores a token securely and attaches it to subsequent API calls. |
| Architecture | • Clean Architecture principles <br>• Layered folder structure (presentation, domain, data) <br>• Dependency injection (get_it) | Re‑organize your demo project following clean architecture; mention this organization in your README. |
| Performance | • Profiling with DevTools <br>• Reducing widget rebuilds (const, AutomaticKeepAlive) <br>• Lazy loading & pagination | Record a short video (or screenshots) of DevTools showing frame rendering time before and after optimization. |
| Offline & Caching | • local storage options (shared_preferences, Hive, sqflite) <br>• Data caching strategies | Add a simple offline‑first list that caches API results locally. |
| Testing | • Unit tests (test, mockito) <br>• Widget tests (flutter_test) <br>• Integration tests (integration_test) | Provide a test suite in your repo with at least one test of each type. |
| Version Control | • Git branching (feature, develop, master) <br>• Pull request workflow on GitHub | Keep your demo project in a public GitHub repo with a clear commit history and a PR that merges a new feature. |
| CI/CD | • GitHub Actions basics <br>• Codemagic or similar for Flutter builds | Add a simple GitHub Actions workflow that runs `flutter test` and builds an APK. |
| Firebase (optional but valued) | • Auth, Firestore, Cloud Messaging basics | If you have time, integrate Firebase Auth into your demo for the login flow. |
| Python/Django basics | • Understanding of REST endpoints, authentication mechanisms | Read the Django REST Framework documentation; be ready to discuss how you would consume its APIs from Flutter. |
3. Portfolio & GitHub Preparation
- Create a public GitHub repository for the demo project described above.
- Include a concise README: project purpose, tech stack, architecture diagram, how to run, and screenshots / video demo.
- Highlight any additional side projects that involve Flutter, CI/CD pipelines, or integration with backend services.
4. CV and Application Materials
- Update your CV to list:
• Education (B.Sc. in CSE/Software Engineering/ICT)
• 1–2 years of Flutter experience, naming specific apps or modules you built.
• Explicit mention of state‑management libraries, testing, CI/CD, and any Firebase work.
• Soft skills: teamwork, communication, problem‑solving.
- Add a “Technical Skills” section with bullet points for Flutter, Dart, Git, CI/CD tools, Firebase, Python/Django basics, HTML/CSS.
- Provide a 3–5 line summary of your most recent project, focusing on: problem solved, key Flutter features used, integration with backend, and outcome (e.g., performance gains, user adoption).
5. Interview Preparation
*Technical Questions*
- Be ready to explain the difference between Provider and Bloc, and why you would choose one over the other in a given scenario.
- Prepare to discuss clean architecture: what each layer contains, how dependencies flow, and benefits for large teams.
- Expect coding exercises: building a small UI component, parsing JSON, or writing a unit test on the spot.
*System Design*
- Sketch a high‑level design for a mobile HRM app that syncs employee data with a Django ERP backend. Include authentication flow, offline sync, and push notification handling.
*Behavioral Questions*
- Provide examples of collaborating with backend developers to resolve API mismatches.
- Talk about a time you identified a performance bottleneck and how you resolved it.
- Show how you handled tight deadlines while maintaining code quality and test coverage.
6. Practical Steps Before the Deadline (January 3 2026)
1. Two weeks prior – Finish the demo app, push to GitHub, add CI workflow, and verify it builds on both Android and iOS simulators.
2. One week prior – Polish the README, generate screenshots/video, and ensure the repository is public and accessible.
3. Three days prior – Tailor your CV to the job description, double‑check the tech‑stack list, and write the 3‑5 line project summary.
4. Day before – Review common Flutter interview questions, rehearse explaining your architecture decisions, and prepare a few questions for the interviewers (e.g., “How does the mobile team coordinate with the ERP developers?”).
5. Submission day – Send the application email/portal attachment with CV, cover letter (optional), GitHub/portfolio link, and project summary. Keep a copy of the sent email for reference.
7. Additional Tips
- Practice explaining technical concepts in simple terms; the employer may value clear communication with non‑technical stakeholders.
- Familiarize yourself with the Google Play Console and Apple App Store submission steps, even if you won’t perform the final release yourself.
- Keep an eye on Flutter’s release notes; being aware of recent stable releases demonstrates ongoing learning.
Following this structured preparation plan will showcase both the depth of your Flutter expertise and your readiness to integrate smoothly with Tanvir Construction Ltd.’s ERP/HRM ecosystem. Good luck!
