Discover a range of answers from our Insiders, shaped by their roles, journeys and experiences at Nokia.
Anonymous asked a question to Oskar T.
Hello there.
The honest bit first: I am not the right person for a deep Java/Spring/Kafka/AWS briefing. That is not my daily stack, so I will not pretend I can coach you through it. Nokia is a big place and the interview will follow the job you applied for, not a universal “learn these five tools” list.
If the posting is Java/backend, you are already in the right neighbourhood. I would not go hunting extra frameworks for just the sake of it. Know your own work well enough to talk about it simply: what you built, what broke, what you would do differently. Confidence shows and that usually travels better than keyword bingo.
On my side of the product we live more in C++, Linux and large existing codebases. It's less shiny new stack, more “please don’t break the prod(uction)”. For me personally the cloud alphabet soup is a nice backpack, not the cheat code. In my interviews it was example problems and questions: think through a messy one, explain yourself clearly, show you can learn fast.
Whatever the profile is, remember to think out loud — they cannot give points for a brilliant silence.
On AI: skip the benchmark Olympics. More and more teams are using it, some interviews will never mention it and I can only speak for people like me. If the posting asks for it, talk about how it helps you day to day - real talk, a bit of prompt hygiene and the habit of checking what it actually gave you. If it doesn’t, don’t build a shrine to it.
Good luck!
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer's hard drive.
These are cookies that are required for the operation of our website. These essential cookies are always enabled because our website won’t work properly without them. You can switch off these cookies in your browser settings but you may then not be able to access all or parts of our website.
These allow us to recognise and count the number of users and to see how users move around our website when they are using it. This helps us to improve the way our website works.