When Productboard started in 2014, our clear focus was on product managers in smaller teams who lacked a great product management tool. Nowadays, we help much larger companies with thousands of employees, and we need to solve quite different needs and personas.
When it comes to an engineer’s life at Productboard, there’s a lot to cover. We’ve talked about the hiring process, and you got a detailed behind-the-scenes look at our onboarding process, workflow, and team dynamics.
After taking you through the hiring process in my last post, I now want to delve deeper into engineering life at Productboard. I’ll be detailing the onboarding process — two weeks of fun dedicated to studying the ins and outs of Productboard, pair programming, and getting to know the team.
This three-article series covers why I decided to join Productboard as an engineer and how things work inside the company.
Whether you’re starting a new engineering job soon or have only just begun looking for new opportunities, taking the next step in your career can be a daunting experience. Set yourself up for success and stay on track using a simple 30–60–90 plan, which will help you prioritize your goals for the first three months at your new job and make your onboarding process smoother.
And that is correct! Network glitches, deployment glitches, dependencies upgrades, developer’s carelessness or just small data inconsistencies. There’s plenty of stuff in web development that can go wrong, and it will go wrong at some point. What’s far more important than trying to prevent anything from going south is having solid monitoring in place and clear processes to follow.
This article describes how to identify intermediate states while loading using React Suspense.
Every modern app needs to load data from a server. This may take a while, and making our users wait on a blank screen just won’t do.
Now comes the choice — loading spinner or loading skeleton.
Building a design system without knowing how it is used can be very tricky, and even the simplest of questions can be hard to answer. Do you know how often your components are used? Can you remove deprecated components from the code? What is the adoption of your design system?
It was in the spring of 2018 when I first interviewed for the position of a product designer at a local startup — you guessed it, Productboard.
In part one, I provided an introduction to our design ethos and team set-up here at Productboard. For part two, I’ll discuss how we work, focussing on the important matters of collaboration and feedback.
As we continue to grow at a rapid pace, we’re always on the lookout for talented new designers to join our team. We interview a lot of people in the process. And those people ask a lot of great questions. In this series of articles, I’ll answer some of the most frequently asked questions we get asked.
In this series of articles, I answer some of the most common questions we get asked by design candidates during the interview process. The aim is to provide as much clarity as possible, giving future candidates all the information they need to approach their Productboard journey with confidence.
