Hello Oskar, I applied for the Junior SW Dev role. What core tools and skills should an entry-level engineer focus on to succeed in Nokia’s development environment? Thanks!
Rayan B. asked a question to Oskar T.
I came across your profile through Nokia's employee chat after applying for the Junior SW Development Engineer role. I noticed your advice about being curious and learning on the job. Could you share what tools or daily workflows are most central to your development team, and what advice you'd give to someone aiming to succeed in an entry-level software role at Nokia?
- 1 reply
- 1 views
- Category: Role, Role description
- Date asked:
- Last update:
-
Hi, thanks for writing and good luck with your application. Curiosity is a good starting point and the tools are much less mysterious than they look from the outside.
For the tools, Moba shows up mainly during onboarding, when you set up access to the remote servers. After that, VS Code is still around, but Cursor is the party member you actually travel with these days. It will happily offer to finish the quest. Useful, fast, but you still want to read the loot before you equip it. Git is constant. Vim shows up for commit messages and the odd edit on a Linux server. Some people escape to Nano and nobody calls security. If Vim ever traps you, ":q" to flee. On Gerrit and Jenkins the loop is simple: edit, local tests green, push, check CI, get roasted in review, fix, and rinse and repeat until it merges. There are also internal tools for investigations, build tracking and the rest - the map fills in as you walk.
Paperwork lives in Confluence and Jira, chat in Microsoft Teams, and - heavy rain, thunderstrike in the distance - Outlook, where a few hundred mails can arrive and stare at you convinced they are urgent. A smart buddy will help you set up rules so the important ones don’t drown in the flood.
For the skills, I would not collect every framework in advance. Comfort with Git, a Linux terminal and reading code you did not write will carry you further. Every day we stray further from... pure coding skills, so a bit of system design is a good call: how the pieces talk, what breaks and why. Ask the early question, think out loud when you are stuck. Nobody expects you to know the whole codebase on Monday. They will notice if you are willing to learn it.
