Are you about to start an engineering internship and are wondering how you can optimize your time there? Or maybe you’re starting your first full-time job and want to get started on the right foot. Throughout my internship at Shift and other past internship, I have learned many invaluable lessons that helped me grow as an engineer and perform well at my internships. Here are some of the lessons and tips that I find most important to optimize your internship!
Be customer focused
Whether you’re building a new consumer-facing feature or internal tool, you should always be thinking about your users and customers.
Who are the users of your project? Are they engineers, data scientists, or car buyers? Are they technical? What is going to bring the best user experience to them? Understanding your users will help drive the direction and vision of your finished product.
Why are they using it? Are they using the product to buy/sell a car, for entertainment, or something else entirely? This is a question to address early because if you can’t think of any reason why they would use what you’re building, you should hold off on writing code. Instead, talk to your manager, designers, and even customers to get a better understanding of why people would want your feature. This step will also help you understand the leverage and impact of your project! Continue reading “How to make the most of your engineering internship”
When I received my first code review as a fresh new engineering intern, I was horrified. How could I have received 87 comments on a 50 line code change? After getting A’s in all my CS classes, how could I be so unprepared for programming in the real world? After taking a deeper look at the comments, I realized that my fundamentals were fine, I simply didn’t know any of the industry style guidelines or best practices. The code review comments were extremely helpful in teaching me the industry standards for programming in Go. To help any future engineering interns, this blog post is a list of the three Go styles and best practices I wish I had known before I started my internship.
Continue reading “Getting Started with Go: 3 Tips for Engineering Interns”
Andrew Carman is a software engineer at Shift.
At the core of any market is pricing. If you get pricing wrong, your marketplace doesn’t work. Our success at Shift—as a marketplace that makes it easy for anyone to buy and sell used cars—hinges on accurately and competitively pricing cars.
Dealerships traditionally have a team of experts that price trade-ins for customers and manage the prices of their vehicles. They haggle over those prices with buyers that come to their dealerships, and often take advantage of consumers who have less access to car price data.
Our goal is to make selling and buying a car a fun, fair, and accessible experience by using technology to disintermediate what car dealerships do poorly. So we build software instead of back-office sales teams to price our cars, which increases efficiency, levels the playing field for our customers, and lets us systematically improve the accuracy of our pricing over time.
Read on to see exactly how we did it, and pass this along to the folks who might be interested in our approach.
Continue reading “How I Used Machine Learning To Price Used Cars”
Kate Heddleston is an Engineering Manager at Shift.
When I was first learning to play water polo, a coach told me something I’ve never forgotten. He said, “Great players make everyone around them look like great players.” A great player can catch any pass, anticipating imperfect throws and getting into position. When they make a return pass, they throw the ball so that the other person can make the catch easily.
Here at Shift HQ, software engineering is a team sport. Like water polo, you can’t build incredible software systems alone. So when I first heard the concept of the 10x engineer, I was confused. How could someone be so talented that it overshadows the power of teamwork? In my experience, individual excellence is necessary, but not sufficient, for greatness. Focusing purely on individual achievement misses the larger picture that teams are required to build great software. So I decided to change the definition of a 10x engineer to this:
A 10x engineer isn’t someone who is 10x better than those around them, but someone who makes those around them 10x better.
Over the years I’ve combined my personal experience with research about building and growing effective teams and turned that into a list of 10 ways to be a better teammate, regardless of position or experience level. While many things on this list are general pieces of advice for how to be a good teammate, there is an emphasis on how to be a good teammate to people from diverse backgrounds. Read on, and pass this along to the people you work and collaborate with on the daily!
Continue reading “10 Tips For Becoming A Better Teammate”
By: Emily Nguyen
Should I intern at a startup or a large company? With so many companies to choose from, picking a place to intern at is a difficult decision. It may be tempting to choose a large tech company, because of its well-known brand and perks. I used to be hesitant about startups too. In the past, I’ve interned at some of the big tech giants…and it was a great experience. However, for my next internship, I wanted the opportunity to work at a small startup where I would be able to build software from scratch, learn how a company operates early on, and make a significant impact.
I ended up interning at Shift, with their Buyer Experience team. What attracted me to this startup was the people, mentorship opportunities, interesting engineering challenges, and the chance to make a huge impact at a high-momentum startup. In the 12 weeks of my time at Shift, I’ve learned more than I have in all my past internships.
Continue reading “SHIFT-ing Perspectives: What I Learned From My First Startup Internship”
Buying and selling cars isn’t easy. Not only is it a large transaction, it’s a highly regulated one. To top it all off, here at Shift we believe you shouldn’t have to complete it at a dealership. You should be able to buy a car on your own turf whether that’s your home, your office, or your SoulCycle. Luckily we have a crack team of Car Enthusiasts (CEs) to make this possible. To make their job possible we have Assistant. Assistant is the internal iPad app used by our field teams on all types of appointments. Throughout the development process we keep three core tenets in mind. Continue reading “Assistant or: How I Learned to Stop Worrying and Love Field Ops”
Shift’s engineering team has always had an informal process around design docs for new systems, but the process has varied from team to team and engineer to engineer. We’ve had the assumption that if a project or feature is expected to take more than a week or involve more than one engineer, it probably makes sense to document your design in advance so you can get feedback.
A few engineers from our infrastructure team recently formalized the process to add some consistency with the main goal of streamlining the process–we want the term “design doc” to mean the same thing to everyone and to prevent engineers from feeling like they have to reinvent the wheel every time. We also think design docs can be used for mentorship because they allow junior engineers to get feedback faster than through code reviews.
Continue reading “Knowledge-Sharing with Design Docs”
At Shift, a foundational belief is that the used car market is local and that customers need to see, feel, and smell a car before they are comfortable buying one.
With this belief in mind, one of our core value propositions is we will meet you where and when you want us to, and when we meet we are able to do all things a traditional dealer needs to do in order to sell you that car from the comfort of your driveway.
Delivering this core value proposition may seem simple — companies have been doing field sales for ages — but to do it delightfully, efficiently, and at scale with vehicles is a tough problem. Here at Shift, we call the system that coordinates all of this the Logistics Platform, and its main responsibilities are to:
- Model customer demand and manage our availability
- Monitor and adjust operational schedules
- Enable the field sale
We’ve built parts of the system so far, and have grand plans for the rest, so let’s dig in and see what these responsibilities really entail.
Continue reading “Logistics at Shift”