From Geology to QA: An Unexpected Journey
How years of fieldwork in geology prepared me for a career in software quality assurance — more than I ever expected.
When people hear that I transitioned from geology to QA engineering, they usually ask: “How does that even make sense?”
It makes more sense than you’d think.
Observation is Everything
In geology, you spend years training your eye to notice things others miss — a subtle color change in rock, a fault line hidden beneath vegetation, a mineral inclusion the size of a grain of sand.
In QA, that same skill translates directly. You’re looking for the crack in the system, the edge case the developer didn’t think of, the sequence of clicks that breaks the UI in an unexpected way.
Documentation is Non-Negotiable
Field geologists write reports. Lots of them. Precise, detailed, reproducible reports. If your colleague can’t follow your field notes and reach the same outcrop, the notes are useless.
Good bug reports work the same way. Steps to reproduce, expected vs actual behavior, environment details. If a developer can’t reproduce the bug from your report, the report fails.
Systems Thinking
Geology is fundamentally about understanding systems — how rocks form, deform, erode, and interact over millions of years. Nothing happens in isolation.
Software is the same. A change in one API endpoint can cascade into failures three layers deep. Understanding systems — holding the whole in mind while examining the parts — is the core skill.
What I Bring from the Field
I’m still a geologist in the way I think. Patient, methodical, curious. I just work with software instead of rock now.
And honestly? I miss the field sometimes. But I don’t miss the dust.