Peers: Why are you excited about your job?
Paul: I always worked in the companies where I believed in the product. The solution I am working on should be helpful for the users and it should make their life easier. That is what all my jobs have in common – the products I have worked on were related with training and self-development. The value of the product keeps me passionate.
Peers: What skills are needed for the tech team?
Paul: It mostly depends on the company. For working at Peers in the tech team you should be able to see the whole product and understand it end-to-end. If there is something important coming up, you should be able to jump in. Each team member should be able to contribute to every part of the project – it is called T-shaped skills. Whereas in big teams you can be professional in a single domain and the team skilled people in other domains too.
Peers: If you could snap your fingers and become an expert in something, what would it be?
Paul: I would choose system architecture, as it involves everything in my
profession. It would be great to have the ability to map the whole to process of building the system in your brain. Normally, it comes with an experience, but it would be so cool to have it immediately.
Peers: What is the best piece of professional advice you have ever received?
Paul: “Start early” – no matter if you want to learn or start something new, do it early. I got this one from my mentors, if you want to develop, do it right away.
Peers: What is your go-to productivity trick?
I usually keep a pen and a block with me. I tried to use different productivity apps, but a pen and paper work better for me.
Peers: If you could only have three apps on your smartphone, which would you pick? And why?
Youtube and Youtube Music for listening music. I don’t like having too many native apps on my phone, so I would definitely go for Google Chrome.