Senior Flutter Developer (freelance)
- Compensation
- PLN 90–PLN 190 / hr
- Location
- Remote job
- Work setup
- Remote
- Seniority
- Senior
- Employment
- Contract
- Experience
- Not specified
- Category
- Not specified
- Posted
Skills
Must have
- Strong commercial experience with the Flutter SDK (not "I built a side project once")
- Advanced Dart skills, including state management and async patterns
- Working knowledge of iOS and Android: enough to debug when the platform layer is the problem
- Hands-on BLE experience, particularly with flutter_blue_plus or similar
- English at B2+, written and spoken, because our clients are mostly US-based
- Problem-solving over line-counting: we'll take a creative thinker over a fast typist any day
- High coding standards and willingness to align with the team's patterns
- Initiative: you bring new ideas in and you can also walk away from them when the evidence says so
- Engagement and team-play, the kind where people actually want you in the room
Nice to have
- Native iOS (Swift) or Android (Kotlin) experience for the moments when Flutter isn't enough
- Previous IoT or connected device projects
- Method channels and platform-specific plugin work
- Scrum or other Agile delivery experience
- Willingness to share publicly: hackathons, conferences, internal talks
- Genuine curiosity about the devices you build for, not just the code behind them
Full description
In short
If you're a Senior Flutter Developer who knows what flutter_blue_plus does in production, and you've shipped apps that talk to physical devices over BLE, we want to talk. You'd join us on a freelance, time & material basis: you're paid for the hours you actually work on real client projects. The first three months are about figuring out if we're a good match. When things work out, and that depends on the work itself, the project pipeline, and business timing, there's a real path to our core team with a permanent contract and full benefits.
Why intent?
We've been designing and co-creating connected devices since 2008. Wearables, smart audio, health-tech hardware for clients like Oura and BOSE, backed by investors like a16z and Founders Fund. We're 60+ people, fully remote, and AI-native since before LinkedIn influencers discovered the term. Our Flutter work isn't another generic app: it's cross-platform code talking to firmware, sensors, and real hardware behavior on both iOS and Android. If your Dart has ever made a physical device do something it couldn't do before, you already get why we love what we do.
Who this role is NOT for
If you like being told exactly what to build every morning, opening Jira, closing Jira, and logging off at 17:01, we're probably not your people. We look for engineers who ask "why" before "how", challenge assumptions, and occasionally break things because they were trying something new. We're AI-native and we expect you to treat AI as a daily multiplier, not a gimmick. What we expect: ownership of what you touch, straight talk when things get complicated, and the kind of curiosity that makes you actually care about the device on the other end of your Bluetooth connection.
What you'll do
- Build and maintain Flutter apps that communicate with hardware peripherals over BLE
- Make cross-platform code that behaves well on both iOS and Android, not just "compiles on both"
- Take part in specifying, planning, and estimating new modules and features
- Improve reliability by chasing down the issues QA finds, including the weird ones
- Review pull requests and give your teammates feedback that actually helps
- Share what you learn: tech talks, internal docs, pair sessions, whatever fits
- Work side by side with firmware engineers, designers, QA, and PMs
- Use AI tools as part of your daily workflow, not as a party trick
How we work
Fully remote. We have a pet-friendly office in Warsaw and a coworking space in Gdansk if walls and coffee machines motivate you, but nobody will ask why you're not there. Working hours are flexible: most of the team operates between 10:00 and 18:00 CET, and that's when most meetings happen. Evening calls with US-based clients (up to ~20:00) are part of the rhythm, sometimes a couple of times a week, always planned ahead. You'll be part of the Mobile chapter for knowledge-sharing, and at the same time on a project squad led by a PM for day-to-day delivery.