{"id":68371,"date":"2023-06-26T15:31:53","date_gmt":"2023-06-26T07:31:53","guid":{"rendered":"https:\/\/version-2.com\/?p=68371"},"modified":"2023-06-26T15:37:33","modified_gmt":"2023-06-26T07:37:33","slug":"meet-nord-people-insights-from-our-engineering-managers","status":"publish","type":"post","link":"https:\/\/version-2.com\/zh\/2023\/06\/meet-nord-people-insights-from-our-engineering-managers\/","title":{"rendered":"Meet Nord People: Insights from our Engineering Managers"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n

As we strive to create a safer cyber future for everyone, our talented engineering team takes center stage. Curious about what it\u2019s like to be at the heart of our operations? We recently caught up with a few engineering leaders at Nord Security: Gerrit Garbereder, Rokas Dambrauskas, and Paulius Kimbartas to discuss their teams, daily tasks, challenges, and skills.<\/p>\n\n

\n
\n

But not everything made it into the video, and we had a few requests for further exploration! So settle back and enjoy, as we delve deeper into the world of Nord Security engineering.<\/p>\n\n

Engineering teams’ role and projects<\/b><\/h2>\n

Hello, Gerrit, Paulius, and Rokas! Thanks for your time today. To start things off, could you tell us how your teams play a role in the success of Nord Security?<\/b><\/p>\n\n

Paulius<\/b>: Hi there. My team at NordVPN<\/a> is developing the Checkout system, polishing purchase flows so that customers can get our products in the easiest and most secure way possible. So simply enabling people to purchase our products in their preferred way helps grow our user base.<\/p>\n

Gerrit<\/b>: We\u2019re building tools to protect NordPass<\/a> customers, even when they\u2019re not actively using the app. Further, as the Premium squad, our team concentrates on monetization of the service. We\u2019re driving this by maximizing customer satisfaction and value for money. Delivering high quality tooling will increase premium subscriptions and reduce the churn rate.<\/p>\n

Rokas<\/b>: Our mission is to continuously enhance the NordLocker<\/a> platform, creating a seamless and efficient experience for everyone who uses it. By doing so, we empower other teams to excel in their work and ultimately drive the success of the entire company.<\/p>\n

Awesome! What are some recent interesting projects you\u2019ve worked on?<\/b><\/p>\n

R<\/b>: A little more than a year ago, NordLocker made the strategic decision to go serverless and focus on building cloud-based solutions<\/a>. In recent months, we finally managed to migrate one of our core functionalities to the cloud, which was a very challenging task!<\/p>\n

P<\/b>: On the NordVPN team, we recently added a one-click payment option to enable our existing users to have a seamless purchase experience in a secure way. This feature required multiple components, such as authentication and secure data retrieval.<\/p>\n

G<\/b>: Adding attachments to NordPass<\/a> was a really challenging project. We had to align the integration with our colleagues at NordLocker while the underlying structure was reworked from the ground up. During this project we created not only new features but also formed new bonds with people across multiple teams.<\/p>\n\n

Work tools and daily operations<\/b><\/h2>\n

And to get these projects over the finish line, which tools do you normally use?<\/b><\/p>\n

R<\/b>: Some tools are used across the whole company. GitLab helps us manage our codebase. For snappy communication, we use Slack. Apart from that, engineers are free to use their IDEs and tools of preference.<\/p>\n

P<\/b>: To expand on that, my team uses Docker, Grafana \u2013 and those are only off the top of my head! In terms of programming languages, primarily we use TypeScript, PHP, and GO.<\/p>\n

G<\/b>: As a cross-functional team we\u2019re using a whole zoo of tools every day. We provide each guild the tooling that fits their needs. Android, iOS and Backend development is enabled through corresponding IDEs.<\/p>\n

What does an engineering manager do on an average day?<\/b><\/p>\n

R<\/b>: My day is quite diverse. I spend most of the time communicating with my team, ensuring their projects are on track and addressing any issues that may arise. I also participate in meetings with other teams and help with long-term planning.<\/p>\n

P<\/b>: In one word: dynamic. My primary focus everyday is to enable engineering teams to achieve their goals, so ad-hoc knowledge sharing, brainstorming, and guiding people takes time every day. On the other hand, focus time is really important for me. Planning upcoming features and aligning our goals across teams is a vital part of my work. It contributes to the team\u2019s overall performance and happiness.<\/p>\n\n

G<\/b>: To add to the above, after the daily scrum in the morning, I typically take care to remove impediments for the team\u2019s current tasks. Once everyone is unblocked I move towards tactical planning together with the Product Owner on upcoming projects and challenges.<\/p>\n

R<\/b>: I always strive to do some hands-on technical work as well, so I can stay connected to my team and the work they’re doing.<\/p>\n\n

Growth opportunities and skills needed<\/b><\/h2>\n

What do you look for in your teammates?<\/b><\/p>\n

P<\/b>: It\u2019s all about having an eagerness to learn \u2013 the cybersecurity field is very dynamic, new risks arise and our engineers need to be constantly learning and up to date with new technologies and best practices.<\/p>\n

R<\/b>: Strong technical skills are important, but we also look for individuals who are excellent problem-solvers, able to work well in a team, and have a growth mindset.<\/p>\n

G<\/b>: Engineering specialists are of course expected to be experts in their field. However, I believe it\u2019s also necessary for this role to be open-minded with customer success as a focus. And I agree with Paulius, my expectation for any engineer is to be curious and eager to learn.<\/p>\n

P<\/b>: One other crucial thing is to be an honest communicator. If something\u2019s wrong, we don\u2019t wait till the situation develops. We speak about it and solve it.<\/p>\n

How does your team grow together?<\/b><\/p>\n

R<\/b>: In my team I encourage open communication and knowledge sharing, which helps everyone on the team to continually refine their skills. Also we do regular performance evaluations, 1-on-1 meetings, as well as offering opportunities to attend relevant training and conferences.<\/p>\n

P<\/b>: Yes, 1-on-1 meetings help us to determine how each engineer wants to grow, because growth is such an individual thing. I always plan the team’s work accordingly, and prioritize initiatives that will help us all grow.<\/p>\n

G<\/b>: We benefit from the training possibilities provided through the Tesonet Group, which focus mainly on soft skills. Hard skills are improved through mentorship programs, online courses, and conferences. I encourage my team to spend around 10% of their time learning, which is scheduled into our sprint planning.<\/p>\n\n

Challenges and how we solve them<\/b><\/h2>\n

It sounds like there\u2019s a lot to consider! What challenges do you face as managers?<\/b><\/p>\n

G<\/b>: Translating the big picture into actionable items that allow individual contributors to relate their work to the company’s success is a challenge. Making everyone aware of the actual problem we are trying to solve is a difficult task. Often enough engineers tend to dive straight into a sophisticated solution while a simpler solution would have solved the customer\u2019s problem with ease.<\/p>\n\n

\n\n\"\"<\/span><\/span>\n\n