Introduction
I moved from B2B sales into software engineering six years ago. In my fifth year as an engineer, I joined a leading Japanese IT company, where I now build AI agents.
People often say that switching careers without any experience is hard. In this post I'll write about what I did, where I struggled, what my sales background gave me, and what I built up at each company on the way from a small company to a leading IT company.
When I was in sales
I did B2B sales, and I was a team leader too. Every day was about watching numbers and acting on them.
At the same time, there were many situations where I had to sell products I didn't fully believe in.
What made me switch
One of the products I sold was an electricity service. One day I saw a website where an AI recommends the electricity plan that fits your conditions.
Choosing the right product for a customer, something sales people spend time on, was being done by the AI on the spot. I stopped being sure what my own work was for. What matters is that customers can receive the service that fits them, and if IT can do that, I wanted to be the one building it.
Preparation: three months of study, and nothing else
After I left sales, I joined DMM WebCamp, a coding bootcamp, and studied 10 hours a day for three months. I did nothing else.
After that, I kept studying while job hunting. In total, that came to about 1,000 hours of study.
You sometimes hear that it takes about 1,000 hours to become useful in real work. (I couldn't find a primary source for this number, so please treat it only as a rough guide.) I used it as a guide and committed that time on purpose.
Before my first engineering job
My first company was one of the companies introduced to me by a WebCamp career advisor. It was a company that built its own service in-house.
I wrote about the preparation for that job, especially how I built my portfolio README on GitHub, in an earlier article on Qiita (in Japanese): 未経験者が自社開発企業に就職するためのREADME書き方
The first year: I couldn't keep up with the technology
The hardest thing after joining was not being able to keep up with the technology.
The school had only taught me the basics. As soon as I joined, real work began, and I had to learn the business domain and the technology at the same time. I could no longer tell which part was business and which part was technology.
What saved me was that the CTO was in a position to teach me directly. I asked about everything, and I learned by doing, with my hands.
What my sales experience gave me
The biggest thing was paying attention to numbers.
In sales, I looked at numbers every day and checked how far I had come against the target. As a leader, I was also in the habit of thinking about individual reviews and how the team worked. Even as an engineer, the habit of checking "how far have I come?" with numbers and facts is still useful.
From a small company to a leading IT company: what I built at three companies
After my first company, I changed jobs twice. Here is what I built at each, in order.
My first engineering company (about 20–50 people): building broadly, and leading
This is the first company I mentioned. They built a warehouse-management SaaS in-house. I worked broadly across front end, back end, and mobile apps. Each site had different operations, so I built APIs to handle site-specific customization. I was also given a leader role, and gained experience building features with a team of five.
Second company: seeing the gap with the people around me, and digging into the fundamentals
My second company built an admin system for a job-listing service. I changed jobs because I wanted to broaden my technical skills and development environment in a larger business at a larger scale.
It was a large, late-stage startup, and it was normal there for people to have a STEM background. Once again, I felt how little foundational knowledge I had. So I went deep into the technical side again: how frameworks work, what design patterns exist, and how to decide on an architecture.
What helped most was an extremely strong tech lead. They also taught me how to study. Don't start by writing code. First, absorb the knowledge of the language and framework properly. Take in design patterns, design, and architecture too. That is how people become better than the people around them, I heard, and I followed their example and kept taking in knowledge.
Then I used a strength I had carried over from sales, setting numbers and hitting the target, and I began to produce results that could be seen in numbers, such as test coverage.
Third company: a leading Japanese IT company, and raising my hand
At my third company, I joined a leading Japanese IT company. My reasons for changing jobs were remote work, experience at a large company, and global experience.
Before joining, I had the image that large companies have many rules and little speed or freedom. That is also what people generally say, so I was worried. After joining, it looked completely different.
Because the rules are solid, I feel more freedom, not less. And even in fields I had no experience in, I could take on a challenge if I raised my hand. I am often assigned to projects I have no experience with. I had no global experience, but I joined a team led by an American project leader and worked in Japanese and English with members from more than ten countries. I had no AI experience, but they let me into a dedicated AI team, and I led the development of an AI agent. I also worked on iPad support for an expense-reporting system, DevOps for a connected-car platform, and led a project for a screen app for an electric utility. Now I build AI agents on the company's AI enablement team.
What I felt was valued in the selection process was being able to talk about results in numbers. I talked about my experience at my first company, building broadly while leading, working directly with customers and producing results in numbers. I had also written my results in numbers in my resume, and I think that paid off.
Closing
I think four things worked for me in switching careers without experience:
- Commit a set amount of time, intensely, for the first few months
- Choose an environment where you can ask questions
- Your previous career is more useful than you think
- Join an environment where you can take on fields you have no experience in, just by raising your hand
And at each company, I built what I had been missing at the previous one. Build broadly at a small company, dig into fundamentals and design at the next, and experience scale and collaboration at a leading IT company. Looking back, that order suited me.
This is just one person's experience. I hope it helps someone considering the same path.
