Career Switching to Tech at 30: From Sales to Frontend Developer at Amazon

Background

Let me start with my situation. I'm 30 years old, and I spent 5 years in sales — from door-to-door to telemarketing to enterprise accounts. I was what you'd call a seasoned salesperson. But honestly, the longer I stayed in sales, the more exhausted I became. KPIs were suffocating, client resources were hoarded by veterans, and newcomers had almost no room to grow. Most importantly, I couldn't see a future.

When I was 29, a friend who worked as a frontend developer told me his team had just hired someone who transitioned from the restaurant industry. I was stunned — career switching was actually possible? So I started teaching myself to code. After work every day, I watched tutorials and wrote code. On weekends, I lived at the library. I kept this up for a full year. From HTML/CSS to JavaScript, then React and Vue — I learned everything I could.

A year later, I quit my job and started looking for work full-time. Honestly, I was terrified. Thirty years old, no relevant work experience, a resume full of sales roles — who would hire me?

Interview Process Review

Company 1: A Startup (Failed)

This was the first company I applied to, a SaaS startup with about 20 people. Their HR reached out to me on a job platform after seeing my GitHub projects. I was excited — someone finally recognized me.

The first round was a technical interview with a guy who looked a few years younger than me. He asked me to introduce myself, and when I mentioned switching careers at 30, he visibly paused. Then he asked a question I'll never forget: "Why didn't you stay in sales?" It sounded like concern, but I knew he was questioning my decision.

The technical questions were all basics — CSS centering, JavaScript closures, React lifecycle methods. I did okay, but the live coding section exposed me. He asked me to write a debounce function, and I couldn't pull it off. He ended with "we'll be in touch," and I knew it was over.

Company 2: A Mid-size Tech Company (Failed)

The second company was an e-commerce business with about 200 employees. The process was more formal — an online coding test followed by two technical rounds.

I passed the coding test, but the first technical interview went south. The interviewer looked at my resume and asked point-blank: "You don't have a CS degree or relevant work experience. Do you think you can handle this role?" My heart sank, but I pushed through and talked about my learning journey and projects.

The technical questions went deeper — Vue's reactivity system, virtual DOM implementation, webpack's build process. I could explain Vue's reactivity at a high level, but virtual DOM and webpack? I was just reciting from memory. The interviewer clearly wasn't impressed. He also gave me an algorithm problem — Two Sum. I wrote a brute-force solution, and he asked, "Can you optimize the time complexity?" I knew a hash map would work, but I couldn't implement it on the spot.

The worst part was at the end when the interviewer said: "Your fundamentals are decent, but honestly, we prefer candidates with experience." That hit me like a bucket of cold water.

Company 3: A Mid-size Tech Company (Passed!)

The third company built internet products with about 150 employees and a 10-person frontend team. The interview experience was completely different.

The first round was with a friendly female interviewer, probably around 27 or 28. She showed zero bias about my age or career switch. Instead, she said, "Career switchers often have more self-drive. I think that's an advantage." I almost cried right then.

The technical questions were practical — how to implement infinite scrolling, component lazy loading, CORS solutions. These were problems I'd encountered in my projects, so I answered smoothly. For the live coding, she asked me to implement a simple Promise. I got it done — not perfect, but the core logic was correct.

The second round was with the tech lead. He asked about my projects, my views on frontend development, and my future plans. I shared everything — the pitfalls I'd hit while learning, the projects I'd built, my understanding of the field. He listened carefully and finally said, "I respect your learning ability and attitude. Technical skills can be improved over time."

The HR round was about salary and start date. They offered me 15K RMB — not high, but a huge validation for me.

Real Interview Questions

1. Multiple ways to center elements horizontally and vertically in CSS

2. What is a JavaScript closure? Give a practical example

3. Differences between React and Vue? Which do you prefer?

4. Implement a debounce function from scratch

5. Vue's reactivity system (difference between Object.defineProperty and Proxy)

6. What is Virtual DOM? Why do we need it?

7. Webpack's build process

8. Two Sum (LeetCode #1)

9. How to implement infinite scrolling?

10. Implement a simple Promise from scratch

11. Component lazy loading approaches

12. CORS solutions

13. Why did you switch to frontend development?

14. What are the advantages and disadvantages of career switchers?

15. What's your career plan?

Key Takeaways

1. Age anxiety is real, but don't let it trap you. I did encounter bias during interviews. Some interviewers directly or indirectly expressed distrust of career switchers. But I also met people willing to give me a chance. Don't give up because of your age — someone will see your value.

2. Project experience matters more than degrees. As a career switcher, you lack a CS degree and relevant work experience. The only thing that proves your ability is your projects. I had 5 projects on GitHub. Though they started from tutorials, I made significant modifications and extensions, and I could clearly explain the tech stack, implementation approach, and challenges for each one.

3. Fundamentals must be solid. My first two interview failures were largely due to weak fundamentals. Closures, prototype chains, event loops — you can't just memorize these. You need to truly understand them. Live coding is crucial too: debounce, throttle, Promise, deep clone — you must be able to write these from scratch.

4. Choose the right companies. Big tech isn't friendly to career switchers — you won't even pass the resume screen. Mid-size companies value practical skills more and have more pragmatic interviews. Get your first job, build experience, then consider bigger moves.

5. Mindset matters. Rejection is normal, especially for career switchers. I sent about 50 resumes, got 5 interviews, and received 1 offer. But one company giving you a chance is all you need.

FAQ

Q: Is 30 too late to switch careers?

A: Honestly, it's not early, but it's not too late either. I know people who switched at 35 and even 40. The key is whether you're willing to put in more effort than others. The first year is the hardest — push through and it gets better.

Q: How should I self-teach programming?

A: Set a clear goal first, like "I want to do frontend development," then learn systematically in that direction. Don't dabble randomly — that's inefficient. Start with video tutorials, then build projects, and look up documentation when you're stuck. Most importantly, be consistent — at least 2 hours every day.

Q: How do you answer age-related interview questions?

A: Don't dodge them, and don't feel inferior. I say: "I'm indeed 30, but I taught myself frontend development from scratch in one year. That proves my learning ability and execution. Age isn't a problem for me — it's helped me become clearer about what I want."

Q: Will my salary drop significantly after switching?

A: It definitely will. I was making 20K in sales, and my first tech job paid 15K. But that's temporary. Once you have 1-2 years of experience, your salary will catch up quickly. Plus, tech has a clearer career development path than sales.

Q: How should I write my career switch on my resume?

A: Put your project experience first and highlight your technical skills. Keep your work history brief but honest. I proactively explain my career switch in my self-summary, emphasizing my learning ability and passion for technology.