From Rejection to Offer: A Career Changer's Story

The Opening

I was an accountant. At 30, I switched to programming with zero background.

Now I write code at ByteDance.

Sounds like an inspiring success story, right? But I don't want to give you motivational fluff. I want to tell you how hard this path really was, how many times I fell, and how I finally got back up.

If you're changing careers or considering it, I hope my experience gives you some real, practical insights. Not empty phrases like "just work hard and you'll succeed," but concrete, actionable lessons.

Why I Changed Careers

Many people ask me: "Did you love programming since you were a kid?"

Honestly? No.

My reason was very practical: Money.

I worked as an accountant for 5 years. My salary went from 4,500 to 8,000 RMB. A few hundred RMB raise each year, promotions nowhere in sight. I watched peers join tech companies with starting salaries double mine. Yeah, it stung.

But what really scared me was this: I was becoming obsolete.

The company started implementing financial systems. Manual bookkeeping was being automated. My daily work kept shrinking. My manager said, "These systems will get smarter. You need to learn to use the tools."

That sent chills down my spine.

It's not that I didn't like accounting. But I saw the trend—the value of my role was declining. Programmers, at least for the next 10 years, would still be in demand.

I didn't switch careers for a "dream." I switched for survival.

Year One: Self-Taught Hell

March 2021. I started teaching myself.

I made a plan: 4 hours every night after work, 8 hours on weekends.

First three months, I finished Python basics. Felt okay. Could write some simple scripts.

Then I learned Django and built a blog system. Felt pretty impressive.

Then MySQL, Redis, Docker... I learned the surface of each.

A year later, I thought I was "ready."

I sent out resumes. 50 of them.

Responses: 0.

I thought my resume was the problem. Rewrote it. Sent another 50.

Responses: 2.

Two interview opportunities. I went to both.

The first one, the interviewer asked: "What projects have you worked on?"

I said: "I built a blog system using Django."

He said: "Can you explain the architecture? How did you design the database? What problems did you encounter? How did you solve them?"

I froze. I... I just followed a tutorial. The tutorial told me what to write, so I wrote it. I never thought about these questions.

The second interview was worse. The interviewer asked: "Why do you want to change careers?"

I said: "I think programming has better career prospects."

He said: "So you don't actually like programming? You're just doing it for the money?"

I was speechless.

One year. Four hours a day. Over 1,400 hours. And I couldn't pass a single decent interview.

During that time, I really doubted myself. Was I too stupid? Was 30 really too late? Should I just give up?

First Interview: A Complete Disaster

Let me tell you about my first interview in detail, because that was my turning point.

It was a small company hiring a junior Python developer. I wore a borrowed suit and arrived 30 minutes early.

The interviewer was a guy in his 30s, looked exhausted. He glanced at my resume and said: "Your background is accounting?"

"Yes."

"Why do you want to switch careers?"

"I think programming has more growth potential..."

"How long have you been learning?"

"A little over a year."

"What projects have you done?"

"I built a blog system, and a web scraper that collects stock data..."

"Can you explain the blog system's architecture?"

"Um... it's Django, and..."

"How did you design the database?"

"Just... user table, article table, comment table..."

"What's the relationship between articles and comments?"

"One-to-many?"

"How specifically? Foreign key? Or a separate junction table?"

"I think it's a foreign key..."

"You're not sure?"

"..."

"What about the scraper? Can you tell me about it?"

"It uses requests and BeautifulSoup..."

"What if the website has anti-scraping measures?"

"Add headers?"

"And then?"

"..."

"What's the biggest technical challenge you've faced? How did you solve it?"

I went silent.

Because I had never encountered a "technical challenge." I only encountered problems that "weren't in the tutorial," and then I just skipped them.

The interviewer sighed and said: "Your basics are okay, but... your project experience is too thin. What you've built looks more like completing assignments, not solving real problems."

I walked out of that company, stood by the road, and suddenly wanted to cry.

Not because he rejected me. But because I knew he was right.

The Turning Point: I Met a Mentor

May 2022. I met Old Chen in a tech group chat.

Old Chen was a tech lead at a big tech company, a few years older than me, also a career changer. He looked at my resume and said one thing:

"Your problem isn't technical. It's communication."

I wasn't convinced: "My technical skills aren't good either. I couldn't answer any of the interviewer's questions."

He said: "You couldn't answer because you never thought about them. You 'did' the projects, but you didn't 'understand' them. You were like copying homework—you finished copying but don't know why it was written that way."

"So what should I do?"

He gave me three pieces of advice:

Build real projects, not tutorial projects—Find real needs from people around you, build things that will actually be used
Document your thinking process—Not "what I did," but "why I did it this way, what problems I encountered, how I solved them"
Learn to tell stories—An interview isn't a test, it's a conversation. You need to show the interviewer how you think

These three pieces of advice changed everything.

