A guide to hiring a Symbian developer
Symbian was an operating system for mobile phones. It ran on many handsets, a large share of them made by Nokia, and it came with its own ways of building apps. It is no longer a platform for new products, but code written for it still exists. Some companies keep a field device, a business app or an old product line alive on it. A Symbian developer is someone who can read that code, keep it working and, when the time comes, help move it to something current. Hiring one is mostly about care and patience, not about new features.
What the work looks like today
Most requests fall into three groups. The first is maintenance: a bug in an app that customers still use, or a build that must be redone because a tool has gone. The second is recovery: finding out what an old app does when the people who wrote it have left. The third is migration: carrying the logic, the data and the screens over to Android or iOS. Often one project holds all three, in that order.
Symbian C++ is its own style
Symbian C++ looks like ordinary C++ but follows its own habits, made for phones with little memory. Strings are handled through descriptors. Long tasks use active objects instead of threads. Memory is protected by a cleanup stack, and errors travel through leaves and traps. A developer who has only written modern C++ will find these rules strange, and mistakes can mean leaks or crashes that are hard to trace. This is why a person with real Symbian time is worth looking for.
Qt, Open C and Java ME
Not every Symbian app is written in Symbian C++. Some use Qt, which gave developers a friendlier toolkit for screens. Some use Open C and Open C++ to bring over standard code. Others are small Java ME programs, called MIDlets, which run in a sandbox with a limited set of features. When you hire, say which of these your app uses, so the search starts with the right skills. A Java background helps with the last group, and our Java developers can help when part of the work sits in that code.
Build files, tools and packages
Old apps are built with old tools. Project files describe what to compile, and a separate file lists the pieces. An installer package then bundles the app for the phone. If the IDE or the SDK is missing, rebuilding can take days before the first line of code changes. A developer with experience will know what to look for, where an older toolchain may still be found and how to record the setup so it is never lost again. Keep copies of every tool in your own storage.
Testing on real phones
Symbian phones differ a lot: screen sizes, memory, keyboards and features. An emulator can show a screen but misses many faults, such as a crash when the phone runs low on memory or a Bluetooth call that fails on one model. Ask a candidate how they test and which devices they have used. If you still hold test handsets, say so, because they are worth more than any list of tools.
Reading code with no notes
The hardest part is often not writing code but understanding it. A strong developer reads a module, follows how data moves, lists the outside calls and writes a short note. That note is valuable even if you never touch Symbian again, because it becomes the specification for a new app. Ask to see a note like this from a past job. Clear writing is as important here as skill with code.
Moving to Android or iOS
A good migration begins with a list of what the app does and who uses each part. Some parts will be dropped, some will be kept as they are and a few will need a redesign. Data is moved next, since contacts, files and records have more value than screens. Then a new app is built, ideally while the old one keeps running. Our Android developers and iOS developers build the new version, and your Symbian hire explains the old rules. If Kotlin is the target language, see our Kotlin developers.
When this hire makes sense
- You have an app or a device that customers still rely on and that runs on Symbian.
- You hold the source code but nobody on staff can read it.
- You need to export data from an old format before a system is turned off.
- You want a clear plan and a safe order of steps for leaving the platform.
If you are starting a brand new app, skip Symbian and go straight to a current platform. A developer who tells you that is being straight with you.
Interview questions worth asking
- What is an active object, and what problem does it solve?
- How does the cleanup stack protect memory when something fails?
- An old project will not build. What do you check first?
- How would you list what an app does when there are no documents?
- Which parts of an old app would you move first to Android or iOS, and why?
A strong answer includes a reason and an example from real work. Someone who recites terms but has never shipped an installer is not ready.
Try a small paid job
Give each finalist the same short task, such as reading one module and writing a one page note on what it does, or rebuilding a small sample project. Pay for the time. Compare the notes, the questions they asked and how clearly they explain what they found.
Setting up for the long run
Agree the working rhythm early: who holds the source, where the tools are kept, how changes are tested and who signs off a release. Store every tool, key and build script in one place you control. A single page that explains how to build and package the app is worth many hours to the next person.
Mistakes to avoid
- Putting a modern app developer on Symbian C++ and expecting a quick fix.
- Rewriting everything at once without writing down what the old app does.
- Letting the only copy of the tools or source sit on one laptop.
- Trusting a resume line when no shipped Symbian app backs it up.
Related help: our app developers in India can build the replacement, and our software engineers suit wider system work around it.















