In an effort to better serve our enterprise customers, we are building up our engineering presence in San Francisco. We recently sat down with Andrei to find out how candidates can make sure they make it to the top of the CV pile. He goes through the key steps of our interview process and discusses how engineers can make an early impact when joining a company as staff or senior staff engineer.
It’s a familiar experience that lots of us have shared — migrations to merging, refreshes and refactors. It can be a tough conversation to have, but reworking your design system can be what’s in the best interest of everyone.
Our design system has a good foundation, but after thumbing through the libraries, we discovered a few things that could use some tweaking to help take us to the next level.
We sat down with Stu Cavill, Senior Engineering Manager for Growth at Productboard, to talk about the significance of Growth Engineering, the differences between Growth Engineers and Product Engineers and the skills needed to successfully drive growth.
At the helm of all our big tech initiatives is our dedicated Architecture Guild, a diverse team of experienced individual contributors that plays a central role in influencing the direction our architecture takes.
Analyse, over-communicate, strategize and collaborate. When you get right down to it, these are the four core skills that management consultants and product managers have in common.
I’d like to share a few things I learned along my journey from management consultant to product manager. Perhaps my insights might help you better navigate your own career path.
If you are a product-maker, one of your most important allies when sitting down at the collaborative discovery table should be User Story Mapping.
It helps teams to visualize the whole user journey as meaningful increments and have really good discussions, with the aim of building a mutual understanding of the challenges they face along the way.
A few years ago, we started a podcast about engineering leadership and management – what it takes to be an engineer at an IT company.
We recently decided it was time to move from Cypress 9 to Cypress 12 on the platform team. Here’s a brief look a what went on behind the scenes.
Anyone who has worked on a multi-team collaboration knows that even under the best circumstances, things can get pretty tense. Check out our key takeaways for streamlining cross-pillar collaborations at your company.
I celebrate and reflect on my 11-month internship at Productboard. In those 11 months, I achieved two things: I entered the job market and validated that I can and want to work as a product designer. I went from being a complete novice to owning my own domain and shipping a feature. I’d like to share how I did it.
Our designers are avid users of Productboard and benefit greatly from gaining a deep understanding of customer needs and feedback trends, staying organized within our product teams, as well as understanding how our work fits into the all-company roadmap.
In this article, we’ll run through some tips on how to integrate Productboard into your day-to-day workflow. We’ll look at how we leverage Productboard for seven key activities, although it’s worth noting that each activity is important regardless of the tool(s) you end up using.
The code review is an essential step in shipping high-quality code. What’s more, it allows developers to share knowledge, give feedback, and learn from each other’s expertise and mistakes. But depending on how we do code review, it can either be a time-consuming hassle or a breeze.
In this article, I’ll share some tips that we use here at Productboard to ensure that code review runs smoothly — for both authors and reviewers. Let’s start at the beginning.
