Switching careers can feel like jumping off a cliff – exhilarating and terrifying in equal measure. For me, that cliff was public health, and the landing? A surprisingly soft patch in the world of tech, specifically as an OpenShift Engineer Intern at Red Hat. This transition, a Career Pivot Into Coding Bootcamp, wasn’t on my radar until fairly recently, but it’s been the most rewarding professional decision I’ve ever made.
When I shared my story online, the response was overwhelming. My LinkedIn and Twitter notifications exploded with questions: “How did you do it?” “Is a coding bootcamp really worth it?” So, for those of you curious about making a similar leap, I’m laying out my journey, offering insights and advice based on my personal experience.
Before we dive in, a crucial disclaimer: my experience is rooted in a specific bootcamp – General Assembly (GA) in Boston. While I can vouch for their program, I can’t speak to the quality of every bootcamp out there. It’s also important to manage expectations. Enrolling in a bootcamp is a significant step, but it’s not a guaranteed golden ticket to a FAANG job right away. While those stories exist, they are the exception, not the rule. Be prepared to work hard and be realistic about your initial job prospects. Having a supportive partner in tech, like my software engineer boyfriend, definitely provided invaluable support and insights. Finally, I acknowledge my privilege. Financially, this pivot was possible because of loans from my mother and boyfriend, which eased the burden of living expenses during the bootcamp and job search. Not everyone has this safety net, so carefully consider your financial situation and prepare for potential belt-tightening (ramen upgrades are a must-learn skill!).
So, how did a public health graduate end up in the world of open-source technology? Let’s rewind to my pre-bootcamp life.
From Public Health to Public Tech: Finding My Calling
My academic background is in Public Health Sciences from UMass Amherst (Class of 2017). I was drawn to the field by a genuine interest in social determinants of health and a desire to help people thrive. My first job after graduation was as an environmental technician. While technically related to public health, spending my days collecting air samples on construction sites felt far removed from my initial aspirations. It lacked purpose and direct impact. After a year, I knew I needed a change.
I transitioned to a community coordinator role, which felt closer to my public health degree’s intent. I worked with residents in Section-8 housing, connecting them with resources and organizing community programs. While the job’s nature was fulfilling, I felt increasingly burnt out, unmotivated, and disconnected. The pay was barely enough to live comfortably in Boston. A classic quarter-life crisis was brewing. I knew I couldn’t sustain this path long-term.
Seeking alternatives, I attended the 2019 PAX East conference. The intersection of health and gaming sparked a new interest. My boyfriend, a software engineer at Google, suggested coding. Coding? For me? It seemed like something for geniuses, not someone with a public health background. However, intrigued, I tried free online coding tutorials on freecodecamp.org. To my surprise, I enjoyed it. Building web pages, manipulating elements, and even JavaScript (which initially seemed daunting) became engaging puzzles.
I researched coding bootcamps in Boston and General Assembly’s 12-week Software Engineering Immersive stood out. The location was accessible, and the program boasted strong employment prospects. The cost was significant, but the potential salary jump in software engineering meant I could recoup the investment within a year. After visiting the campus and speaking with an admissions counselor, I decided to take the plunge. A symbolic purple hair dye later (quarter-life crisis still in full swing!), and I was committed to this new direction.
Bootcamp Immersion: Projects, Problems, and Progress
My three months at GA were intense and transformative. It was a whirlwind of projects, late nights, and a newfound Stardew Valley obsession (farming pixels is surprisingly therapeutic when real-life coding gets stressful!). While I won’t detail the entire curriculum (their website has you covered), here’s the gist:
GA covered the fundamentals: HTML/CSS, JavaScript, Node, Ruby on Rails, Express, MongoDB, and React. Truthfully, the specifics of syntax have faded (thank goodness for Google!). However, the lasting value wasn’t just the languages. GA taught me how to learn and how to problem-solve. They instilled principles like Git, version control, and agile methodologies. They equipped us to combat imposter syndrome. Crucially, they taught us to break down complex problems into manageable pieces. GA provided a solid foundation of principles that I could build upon.
Our first major project, the infamous tic-tac-toe game, became a crucible. Building a functional game with a Ruby backend to manage user and game data in just five days seemed deceptively simple. “Tic-tac-toe is child’s play,” right? Wrong. This project pushed many of us to our limits. Day two was my near-quit moment. But GA’s instructors were incredible. They offered just the right amount of guidance to nudge us forward without giving away the answers, mirroring the support you might find from a tech manager. After surviving tic-tac-toe-gate, subsequent projects felt less daunting, especially once we collectively discovered the power of StackOverflow.
Another vital component was GA’s career coaching, branded as “Outcomes.” Each week featured workshops on job search essentials: resume and cover letter crafting, LinkedIn profile optimization, behavioral and technical interview preparation, job searching strategies, and even salary negotiation. Weekly homework assignments, focused on these topics, were mandatory for continued post-graduation career support. This structured career guidance proved invaluable during the job search phase.
Overall, my GA experience was overwhelmingly positive. I felt genuinely supported and encouraged. The instructors and staff fostered a real sense of community, making me feel like a valued individual, not just another tuition payment. They were invested in my success and attuned to our well-being, offering support when they sensed frustration.
In summary, enrolling in General Assembly Boston was a fantastic decision. I wholeheartedly recommend their program to anyone considering a career pivot into a coding bootcamp.
Navigating the Post-Bootcamp Job Market
Graduation day, December 9th, 2019, marked the start of a challenging period. I hadn’t been unemployed since I was 17, and the weight of my debt grew heavier each day. Some days, I’d force myself to commute downtown to work on job applications at the GA campus. More often, I’d sleep in, passively scroll through LinkedIn, submit a few applications, and then wonder why I wasn’t getting any responses. Graduating in early December, right before the holiday hiring freeze, certainly didn’t help.
As the new year began, I resolved to get serious about my job search. I treated applications with more intention and committed to daily coding interview practice. I aimed to push something to my Github each day (those green squares are surprisingly motivating!). I also resumed working out and started networking aggressively, signing up for numerous Meetup events.
One standout event I discovered on Meetup was TechTogether Boston, a free 3-day hackathon for women and non-binary individuals at Boston University. Hackathons were new to me, but I saw it as a networking opportunity with potential seminars and, let’s be honest, free swag (t-shirts and stickers are my weakness!). Despite still feeling like a coding novice, I joined a team of fellow first-timers, and we brainstormed project ideas.
Around this time, amidst my renewed job search efforts, I landed an interview for a full-time position at Grubhub in Boston. A college connection working there had provided a referral. I was thrilled to get a phone interview, then a virtual coding challenge, and then, incredibly, an on-site final interview. However, my optimism waned when I learned another GA classmate was also a finalist. It felt like a head-to-head competition. She was undeniably a stronger coder. Despite giving it my best, the rejection email stung. It felt like starting over again.
Hackathon to the Rescue: Red Hat Emerges
Just moments after the Grubhub rejection email, I walked into the TechTogether Boston hackathon, surrounded by hundreds of talented individuals and recruiters from companies like Facebook, Capital One, Wayfair, and IBM. Feeling vulnerable, I wasn’t initially eager to hand out my resume. But I was there, and free swag awaited!
One of the first booths I approached was Red Hat. Frankly, I’d heard of them but wasn’t sure what they did. I spoke with a recruiter who was incredibly kind and encouraging. She didn’t dismiss me for being a bootcamp graduate. Although they were primarily recruiting summer interns (and I was seeking immediate employment), I gave her my resume anyway. Her positive interaction boosted my spirits, giving me the motivation to fully participate in the hackathon. I spent the next two days coding intensely with my team, culminating in a project demo – an app designed to discreetly send a fake emergency text, providing an escape route from uncomfortable or potentially unsafe dates (college me would have loved this!).
The Interview Process and Unexpected Success
Weeks later, an email from Red Hat Early Talent Acquisition arrived, inviting me to video interviews for two different internship positions. I was ecstatic and immediately shared the news. Trying to temper my excitement, I repeated, “It’s just interview experience,” to manage expectations.
My interviews were scheduled for a Friday and the following Monday. My first interview, with my now-manager, was surprisingly enjoyable. She was approachable and engaging. The conversation focused on my bootcamp projects and GA experience. She explained Red Hat and OpenShift. There were no technical coding questions. The second interview, with another manager, was equally positive, focusing on problem-solving approaches rather than coding specifics.
Then, I waited. Prepared for another rejection, I continued applying for other roles. I even reached the final on-site interview stage with a small web consulting firm outside the city. They offered me a position. While the salary was lower than ideal and the commute was a factor, I was ready to accept, eager to end the job search. I requested a few days to consider.
The very next day, an email from Red Hat arrived – an internship offer for the OpenShift Engineering team! Suddenly, I had two offers. Choosing Red Hat was an easy decision, despite the internship’s temporary nature. I felt it offered better long-term career potential. My boyfriend generously agreed to continue supporting me financially until the internship started. I accepted the Red Hat offer and respectfully declined the other.
In total, I applied to roughly 80 jobs between December 16th and February 20th. I heard back from only 9. Of those 9, 4 led to on-site interviews, and ultimately, 2 resulted in job offers.
Landing the Red Hat internship felt incredibly fortunate. I don’t believe I possess any extraordinary talent; I simply followed the advice of my career coaches and persevered. My hope is to continue at Red Hat beyond the internship, which requires continued hard work and skill development. Sharing my story is meant to show that a career pivot into coding bootcamp is achievable. If you’re considering a change, or struggling in your tech job search, take encouragement from my journey. I’m not a prodigy, just someone who put in the effort. If I can do it, you likely can too.
Frequently Asked Questions for Aspiring Tech Pivoters
“What’s your best advice for tech job seekers?”
Start with the basics: Google it! Seriously, online resources are abundant. Assuming you’re already crafting compelling cover letters and have a polished resume (critiqued by multiple sources), here are four tips that might give you an edge:
General Assembly: Would you recommend it?
Absolutely, especially the Boston location.
My experience is specific to GA Boston. Curriculum, instructors, and staff vary across locations. If considering a different GA campus, visit, explore the curriculum, assess the local job market perception of GA graduates. However, I have no reason to believe other locations are inferior; I simply lack firsthand experience.
The teachers and staff at GA Boston were instrumental in my successful career pivot into coding bootcamp. (Maybe not impossible without them, but definitely far more challenging and time-consuming.)
Is a coding bootcamp the right path for me?
Many factors to consider. Finances are key: Is the bootcamp cost justifiable given your potential salary increase? For me, the projected salary jump covered the cost within a year. Explore if your current employer offers tuition reimbursement for bootcamps or might re-hire you in a tech role post-completion.
Consider your happiness. Why tech? Genuine interest, or just salary and perks? If you dislike debugging or constant learning, tech might not be fulfilling. Ensure it aligns with your interests or at least tolerability to avoid career misery. Technical backgrounds (e.g., mechanical engineering) might find software engineering a smoother transition. If you lack tech experience (like me), extensively explore free online resources before committing to a bootcamp.
Can I break into software engineering without a bootcamp?
Definitely! Many do. It requires self-discipline, time, and patience. Coding knowledge is largely accessible online for free. It’s a remarkably accessible field and a great hobby for skill development.
Am I smart enough for software engineering?
Probably, yes! Most of my ~30 bootcamp cohort successfully completed challenging projects. Traditional “smartness” (instant comprehension, effortless memorization) isn’t essential. Hard work and a passion for learning are more crucial.
Women especially question their aptitude. I did too, and sometimes still do. Societal conditioning often leads girls to believe they should be instantly good at everything. Struggles can lead to discouragement and avoidance of challenging fields like tech, contributing to the gender disparity. A crucial realization in my career pivot into coding bootcamp was: it’s okay to be wrong. Error codes are learning opportunities. You iterate, experiment, and find solutions.
How should I structure my job search time?
Personal schedules vary, but treat the job search like a full-time job: 8 hours a day, 40 hours a week.
Job search stagnant? What should I do differently? Give up?
Job search fatigue is real. If it’s been a month with no responses, resist the urge to quit. Job searching takes time. GA career coaches advised that immediate job offers post-bootcamp are rare. A 4-month average job search duration is typical. Prepare for potentially longer timelines, especially given current economic uncertainties. It’s a marathon, not a sprint. If your current approach isn’t yielding results, research alternative strategies and adapt.
Financial strain during a prolonged job search is tough. Consider part-time work for income and structure. Extra responsibility can boost productivity and reduce wasted time. However, ensure part-time work doesn’t detract from treating the job search as a primary focus, potentially lengthening the overall process.
What’s the interview process like?
Company-dependent. My Red Hat internship interview was video-based, focusing on project discussions, not live coding. Most other interviews involved coding challenges – take-home or whiteboard exercises (mostly “easy” LeetCode level).
Typical process: phone screening, take-home challenge, on-site interview, but variations exist.
Interview prep tips?
Code challenge practice. EVERY. DAY. LeetCode and Codewars are great resources. Master palindrome string checks.
YouTube interview practice videos can be helpful, but hands-on problem-solving is more effective. Use videos strategically: try solving the problem first, then consult the video for guidance if stuck, and compare approaches afterward.
Prepare for both “hard” technical questions and “soft” technical questions (e.g., “explain what happens when you google something?”).
Don’t neglect behavioral interview questions. Prepare stories illustrating teamwork, conflict resolution, etc. Practice responses to avoid nervousness-induced stumbles.
Do I need a portfolio?
Perhaps not with a computer science degree. But it helps. Especially for career pivot into coding bootcamp individuals lacking a CS degree, a portfolio is highly recommended (example: mine).
Unless you’re a UX/UI design expert, use a template. Paid templates are affordable (mine was $13 – less than a Boston cocktail, far more useful). Free templates are also readily available.
Thank you for reading my story. I hope my journey inspires you to consider a career pivot into coding bootcamp or encourages you during your own tech job search.
I plan to write a follow-up article on how well the bootcamp prepared me for my tech role. Follow me on social media for updates! So far, so good!
About Me
Beyond coding, I’m a video game enthusiast and self-proclaimed nerd, deeply immersed in the Star Wars fandom. I also enjoy makeup artistry, anime, and running. Sadly, no pets (landlord says no), but I live with my awesome boyfriend and a collection of plants.
