Hitting the Ground Running: A New Engineer’s Journey at Kogan.com
We are always excited to welcome new talent to our team! At the heart of our engineering culture is a robust and agile onboarding process that gets new joiners up to speed in no time. We pride ourselves on helping our teams hit the ground running, shipping fast, experimenting boldly, and embracing failure as a valuable part of learning.
Our onboarding is designed to immerse new team members in the action right away. From day one, they’re trusted to roll up their sleeves and tackle exciting challenges. Teams are encouraged to ship their first changes early, iterating quickly and gaining exposure to the "fun and gritty" aspects of the work. As part of our dev blog series, we speak to Fraser, one of our newest engineers, to hear about his experience joining the team and how our unique approach has supported his journey so far.
What was your first impression of the team and the kind of work you get to do here?
Joining this team has been an incredible journey, working alongside highly experienced engineers has been inspiring. It’s a fantastic environment to grow, learn, and problem solve alongside some of the best minds.
Can you describe the first project or task you worked on after joining?
I’m currently working on a project with one of Kogan.com’s verticals. It's a migration and integration project with a major financial institution. It’s been an exciting new experience, offering valuable insights and opportunities to learn.
What excites you most about the technology or product you're contributing to?
I hadn’t worked with the Django framework commercially before, but it’s been exciting to explore the structure of a large-scale Django application and come up with innovative ways to future-proof it.
How does this experience compare to other roles or teams you've been part of?
Kogan.com’s focus on in-person collaboration is incredibly refreshing. I truly value the emphasis on face-to-face conversations and the ease of tapping someone on the shoulder to quickly understand different parts of the application. It’s absolutely invaluable 🙂
Source: View source