I Changed My Strategy

From that day on, I stopped grinding coding problems. I stopped doing tutorial projects.

I built a real system: an inventory management system for my wife's clothing store.

This was a real need:

She had to count inventory every day, which was tedious
She wanted to see sales data, but Excel was too slow
She wanted to use her phone, not a computer

I started building this system. But this time, I wasn't "following a tutorial."

I encountered real problems:

Her phone is an iPhone, I don't know iOS development, what to do? → I used React Native
Her store doesn't have stable internet, how to sync data? → I built local caching + offline sync
She's not technical, the interface needs to be very simple → I did lots of user testing, iterated repeatedly
Her data is important, can't lose it → I built auto-backup and data export

For every problem, I documented:

The context of the problem
Solutions I tried
Why they failed
The final solution
What I learned

Six months later, the system went live. My wife uses it every day.

More importantly, I finally had a project I could "tell a story" about.

20th Interview: Finally Got the Offer

November 2022. I received an interview invitation from ByteDance.

This was my 20th interview.

The interviewer asked: "What projects have you worked on?"

I said: "I built an inventory management system for my wife's clothing store."

"Can you tell me about it?"

"Sure. The background of this project was..."

I started telling a story.

Not reciting answers, but genuinely narrating:

Why I built this project
What problems I encountered
How I thought about them
What solutions I tried
Why they failed
How I finally solved them
What I learned

I talked for 20 minutes. The interviewer listened the whole time, occasionally asking follow-up questions.

Finally, he said: "Your project experience is quite unique. It's not some massive project, but you can explain the problems clearly. You can see problems, think through solutions, iterate and improve. That's exactly what we need."

One week later, I received the offer.

3 Pieces of Advice for Career Changers

Build Real Projects, Not Tutorial Projects

Tutorial projects are "copying homework." You finish, but you don't know why you did it that way.

Real projects are "solving problems." You'll encounter problems not covered in tutorials, and you have to think and solve them yourself.

Real project experience is what interviewers value most.

Learn to Tell Stories, Don't Memorize Answers

An interview isn't a test. It's a conversation.

When an interviewer asks "what projects have you done," they don't want to hear you recite tech stacks. They want to hear:

How you discovered the problem
How you thought about the problem
How you solved the problem
What you learned from it

Turn your project experience into a story with a beginning, middle, and end.

Accept Failure, But Don't Repeat It

I failed 19 times. But after every failure, I reviewed:

Why did I fail?
What did I do poorly?
How can I improve next time?

Failure isn't scary. Not knowing why you failed is.

FAQ

Q: Is 30 really not too late to change careers?

Honestly, it's not early. But it's not too late either.

At ByteDance, I met many career-changing colleagues: from civil engineering, from sales, from teaching. Ages ranged from 25 to 35.

What matters isn't age. It's whether you're truly prepared.

Q: Self-study or bootcamp?

Either works. But regardless of which path, you need to build real projects.

Bootcamps give you systematic curriculum and people to answer questions. But many bootcamps teach "tutorial projects." You need to find opportunities to build real things yourself.

Q: How long until I can find a job?

Depends on your foundation and commitment. I studied for over a year, but the first year was mostly ineffective learning. With the right approach, 6-12 months should be possible.

What matters is the quality of learning, not the time.

Q: What if I keep getting rejected?

Review. After every interview, ask yourself:

What did I answer poorly?
Why was it poor?
How can I improve next time?

Rejection is normal. I was rejected 19 times. The key is not wasting those rejections.

Q: Will I regret changing careers?

Yes. I really do.

Sometimes when I'm working until 2 AM, I think: Why am I doing this to myself? Accounting was so stable.

But more often, I think: If I hadn't changed careers, I would've regretted it for the rest of my life.

Closing Thoughts

I wrote this article over a long time. Not because I didn't know what to write, but because I wanted to write it truthfully.

I don't want to give you motivational fluff and tell you "just work hard and you'll succeed."

What I want to tell you is: This path is hard, but not impossible.

I failed 19 times before I succeeded once. But those 19 failures taught me what really matters:

Not the technology itself, but the ability to solve problems. Not memorizing answers, but the ability to tell stories. Not "doing projects," but "understanding projects."

If you're changing careers, I hope my experience gives you some strength.

You're not fighting alone.

Ready to Start Your Career Change Journey?

If you're also preparing for career-change interviews, or don't know how to prepare your project experience, Interview AiBox can help:

Simulate Real Interviews: AI interviewers will ask questions based on your resume, helping you practice storytelling
Project Experience Organization: Help you turn scattered project experiences into logical stories
Interview Review: After each mock interview, AI gives you detailed feedback and improvement suggestions

Click the button below to start your first mock interview →

Start Free Trial

Author: Interview AiBox Team Last Updated: March 2024

Interview AiBoxInterview AiBox — Interview Copilot