We are looking for an intern Flutter developer to join the Job Solution team.
We are developing a mobile application in Flutter: feature-first monorepo, separate features, shared UI packages and design system, data layer via clients / repositories, UI state via BLoC approach (controller + immutable state). The project has many custom architectural solutions — this is not a training CRUD and not a "typical" stack from a tutorial.
We value the ability to think, not diplomas or course lists. The ability to figure out why the code is structured a certain way, rather than copying templates. Readiness to learn new things and work where some solutions are custom.
Internship involves real tasks within the product: features, bugs, improvements according to team rules. Mentorship is provided, but independence and the desire to understand are mandatory.
- Develop and refine screens and features under the guidance of a mentor
- Understand the architecture: feature folders, packages, repository layer, state management
- Write code in the team's style: immutable models, clear screen state, no flag spaghetti
- Reuse UI from the design system and shared widgets
- Fix bugs, close edge cases, bring tasks to product quality
- Participate in code reviews: accept feedback and learn to justify decisions
- Clarify requirements before implementation and briefly document non-obvious aspects
- Gradually handle tasks "from setup to PR" — starting with support, then more independently
Mandatory
- Basic Flutter / Dart: widgets, navigation, async / Future / Stream / Listenable, UI state management
- Understanding of OOP and SOLID principles — not memorized definitions, but the ability to explain with examples
- Understanding of feature-first and layers: UI → state/controller → repository → client/API
- Familiarity with the BLoC approach (event/command → state → UI), even if you've written with Cubit/Bloc or similar
- Willingness to read others' code and follow the team's architectural rules
- Ability to find answers independently and ask precise questions
- English at the level of reading documentation
Critical for us
- Non-template thinking: not "as in the guide", but "how to correctly integrate this here"
- Interest in internals: why immutable state, packages, repository
- Willingness to learn the team's custom patterns, not impose your usual stack
Will be a plus
- Freezed / Equatable / build_runner
- REST API, JSON, models
- Git: branches, PRs, clear commits
- DI / composition root
- Design system and reusable widgets
- Basic unit / widget tests
- Personal Flutter project with structure (not one huge main.dart)
Not required
- Commercial experience
- Knowledge of a specific state-management package from our stack
- Perfect UI from day one
