Before: The Comfortable Cage
I spent twelve years as a geologist in the oil and gas industry. From the surface, it was a great career. I made good money—after bonuses and stock, I was clearing $180K per year. I had a company truck, an annual bonus that usually came through, perks that made life comfortable. I was good at the work. I understood reservoir geology at a level that took years to develop. My colleagues respected my opinions. I was advancing. There was a clear path to a senior geologist role or a technical director position if I wanted it. Everything suggested I should keep going.
But there was the anxiety. Underneath the comfort, there was a constant low-level fear. It was the boom-bust fear that everyone in energy understands. In 2014, oil was $100+ per barrel. Everything felt stable. Then 2015 hit and oil crashed to $40. Suddenly there were layoffs. Friends and colleagues were let go. Some of them had mortgages and families and suddenly no income. I survived that round of cuts. But the fear was baked in.
Then the brief recovery, and then 2020 and the COVID crash. Another wave of layoffs. This time I felt it personally. The company I'd been with for eight years made cuts. I kept my job, but friends were gone. The message was clear: no amount of seniority guaranteed security. A combination of circumstances—an oil price drop, a global pandemic, corporate restructuring—and your career could implode. It had happened three times in twelve years. Every major crisis, there were massive energy industry layoffs.
The other thing was the knowledge that the ceiling was getting lower. The industry wasn't growing the way it had been. The days of rapid advancement seemed over. There were too many talented people competing for fewer senior positions. The salary was good, but the trajectory felt constrained. I could make $180K per year for the next 20 years, or I could try something else.
I had a golden handcuffs situation. The salary was high enough that it was hard to leave—leaving meant a massive pay cut. But the security was lower than the salary suggested. I was making good money doing work I was competent at, for a company in an industry that was not growing. Sunday nights were rough. I'd think about the upcoming week and feel dread. Not excitement. Not engagement. Dread. That was the sign that something had to change.
The Decision Point: Why Jump at This Particular Moment
The specific catalyst was conversation with my friend who'd transitioned into software development. She'd done a bootcamp three years prior, and now she was a software engineer at a Calgary startup. She loved her job. She talked about the problems she was solving, the people she was working with, the fact that the skills she was learning were getting more valuable every year, not less valuable. She made less than I did, but she wasn't stressed about her industry disappearing. She wasn't anxious about layoffs. She was building things that people used. She had excitement on Sunday nights instead of dread.
I asked her about the transition. How hard was it? She said it was hard, but the hardness was the good kind of hard—challenge and growth, not anxiety and uncertainty. She said the first month of the bootcamp felt like she was drowning. By month three, things started clicking. By month twelve of her first job, she felt competent. By year two, she was thinking about technical problems clearly. She recommended the bootcamp. She said the community was supportive. She said there were other people doing the transition from energy to tech.
I did the arithmetic. The bootcamp was $12,000 and 12 weeks. I had savings from the high salary. I could afford to do it. If I started a junior dev job at $70-80K (best case), I'd be taking about a 60% pay cut. That was significant. But I was also losing the anxiety. I was joining an industry that was growing, not declining. I was learning skills that appreciated over time, not depreciated. And I was 38 years old. If I was going to make a career change, this was the time. In ten years, it would be harder.
After: The First Year Was Brutal
I applied to Lighthouse Labs Calgary in the spring. I got in. I quit my geology job in the spring and started the bootcamp in June. The first week was disorienting. I was surrounded by 30 other people trying to learn programming. Most of them were younger than me—early twenties, fresh out of high school or a college degree. A few were career-switchers like me. The instructors were young engineers from Calgary's tech scene. The instruction was fast, practical, and assumed you could learn quickly.
I was terrified. I'd been an expert in my field. I'd published papers. I'd been called in to consult on big projects. Now I was the person in the room who didn't know what an array was. Who had to Google JavaScript syntax every five minutes. Who made stupid mistakes on assignments. The humiliation was real. I'd spent twelve years building expertise and I was starting from zero.
The hardest part was imposter syndrome on steroids. Every day I felt like I was in over my head. I'd see classmates writing code smoothly and think, "They understand this, I don't. Maybe I'm not built for this." I'd go home and spend extra hours trying to understand concepts. I'd lie awake thinking about whether I'd made a huge mistake. I'd spent twelve years building one kind of expertise and I was throwing it away to be a beginner again.
But something shifted around week five. I started being able to write code that worked. Not perfect code, but code that did what I intended. The concepts that had been opaque started making sense. I realized that programming is a skill that develops with practice like any other skill. I was not stupid. I was just inexperienced. There's a massive difference.
The bootcamp was twelve weeks. By week ten, I'd started getting job interviews. By week twelve, I had three offers. The highest was $72K at a Calgary SaaS company. I took it. Suddenly, I was a junior developer making $72K, down from $180K as a senior geologist. It was a huge financial cut. Financially, I was fine because I had savings and no debt. But psychologically, it was shocking to walk into a role where I was entry-level, where my paycheck had been cut by more than half, where I had to ask basic questions.
Months 1-6 as a Junior Developer: Incompetence as a Feature
The first six months of my first developer job were the hardest. I was incompetent at everything. Code review was humbling. I'd write code that I thought was fine and my senior engineers would make suggestions that showed me I didn't understand something fundamental. I'd spend an hour fixing a bug that a senior engineer could fix in five minutes. I'd ask questions that made me feel stupid. Why does this variable undefined instead of null? How do I debug this? What's the difference between synchronous and asynchronous?
My salary was $72K. I was making less than I'd been making in geology. But I was also learning faster than I'd learned anything before. Every day I was learning. Every day I was slightly less incompetent. The trajectory was steep upward. As a senior geologist, the trajectory had been flat. I wasn't learning new things; I was just applying the same knowledge in new contexts. As a junior developer, the trajectory was nearly vertical.
The paycheck mattered less than I thought it would. Yes, I was making significantly less. But I'd prepared for it financially. I had savings. I didn't need to make six figures. I needed to make enough, and $72K in Calgary, in a modest lifestyle, was enough. The reduction in financial stress was more than offset by the reduction in industry anxiety. I wasn't lying awake thinking about oil prices. I wasn't anxious about layoffs. I was anxious about being incompetent at my job, but that's an anxiety with a path to resolution. You learn. You get better. You become competent.
Months 6-18: The Inflection Point
Around month six, something shifted. I started understanding not just individual concepts, but how they fit together. I could read code and understand the logic flow. I could write code that didn't just work, but was readable and maintainable. I could anticipate problems. I understood the tools. By month 12, I was being assigned more complex projects. I was mentoring one of the other junior developers on the team. By month 18, I felt competent. Not expert, but competent.
The senior engineer who'd been my main mentor told me, around month 14, that my geology background was becoming visible in my work. I was thinking about systems in sophisticated ways. When we were discussing database architecture, I was asking the right questions about constraints and trade-offs. When we were thinking about how to scale our systems, I was understanding the underlying principles. The geology wasn't directly relevant, but the thinking pattern—how to model complex systems—was visible.
At month 18, the company gave me a raise. $82K. It wasn't huge, but it was recognition that my value was increasing. I was no longer entry-level. I was a mid-junior developer, capable of working more independently. I was still making less than I'd made in geology, but the gap was closing. And importantly, I wasn't worried about it closing. I could see the trajectory. If I stayed on course, in five years I'd be making $130-150K. Not $180K, but close. And I'd have built a career in a growing field, not a declining one.
Year Two: Building Skills, Building Confidence
By year two, the imposter syndrome had largely faded. I'd shipped real features. I'd debugged production issues. I'd written code that people used. I'd made mistakes and learned from them. The competence was real, not imagined. I was thinking about technical problems in sophisticated ways. I was contributing meaningfully to team discussions about architecture and design.
The financial reality of the career change was clear by then. I was making $82K. I wasn't making anywhere near the $180K I'd made in geology. But I also wasn't anxious. I wasn't worried that an oil price drop would end my career. I wasn't worried about layoffs (tech companies do layoffs, but not with the same cyclical certainty as energy). I wasn't dreading Sundays. I was excited to go to work.
The skills I'd built in geology had become infrastructure. They were invisible because they were baked into how I thought. The geological thinking—how to model complex systems, how to work with data, how to understand constraints—was shaping how I approached software problems. And the software skills were real. I could write complex features. I could debug systems. I could understand other people's code. I was a developer.
What Geology Skills Translated
Data analysis: Geologists live and die by data analysis. I'd been processing and analyzing data for twelve years. That translated directly into data engineering and data analysis work in software. I understood how to think about data quality, data sources, data relationships. That was rare in junior developers who'd never worked with real data at scale.
System thinking: Geology is about understanding complex interconnected systems—how rocks relate, how fluids move, how time changes things. That's directly analogous to understanding software systems—how components relate, how data flows, how systems behave over time. The domain is different, but the thinking pattern is the same.
Project management: I'd managed complex projects in geology. I understood how to coordinate across teams, how to manage stakeholders with competing priorities, how to handle unexpected problems. That showed up in how I worked on team projects. I understood scheduling and dependencies and risk management in a way that junior developers hadn't necessarily developed.
Domain expertise in energy: This is niche, but valuable. If a company is building software for the energy industry, having someone on the team who understands energy—who knows what geologists actually do, what engineers care about, what problems are worth solving—is powerful. That's a skill that's hard to hire for and takes years to develop.
What Didn't Translate (and What I Had to Learn)
Programming fundamentals: Geology has nothing to teach you about data structures, algorithms, programming languages, or the fundamentals of computer science. I had to learn all of that from scratch. It took months. And it was humbling because I'd spent twelve years as an expert and suddenly I was not an expert.
Modern software practices: The pace of change in software is dramatic. Frameworks and tools that were current five years ago are outdated now. Practices that are standard (version control, continuous integration, cloud deployment) are things I had to actively learn. Energy was slower moving; software moves fast.
Communication style: Software engineers communicate in specific ways. You write code comments, you participate in code review, you communicate in Slack, you write technical documentation. The tone and style are different from geology writing. It took me a few months to find my voice in the software environment.
The Financial Calculation That Actually Mattered
I made $180K as a geologist. I make $82K as a junior developer (after the first year raise). That's a $98K annual pay cut. That sounds devastating. But let's calculate the actual financial impact over time. As a geologist, my career probably had 15-20 years left. Maybe I'd make $180K for another 10 years and then face age discrimination and decline. Total earnings: roughly $1.8M over the next decade.
As a developer, I'm starting over. But the trajectory is different. I'm at $82K. In five years, with normal progression, I should be at $130-150K. By year ten, if I stay in tech and don't burn out, $170-200K. By year fifteen, if I remain active and engaged, probably $200K+. And critically: the industry is growing. There's no cliff edge. The oldest senior engineer at my company is still advancing. There's no age-out in tech the way there is in energy. I could work another 25 years and keep earning more. Total potential earnings: $2.5M+ over the next 15-20 years, if I stay the course.
The short-term pay cut is real. But the long-term financial picture is actually better. Plus, I don't have the anxiety. I can sleep at night. I'm not worried about oil prices. I'm not worried about layoffs. That's worth money. A lot of money. The peace of mind is probably worth $50K+ per year. So the financial trade-off is not nearly as bad as the surface number suggests.
What Made the Transition Possible
Savings: I had about 18 months of runway saved up. That was essential. If I'd had to survive paycheck to paycheck during the bootcamp and the junior dev period, I would have cracked. Having runway meant I could do the bootcamp, then take a junior dev job, then survive the low salary while I was learning.
Community: Lighthouse Labs Calgary has a great community. The instructors were supportive. The other bootcamp students were going through the same thing. The mentors connected you with people further along the path. That made a huge difference psychologically. I wasn't doing this alone.
Support system: I had a partner who was earning money and supportive of the transition. That mattered. If I'd been the sole income earner for a family, this would have been impossible. The financial math doesn't work if you have dependents and you're cutting your income by 60%.
Age: I was 38. I had enough experience and maturity to handle the humiliation of starting over. I had perspective. A 22-year-old making the same transition might have a much harder time psychologically because they haven't had success yet. I'd already succeeded; I was choosing to start over. That's a different mindset.
Company culture: The company I joined was genuinely supportive of junior developers. They had a mentorship program. They had space for learning. They didn't expect junior developers to be fully productive immediately. They expected learning curves. That made a huge difference. If I'd joined a company that threw me into the deep end, I would have struggled much more.
The Honest Cost That I Don't Regret
I took a $98K annual pay cut. Over two years, that's roughly $150K in lost income. I also had $12K in bootcamp tuition. So I paid about $160K (plus opportunity cost) to make this transition. That's not cheap. For most people, it's not an option. I was lucky to have the financial flexibility to do it.
The emotional cost was also real. I spent six months feeling incompetent and afraid. That's not pleasant. I spent a year thinking I'd made a huge mistake. I had days where I wanted to quit, go back to geology, get my high salary back, avoid the struggle. Those days were hard.
But the trade-off was clear: short-term pain for long-term gain. Short-term financial loss for long-term financial security and growth. Short-term humiliation for long-term competence and excitement. I'd make the same decision again. Without hesitation.
The Bridge: What I Wish I'd Known Earlier
If you're thinking about making this transition, understand that it's hard and it's possible. Hard like learning any new field is hard. Possible because people do it every month. There's no magic. You learn, you practice, you build projects, you apply for jobs, you get rejected, you interview, you get offers. It's a process.
The pay cut is real. Prepare for it financially. You need runway. At least six months of expenses saved up, ideally a year. If you don't have that, the stress of not having money will make learning harder. With financial runway, you can focus on learning instead of worrying about bills.
Find a mentor or a community. Bootcamps provide this, but if you're not doing a bootcamp, find an online community or a local meetup or someone who's been through the transition. The support matters. It makes the hard parts more bearable and the victories more meaningful.
Accept that you're going to be incompetent for a while. That's fine. Incompetence is the first step toward competence. You're not incompetent because you're stupid. You're incompetent because you're learning. That's exactly where you're supposed to be.
Choose your company carefully. Work culture matters more than you think. A supportive company with good mentorship will accelerate your learning dramatically. A toxic company will make everything harder. You can learn the technical skills anywhere, but you can learn them faster and happier with good people.
Where I Am Now
I'm two years into my development career. I'm making $82K. I'm competent at my job. I'm learning constantly but from a foundation of confidence instead of fear. I'm excited about work. I have options—if my company had layoffs, I'm confident I could get another job relatively quickly. The industry is growing and talent is scarce. I'm valuable. That's a feeling I didn't have in geology.
Will I make $180K again? Probably. Not this year, not next year. But in five or six years, if I keep learning and stay engaged, I probably will. And I'll be in an industry that's growing, not declining. I'll have job options and career momentum. I'll have peace of mind. The geometry career had a ceiling and it was getting lower. The software career has upside.
Would I do it again? Yes. In a heartbeat. The twelve years in geology weren't wasted—they shaped how I think and they're valuable infrastructure for my software work. But staying in geology for another fifteen years out of financial inertia would have been the real mistake. I took the short-term pain for long-term gain. And I don't regret it for a second.