We currently have 6 months for onboarding. This helps you, as our new colleague, get used to the different environment, the company’s priorities and ways of working.
What requirements we signal before hiring
The self-assessment contains all the elements we try to foster. It shows 4 main areas:
- CPU programming & algorithms
- GPU programming & performance oriented programming
- Problem solving
- Collaboration, planning & prioritization
Each of these, and some personal skills, we discuss, improve and measure. Six months is never enough to improve on everything, but it is enough to focus on the items where most need to be done. It’s certainly enough time to understand what quality means and how to get there.
It’s easy to get confused about quality. Quality might mean deluxness, fanciness, expensiveness. That’s not what quality means. Quality means meeting spec. Keeping the promise. Doing exactly what you said you would do. It is measured in consistency.
Seth Godin
First week(s)
Getting started means you get everything on your desk at once. Best to have a checklist:
- Creation of accounts
- Ask questions you might have to your buddy.
- Introduction to others.
- Learning the basics of the development and collaboration environments
- Get necessary hardware, including noise-canceling headphones.
- Make technical contributions from the first day, as this provides:
- Measurable contributions
- Time management
What to expect in your first months
In your first weeks, you’ll ease into a project, pair up with a buddy, meet teammates (both in-office and remote), and get familiar with how we work, daily standups, time tracking, and internal tools like GitLab. You’ll also learn about our team culture, performance expectations, and key documents that shape how we collaborate. Regular check-ins at one, and five months help track your growth, gather feedback, and support your long-term development.
