In 2013, I was ready for a career change.
Well, to even say I had a career is generous. It'd had been four years since I graduated college with an Econ degree and I was jumping between one random thing to another to pay the rent. I was stuck. Amongst other things, this included trying to sell ebooks and pants (yes, like real pants) online. I had learned to make basic iPhone apps, but it was immediately clear I wasn't going to be coming up with the next app idea that was going to go viral.
I set a goal for myself to get a job at a top-tier tech company to jumpstart my career.
I spent days perfecting my resume, but couldn't get an interview. Naturally, I assumed that meant I had to work on it more. I agonized over every word and drove myself crazy with formatting. I finally perfected it, and every time I applied to a job posting, I was filled with hope. This is going to be the job that gets me into tech, I thought.
But I wasn't getting interviews. Even when I was applying through referrals, I wouldn't hear back. Eventually, it hit me: I was applying to the wrong roles.
I was going after software engineering and product manager roles at brand-name tech companies with limited programming and no product experience. No wonder I was getting rejected left and right — I was applying to roles I aspired to one day have, but in reality, my background and skills didn't meet the needs for those positions. At least, not yet. I had to change my approach.
Instead of thinking about what I wanted, I thought about it from the company's perspective: What needs do they have that I can fill right now?
This approach is especially helpful if you're transitioning into tech from a different industry, non-traditional background or just don't have the relevant experiences for the role you want.
Since I didn't have the background or experience to get interviews for my aspirational roles, I started looking for positions that would be stepping stones toward them. I looked for roles that would give me relevant experiences for my next job — I was thinking two roles ahead.
Before applying to my aspirational role, I wanted to make sure I had two things. First, experience working at a brand-name tech company. Second, a role that gave me an understanding of how end-users used products. I knew those experiences would help prepare me for the job I would apply to next.
With that in mind, I honed in my job search on technical customer support roles. I wanted an end-user facing role where I could leverage the technical skills I built up learning how to make simple iPhone apps earlier in the year.
Once I started to apply for those roles, I was getting interviews, not rejections, left and right.
I had my sights set on the Forward Deployed Engineer role at Palantir and what later became the Product Specialist role at Dropbox. These two roles hit the criteria for the experiences I wanted to gain for future roles. Just as important, I had the background and skills that these roles needed now.
After going through onsite interviews at both companies, I eventually joined Dropbox as a Product Specialist (then called Embedded User Operations Engineer). I was able to immediately contribute in my first role at Dropbox and in one year, I transferred to the Partnerships team. A year after that, I successfully went through the internal interview process to become a Product Manager, my aspirational role.
By recommending stepping-stone roles, I'm not telling you to sell yourself short — I'm telling you to invest in your future. When you're trying to break into tech, for example, focus on getting into a tech company first, then transitioning into your aspirational role.
Everyone's situation is different, so by all means, if you'd like, go after your aspirational role right away. But if you're not even getting interviews, you may want to take a step back and consider if you're applying for the right roles.
Like this story? Like CNBC Make It on Facebook