🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
In short We're looking for a Mobile Developer with serious BLE experience. Flutter, native iOS (Swift), native Android (Kotlin), or some combination, we're open as long as you know how to make apps talk to devices. You'd join us on a freelance, time & material basis : you're paid for the hours you actually work on real client projects. Next project in this area kicks off in January or February, so we're starting now to bring the right person on board in time. 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. Most of our projects are long-term partnerships, so we care about building solid relationships, with clients and inside the team. If you enjoy debugging edge cases in device communication and working with firmware and backend engineers on real products that ship, you'll feel at home. 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 dig into the weird BLE bug nobody else wants to touch. We're AI-native and we expect you to treat AI as a daily multiplier, not a gimmick. What we expect: ownership of the mobile side of the project, straight talk with clients (you won't be hidden behind layers of management), 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 Own the mobile side of a connected-product project: wearables, smart sensors, health-tech devices Design and implement BLE communication flows that hold up in the real world Debug real-world device interactions, including the ones that only happen on one phone in one room Work side by side with firmware engineers, backend, designers, QA, and PMs Contribute to architecture and technical decisions, not just execute someone else's Communicate directly with the client: you won't be hidden behind layers of management 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 cross-functional project squad led by a PM for day-to-day delivery. What you'll get 90-180 PLN/h net B2B, depending on your experience Truly flexible hours: you organize your day Fully remote, with pet-friendly Warsaw office + Gdansk cowork if you want them Access to our internal knowledge-sharing: tech talks, experiments, side projects When the first 3 months work out, and that depends on the work, the project pipeline, and business timing, there's a real path to a permanent contract with a fixed monthly salary, 26 days paid leave, 10 sick days, Saltus medical care, and a training budget No sugarcoating: during the freelance period there's no paid leave or medical benefits. Those come with the permanent contract, and we're transparent about that upfront. Your first weeks We aim to give you space to ramp up before jumping into live project work, but this is a real company with real deadlines: if the project needs you sooner, we'll make sure you have the support to hit the ground running. You'll get paired with a technical buddy and tackle progressively bigger tasks, so we can both see how the collaboration feels. Feedback comes early and often, no one waits three months to tell you something isn't working. If it's great, you'll know. If something needs adjusting, you'll hear about it while there's still time to adjust. Recruitment process Fast and to the point. The entire process is in English. All interviews are recorded for internal evaluation purposes. Application with a few screening questions HR call, ~45 min, just to align on expectations Technical meeting, ~90 min, with the technical team (discussion + practical live task) Final decision within a few days Once we're in touch, you'll hear from us fast. We don't ghost and we don't drag. One more thing intent is an equal opportunity employer. We care about what you can do, not where you come from. Send us your CV and a few words about why this caught your eye. Bonus points if you share something you've built that made you proud, ideally something where BLE was involved.
Here's where they are and how to stand out in your next interview.
24.795Jobs
9.577IN
74%EN
That number includes positions in India (9,577), Poland (3,429), the United States (1,753), Singapore (787), and Brazil (779). If you're looking to move or work remotely, check which countries match your goals — then filter WorkMundi by location to see what's actually hiring near you.
Most developer ads you'll see are written in English: 18,397 of the 24,795. That doesn't tell you whether the job itself requires you to speak English or work in English daily, so read each posting carefully. Don't assume the language of the ad matches the language of the team.
The employers posting the most developer roles are Link Group (369 jobs), Upvanta (257), jobgether (226), and OfferZen (212). If you're applying to any of these, research their hiring patterns. They move fast and post often, which means they're either scaling hard or replacing people who didn't fit.
In your interview, expect this: 'Walk me through the last time you had to debug something that took you more than an hour. What was it, what did you try first, and what would you do differently?' Hiring managers ask this to see if you think systematically or just try random fixes. Have a real example ready with specifics.