Flutter Engineer

at  Recruitment Room

REQUIREMENTS

Consider the questions:
Do you thrive and have experience in a fast-paced start-up environment?
Are you willing and able to make design decisions based on business need and Expandability?
When should we decide on an object data storage instead of relational?
What is the concept of state management in Flutter? How do popular state management solutions (e.g. Provider, Bloc, Riverpod) compare?
What are Flutter’s build modes (debug, profile, release)? How do they differ and when would you use each?
If you have a solid answer for these—without reference to documentation—then we should chat!

Building our mobile app into a product craftsmen can’t live without
You’ll work with a modern front-end stack (Flutter, BLoC/Provider, REST APIs, Hive) to fully own shipping useful, exciting features out to users on a weekly basis.
You will work on a mix of known features / fixes, prototypes to validate ideas, and exploratory projects in between.
Our team is small, so we expect you to appreciate the user needs underlying everything you work on. You should be comfortable making decisions and trade-offs that help us fulfill users’ needs best.
Keeping our bar for quality high
You’ll balance shipping features in the short term with building extensible and maintainable systems.
You will be responsible for your features in production: they need to be scalable, resilient, and easy to operate.
You’ll be the biggest advocate for keeping our bar high for smooth user workflows and making sure the product looks great and is a delight to use. We want somebody on our team who’ll remain obsessed with a high quality user experience, and can hold us accountable to balancing that with shipping rapidly and pursuing new features.
You’ll contribute and drive to discussions around UX, system design, and architecture.