Lessons from 10 Years in Tech: Interviewing Advice for Software Developers
By: Brian Stein
December 2024
After spending a decade at Amazon and AWS, working on mobile apps and Amazon QuickSight, I’ve been through countless interviews—both as a candidate and as a hiring manager. The tech interview landscape has changed over the years, but the fundamentals remain largely the same. Whether you're preparing for your first technical interview or striving to refine your approach, I hope these insights from my journey will help you.
As a disclaimer, everything in this article is my own opinion and personal experience and in no way should be construed as the opinion or view point of any of my former employers.
My Journey into Tech
I’ve always been fascinated by technology. My journey began in ninth grade with a high school web development course. That initial spark turned into a lifelong passion. I started working for a local graphics company doing small business websites, and joined a medical technology startup in college. After college I ended up landing a role at Amazon, where I’d stay for the next 10 years. Over the course of ten years, I grew from a junior engineer to managing teams, tackling exciting challenges, and learning a ton along the way.
Interviews became a regular part of my career early on, and I had the privilege of being on both sides of the table. I’ve seen how candidates can shine and where they often stumble. Here’s a bit about what I’ve learned along the way about technical interviews.
How Tech Interviews Have Evolved
When I first started interviewing at Amazon, the process was heavily reliant on phone screens. Today, many companies have shifted to automated assessments instead of a technical phone screen. These tools help filter candidates efficiently by evaluating coding skills, problem-solving, and even maintainability of solutions. While the industry was already headed in this direction, the pandemic really helped accelerate the adoption and growth of virtual interviewing tools.
Despite the changes in format, the goal of tech interviews remains constant: to evaluate problem-solving abilities and technical competence. Companies like Amazon focus on whether candidates can think critically and deliver practical, working solutions.
Are We Testing the Right Skills?
A common critique of tech interviews is that they emphasize theoretical knowledge—like Big O notation or complex algorithms—that may not be directly applicable to daily work. While there’s some truth to this, I’ve found that candidates who excel in these areas often bring a strong problem-solving mindset to their roles.
Here’s my take:
Theoretical Knowledge: While you may rarely (or never) use some concepts (like Big O) explicitly, understanding them can enhance your ability to write efficient and maintainable code.
Practical Skills: At the end of the day, companies want to know if you can get the job done. Demonstrating your ability to solve problems effectively is key.
Resumes vs. Skills-Based Hiring
As a hiring manager, I’ve rarely placed much weight on resumes. Sure, they’re useful for understanding a candidate’s background and general level of experience, but they don’t always reflect a person’s true potential. Instead, I’ve focused on evaluating what candidates can demonstrate during the interview process.
Advice for Candidates:
Don’t rely solely on your resume. Be prepared to showcase your skills in real-time.
Focus on growth. Years of experience don’t always translate to expertise if you haven’t been challenged or taken opportunities to learn.
Breaking Through: Getting That First Interview
Many candidates struggle to land their first interview. If that sounds familiar, here are some strategies that can help:
Reach out through other Channels: Don’t rely solely on job portals. Reach out directly to hiring managers or team leaders on platforms like LinkedIn. Craft a thoughtful message explaining your interest and how you’d add value to their team.
Build a Portfolio: Showcasing your work—whether through a personal website, GitHub repository, or contributions to open-source projects—can set you apart.
Network Actively: Attend meetups and forums like RC Tech Forum. These events provide opportunities to connect with industry professionals and demonstrate your passion and skills.
Working with Recruiters
There are two main types of recruiters you’ll encounter:
Internal Recruiters: Typically found at large companies, these are full time employees whose only job is to recruit for open roles. You will only find this type of recruiter at companies that can justify the cost of full-time recruiting staff.
External Agencies: These recruiters often work with multiple companies. Some specialize in specific niche fields such as Medical Technology, or Fintech.
Both options have their merits. If you’re targeting a specific company, connecting with internal recruiters is often your best bet. Connecting directly with the recruiter or hiring manager through channels like LinkedIn shows initiative and can often introduce a side door into the hiring process. For broader opportunities, external recruiters can open doors you may not have considered.
The Role of Generative AI in Interviews
AI is transforming the hiring process, but it’s far from replacing human decision-making. Here’s how I see AI shaping the future:
Efficiency in Assessments: AI can help grade coding challenges, analyze patterns in solutions, and filter resumes based on predefined criteria. This reduces the workload for hiring teams and ensures that only qualified candidates move forward.
Maintaining the Human Element: While AI can streamline certain tasks, I don’t foresee it replacing in-person interviews or the nuanced judgments made by hiring managers. Cultural fit, communication skills, and problem-solving approaches still require a human touch.
Anatomy of a Technical Interview
Here’s a breakdown of what you can typically expect during a technical interview process at a company like Amazon:
Recruiter Screening:
Initial call to discuss the role, your background, and high-level skills.
Online Assessment:
Automated coding challenges with problems that test your technical abilities. Submissions are graded for correctness, efficiency, and maintainability.
Technical Interviews:
Usually four rounds of one-hour interviews, often back-to-back.
Includes a mix of coding challenges, system design questions, and behavioral assessments.
Debrief and Decision:
Post-interview, the hiring team reviews feedback and decides whether to extend an offer.
The Challenges of Scheduling and Time Management
One of the most time-consuming aspects of the hiring process is coordinating interviews. At Amazon, every technical interview required a "bar raiser" (an unbiased interviewer ensuring hiring standards) in addition to the hiring manager. Finding time slots that worked for everyone could be challenging.
For candidates, this means patience is key. Be flexible with scheduling and understand that delays don’t necessarily reflect your standing as a candidate.
Candidate Experience Matters
Lengthy processes can be frustrating for candidates. While larger companies may have multi-step pipelines, smaller companies often move faster. As a hiring manager, I’ve always aimed for a two-day turnaround on interview feedback to respect candidates’ time and effort.
Advice for Candidates: If you’re juggling multiple interviews, communicate openly with recruiters about your timelines. Transparency helps both sides manage expectations.
Tips for Acing Your Next Interview
Prepare Strategically:
Brush up on algorithms, data structures, and system design.
Practice coding challenges on platforms like LeetCode or HackerRank.
Communicate Clearly:
Explain your thought process during coding exercises. Interviewers value clarity and logical reasoning.
Be Proactive:
If a question stumps you, don’t panic. Share your approach and ask clarifying questions.
Follow Up:
After the interview, send a thank-you note. It’s a small gesture that leaves a positive impression.
Final Thoughts
Technical interviews can be daunting, but they’re also an opportunity to showcase your problem-solving skills, adaptability, and determination. Remember, preparation is key, and every experience—even a failed interview—is a stepping stone to success.
Whether you’re just starting your journey or looking to advance your career, stay curious, keep learning, and don’t hesitate to leverage your network. Opportunities often come from the most unexpected places.
Good luck out there!
About the RC Tech Forum
The RC Tech Forum: Building a Community of Innovators
The RC Tech Forum was founded with a vision to create a dynamic and inclusive space for technology enthusiasts, innovators, entrepreneurs, and students. Based in the Inland Empire, a region brimming with untapped potential, the forum serves as a centralized platform where individuals can come together, gain valuable experience presenting their ideas, and learn from seasoned speakers. Our mission is to amplify technology growth and foster entrepreneurship within the Inland Empire and beyond.
With over 400 members and growing, the RC Tech Forum has become a magnet for tech-minded individuals from across Southern California. Our community thrives on the hunger for knowledge, collaboration, and innovation. Each month, we host engaging meetups that feature diverse topics ranging from blockchain and artificial intelligence to business strategies for startups and beyond. By adapting our format regularly, we ensure our events remain fresh, relevant, and tailored to the interests of our members.
At RC Tech Forum, we value feedback from our community to guide the topics we explore. Whether you're delving into highly technical subjects or engaging with non-technical content, our events promise something valuable for everyone. Together, we aim to elevate education, spark meaningful discussions, and tackle challenges that drive the tech ecosystem forward.