My Career in Tech
My Career in Tech
My Career in Tech
Gerard Noseworthy
Gardiner Center TechPrep
July 12, 2024
12 YEARS IN TECH AS A BSC IN EARTH SCIENCES
DEVELOPER, CONSULTANT,
MANAGER
Background
PROFESSIONAL DIPLOMA IN WORKED PRIMARILY IN
GEOGRAPHIC INFORMATION HIGH SCIENCE
SYSTEMS ENVIRONMENTS.
Why Tech?
• I always enjoyed problem solving and
building things
• I did not learn to program until my diploma
program.
• I really enjoyed process automation brought it
to any repetitive workflow that I encountered
using Python.
How I got into Tech
• In my GIS program we had to do a capstone project which
we had to present our findings
• I wrote a Simple Decision Support System for avoiding
protected wildlife zones for mining roads
• There was a researcher who had funding for a geospatial
programmer, and I was the only one graduating that was
primarily showcasing programming skills
• Role was working with “big data” to generate climate sensitivity
Physical Scientist at statistics based on Canadian economic regions.
the Canadian • Got to work with IPCC Climate change models (AR4)
• Built a lot of databases, used those to create maps
Forestry Service (My • After 6 months there was a delay in funding so I had to find
first tech Job) another job
GIS Developer
at III
• I got hired as a software developer
• I started in a junior role working on a
decision support systems
• Involved lots of mathematical modelling
and using code to compensate for poor
input data quality.
• I once spent 6 weeks working on a tool, that
my boss completely rewrote overnight.
• Spent about 40% of my time working on
improving testing code coverage for a
longstanding project
GIS Developer at III Part 2
• The greatest benefit of III is that they encouraged professional
development
• Additionally, the projects were diverse, interesting and technically
complex.
JVPLabs
• Develop Cloud environment where researchers could work with
patient data in secure environment
Director of
Software at
JVPLabs
• Received a promotion to oversee team of
researchers, engineers and developers.
• Less time spent coding more time spent
putting together architectural diagrams,
dealing with input requirements, making
sure we were meeting quality goals and
putting procedures in place to ensure we
met FDA guidelines
Software Skills
Full Stack Scientific Embedded Geospatial Database
Version Control
Development Computation Systems Development Development
Cloud Native
Python Numpy, Scipy Firmware SQL Server Git
Geoprocessing
Data Segmentation
Mapbox
and Classification
Knowledge Domains
Unmanned
Information Systems Medical Devices
Autonomous Vehicles