Q&A: Dr Harrison Steel

Anyway, after that I worked for a while, and was then fortunate enough to get one of the General Sir John Monash Scholarships (an Australian foundation) to go overseas to do a PhD. This led me to Oxford, which I aimed for on the basis that there were people doing excellent research, and I would also have the opportunity to do plenty music (choir!) and sports (athletics!) during my time there. I’ve been there since, as a PhD student, post-doc, and now academic. 

What has been your biggest achievement to date?

One thing I’ve been very proud of over the last several years is building a research team that brings together people from many different backgrounds – both personal backgrounds, as well as their areas of study and expertise. We have people from engineering, biology, math, computer science, and several other fields working together to create new technologies which (we hope) will go on to help with some of the big challenges in healthcare and climate change. I’m looking forward to all the things we’ll achieve together in the future! 

What is your favourite thing about being an engineer? 

On the flip side of the last question, I do really like the technical work. Whether this is putting something together in the lab, designing a circuit, or writing code, I can happily do that for hours. In many ways, these things come back to that video game experience I mentioned – you have some goal and your challenge is to combine different approaches that previous engineers have developed (and make new ones where they are missing) to come up with a solution! 

What does a typical day involve for you? 

Since 2020 I’ve been an associate professor which – in short – means I spend my day doing a complete mixture of random tasks. This can range from working in a laboratory building things, to applying for grants and administration, to leading a team of other engineers and helping them build their own careers. This might sound a little strange, since you would imagine an engineer would spend most of their time doing “technical” engineering, but in practice, a huge amount of it is organisational and people skills.  

This is tricky in many ways, not least because you spend most of your training doing technical work and then need to transition to a more leadership-oriented role. But, it does mean you get to learn about a huge variety of different topics, and (at least in the academic setting) have a fair amount of choice over what problem/s you pick to work on. 

What would be your advice to young people looking to pursue a career in engineering? 

First would be to not wait for permission or the perfect timing to do things you are interested in. Often this is referred to “agency” – the ability and willpower to have an idea and then follow it through. So, if you want to make an app, go find a basic tutorial for the simplest possible approach, and start trying to code it! Or if you want to make some physical thing but don’t have the parts or tools you need, go find the email (or LinkedIn) of someone that might and send them a message saying you are an interested young person and ask if they would help you. Pestering people (politely) on the internet is a great way to get things done in the modern world.   

Building on this idea, my second piece of advice would be to get comfortable with not knowing what you are doing. I am constantly searching questions on Google, or talking with an AI Assistant, often asking very simple questions that I probably learned the answer to in high school but subsequently forgot. Anyone who is working on anything particularly ambitious will have to constant operate in this zone of continual ignorance (and learning). Alongside perseverance this is the only “secret tool” you need to make that app or engineering idea mentioned above!

What’s next for you? 

A book and a cup of tea, I have probably talked too much already!