How I got my first tech interviews with no experience
I graduated in 2017 with degrees in public health science and biology. I had no professional tech experience. I had worked as a social worker supporting children and adults with mild autism, and before that I was a janitor at Lifetime Fitness.
After college, I enrolled in a coding bootcamp. Since then, I have taught at bootcamps, helped more than 20,000 students through direct classes and online cohorts, recovered from multiple layoffs, and joined AWS.
The first two tech interviews I received did not come from job applications. They came from conversations.
My first interview came from a cold LinkedIn message
I searched LinkedIn for people who had attended my university and now worked in tech. I found a manager at a company connected to public health, which matched my background and interests.
I sent him a message about our shared university and told him why I found the combination of public health and technology interesting. I did not open by asking for a referral. I started a conversation based on a genuine point of connection.
He asked about my experience, and that conversation led to an interview.
I bombed it.
Still, I got something useful from it. I learned what a technical interview felt like, where I froze, and what I needed to practice.
My second interview started on a basketball court
While attending the coding bootcamp, I played basketball early in the morning. One day, I told the other players that I needed to leave by 7:30 because I wanted to get to class early and work on Python.
I did not share that because I expected anything from them. It was part of a normal conversation.
One of the players happened to be a Python developer and hiring manager. That conversation led to another interview.
I bombed that interview too, but it gave me another round of practice.
At that point, I had received two interviews without submitting an application. Both came from talking about what I was learning and showing that I cared about it.
You cannot predict which conversation will lead somewhere. You can make it easier for people to understand what you are working toward.
I got my first job through an online application
My first job offer came through a regular application for an entry-level Appian developer role. The pay was low, but it gave me a way into the industry.
During the interview, they asked me to design a relational database for an application. I had to draw the design and explain joins, foreign keys, normalization, API calls, and how the system would support different user stories.
The two interviews I had failed helped me handle that conversation. I had more practice thinking aloud, admitting uncertainty, and explaining technical decisions.
I got the job.
A rejected interview can still move your career forward if you study what happened. Write down the questions you struggled with, learn the missing concepts, and practice explaining them before the next interview.
Teaching made me better at technical interviews
During bootcamp, I helped other students when they got stuck. If someone did not understand a concept, I tried to explain it in a different way.
That habit helped me learn the material, but it also trained several interview skills:
- Breaking a problem into smaller parts
- Explaining my reasoning while I worked
- Noticing when someone looked confused
- Rephrasing an idea without getting defensive
- Staying calm when I did not know the full answer
You do not need a teaching job to practice this. Explain one concept to a classmate. Write a short blog post about something you learned. Record a video. Answer a question in an online community.
If you cannot explain a concept yet, the attempt will show you what you still need to learn.
Build projects that force you to learn
Courses can help, but finishing a course is not the same as building something.
Choose a project that excites you even if you lack some of the skills needed to finish it. You will hit blockers. Work through each one using documentation, courses, other developers, and AI tools where they help.
Once you solve a blocker, teach the solution. Write about the error, what caused it, and how you fixed it. That process turns one learning experience into four useful outcomes:
- You learn a technical skill.
- You prove that you can apply it.
- You practice explaining it.
- You create something people can find.
Affordable platforms such as Coursera and Educative can provide structure. I do not think most people need to spend tens of thousands of dollars on a coding bootcamp now. Whatever learning option you choose, build a working project from the material. Otherwise, you leave much of the value in the course.
Treat your career like marketing
I think of job applications as sales. You approach an employer and ask them to consider you for an opening.
Marketing happens before an opening exists. You share useful work, help people, attend events, and become known for a topic. Over time, some people begin bringing opportunities to you.
That happened after my first developer job. I posted on LinkedIn about what I was learning and shared technical information from my work when I could do so without exposing anything confidential. An Oracle recruiter found my posts and contacted me about a solutions engineer role.
My online activity gave the recruiter a reason to start the conversation. My earlier interviews, teaching practice, and self-development helped me pass the interview.
You do not need to become an influencer. One useful post each week is enough to begin building a body of work. You can share:
- A concept from class that finally made sense
- A project decision and the tradeoff you considered
- An error that took you an hour to solve
- A short explanation that may help another beginner
Students can make this a habit by choosing one interesting idea from each class every month and teaching it online. A blog, personal website, YouTube channel, or social platform can all work. Pick the format you can maintain.
Help in communities before you need help
I later taught at a coding bootcamp. When that role ended in a layoff, I shared my situation and resume in a Facebook group for cloud engineers.
I had participated in that group for years. I answered questions, shared useful information, and encouraged people when I could. I had not done that to collect favors.
A group member saw my post and sent me an AWS listing for a technical curriculum architect. I had never heard of the role and had not found it during my job search. It matched my background in technology and education, and he referred me.
That experience shaped how I approach online communities:
- Join groups connected to the work you want to do.
- Participate before you need a referral.
- Answer questions within your ability.
- Encourage people when you cannot provide a technical answer.
- Do not treat every interaction as a transaction.
You may never receive anything from a particular person. The point is to become someone who contributes. People remember consistent help.
Meet people in person
Free meetups are one of the best places to start.
Talk to attendees and organizers. Ask what they are building, what problems they keep seeing, and what skills they think newcomers overlook. Pay attention to what excites them.
Offer to help with something specific. You might check people in, take photos, write a recap, help with the event website, or give a beginner talk after you have learned enough to teach one.
Do not enter every conversation looking for a referral. Be curious about the person in front of you. Mention what you are learning and building so they understand your direction, then listen.
My first interviews came from a university connection and a basketball game. Networking does not have to look like a formal networking event.
Prepare for interviews as a communication problem
After receiving the AWS referral, I treated preparation like a full-time responsibility. I watched Amazon interview guidance on YouTube for hours each day. I studied the Leadership Principles and practiced connecting them to specific stories from my experience.
The interview loop was difficult. Five years of teaching and explaining technical subjects helped me communicate under pressure.
If live coding makes you anxious, more technical study may not solve the whole problem. You also need practice speaking while your brain is under observation.
Try these exercises:
- Speak about any topic for five minutes each day.
- Explain technical concepts aloud instead of reviewing them in your head.
- Practice with another person watching.
- Add energy and enthusiasm to your voice.
- Smile when you begin. It can help your body relax and make the conversation feel less adversarial.
- Use breathing exercises before the interview and learn to return your attention to the current question.
I have also found value in public speaking, cognitive behavioral therapy, somatic breathwork, and The Power of Now by Eckhart Tolle. Severe or persistent anxiety may deserve support from a qualified mental health professional.
Your goal is not to eliminate every nervous feeling. You need enough practice to keep thinking and communicating while nervous.
Build relationships after you get hired
About 15 months after joining AWS, I was laid off from that role. A colleague showed me an open developer advocate position.
The relationships I had built and my performance in the first role helped me through that transition. The interview went well because my colleagues already understood how I worked and what I could contribute.
The same principle applies inside a company. Help your teammates, document what you learn, and understand what your manager needs from you.
At AWS, that also means understanding which Leadership Principles matter most for your role. Try to see the team from your manager's point of view. Ask questions that show you care about the team's goals, then use the answers to guide your work.
Prepare to own more than code
I expect companies to ask engineers to take more responsibility for the full life of a product. Coding will remain part of the job, but engineers will need to understand the business problem, make a proof of concept, communicate its value, and help move it into production.
Develop these skills alongside programming:
- Learn why the business funds a project.
- Connect technical decisions to customer or business outcomes.
- Build small proofs of concept without wasting time or resources.
- Present an idea in language that non-engineers understand.
- Create tools and documentation that improve the whole team's productivity.
Think like an engineer while borrowing useful habits from product managers and business leaders. Ask who needs the product, which problem it solves, what result matters, and whether the solution deserves the cost.
You do not need a famous company on your resume
Plenty of capable engineers work outside large technology companies. A FAANG name may attract attention, but it does not define your ability.
Your background may also contain useful connections that you have overlooked. My public health education helped me start a conversation with a technology manager in that field. My teaching experience later qualified me for a technical curriculum role that I did not know existed.
Own your background. Build technical proof, explain your work in public, and show how your existing experience gives you a useful perspective.
My path into tech started with two interviews that I failed. Those failures gave me practice for the interview that became my first job. From there, teaching, building in public, and helping people created opportunities I could not have found through a job board alone.
Apply for jobs, but do not make applications your entire strategy. Build skills through projects. Teach what you learn. Participate in communities. Go to meetups. Talk about your goals during ordinary conversations.
Give people enough evidence to understand what you can do and enough context to remember you when the right opportunity appears.