Alba Mustafaj

Tell me about yourself and your journey into big tech.

I’m originally from Berat, a small town in southern Albania. I left to study computer engineering in Turkey, where I earned my CS degree. Growing up, I was always fascinated by space exploration - I dreamed of becoming an astronaut. But in my final year of high school, I worked with a friend to build a website about the human brain, and that changed everything. I realized how powerful programming can be, even in fields like healthcare.

During my bachelor’s, I started applying to master’s programs and also explored roles at big tech companies. At the time, I wasn’t sure what I wanted, so I tried everything I could to figure it out. I had a mentor - someone with over 20 years in the industry - and one question he asked stuck with me: “If you could do anything right now, what would you choose?”

That helped me realize I didn’t have a strong preference for a specific specialization in my master’s. I was more curious about the kinds of problems companies were solving. That’s when I started seriously preparing for tech interviews. I was eager to start working right after graduation - and just four days after finishing school, I moved to start my job at Amazon.

The way I got the role at Amazon was pretty unexpected. I had subscribed to a bunch of job alert sites, and one day, the role popped up. I didn’t know anyone at Amazon at the time, so I just cold-applied.

Looking back, I think what may have helped my application stand out was that I had completed an Android Nanodegree outside of school and learned C# independently. These "learn and be curious" data points might have caught the eye of recruiters.

The process back then started with a phone screen, followed by a loop of four back-to-back interviews, each with technical and behavioral questions. I only had about three weeks to prepare. I wasn’t a competitive programmer, but my CS fundamentals - data structures and algorithms - carried me through.

To anyone preparing for interviews, I recommend building strong foundations. You can solve hundreds of problems, but if you don’t understand the underlying concepts, you’ll always get stuck when faced with something new.

Now that I’m a software engineer at Amazon, I also participate in hiring loops as a "bar raiser" - someone that ensures we are hiring someone that raises Amazon's bar. I really enjoy this part of my role and will try to share insights from my own experience.

One thing I see often is that candidates underestimate the importance of non-technical questions. Interviewers look for specific data points: technologies you’ve worked with, team dynamics, learnings from setbacks. It’s not just about saying "this failed" but rather showing what you learned and how you grew from the experience.

In your current role, what does a typical day look like and what are your main job responsibilities?

I've been at Amazon for six years and have worked in two major organizations. When I started, I was part of the global transportation org, building internal tools for Amazonians. Now, I work on more external-facing products.

There’s no such thing as a typical day - it really depends on the nature of your role and your level. Early on, I worked mostly on well-defined tasks. As I grew, I started tackling more ambiguous problems, collaborating with stakeholders, and even initiating side projects that could benefit the organization.

In my current role, I spend time writing code, but I also collaborate across teams and functions. I work closely with product and program managers, and often partner with teams outside my org on projects that impact the broader customer journey. That variety and challenge keeps me excited.

What advice do you have for others who want to break into big tech or do what you do?

Your path into tech might not be linear - and that’s okay. There are many roles in tech, each with its own niche. It’s normal to question which one is right for you. What matters is being honest with yourself about what excites you. If you’re not passionate about something, it’s hard to excel in it.

At one point, I considered switching from software engineering to solutions architecture. I found a mentor, explored the role, and eventually realized I preferred coding. That kind of exploration is normal. And so is reaching out to people - through LinkedIn, at networking events, or mentorship programs. Sometimes "we don't know what we don't know" so networking can help us figure out what direction we want to go in.

When applying for roles, show a complete picture of your experience. Highlight the technologies you’ve used, what you’ve learned from collaboration, and anything that makes your resume stand out. It doesn’t have to be a fancy certification - for me, it was learning C# for a school project.

I know you're a lead for Amazon Women in Engineering and involved in the University Bootcamp and Mentorship program, can you share about your experience?

A few years ago, I launched a university engagement program. It’s a free, nine-week bootcamp where students pair with two Amazonians to build a project of their choice. The goal is for them to be better prepared for industry jobs. We have over 200 mentors involved globally.

One of the things I love about Amazon is how supportive it is of grassroots initiatives. If you have an idea and the time, you can make it happen. Leading this program has helped me build soft skills like influencing and stakeholder management - skills that have translated back into my engineering role.

26 new remote roles! 🙌

Thank you so much for taking the time to read today’s newsletter! If you have any feedback, please let me know down below. Have a great rest of the week and see you in the next one! Cheers, Brenna

Other ways I can help you

Download my personal resume template: It has helped me land interviews at companies like Meta, Google, TikTok, Salesforce, and Uber.

Book a 1:1 coaching call with me: I’ve helped jobseekers land interviews and offers at companies like Meta, Amazon, Salesforce, and Pinterest.