Why did you want to join Trilogy?
There were a couple of reasons for being interested in joining Trilogy for this role. One was the chance to really get back to solving hard technical problems without the burden of dealing with corporate politics and a lot of the noise that operates in a lot of companies.
The other big reason for being interested in joining Trilogy is the chance to work on true asynchronous remote work. I really wanted the opportunity to choose when I do high quality work, in the place that I want to do it.
What stands out to you about your workplace?
A lot of companies deal with a lot of politics. The best idea doesn't always win, and opinions are used over data. Trilogy is very rational and based on making the best idea win. Every week, I'm working on different things, learning new things and being challenged in a constructive way.
What's something you're working on right now?
We had a product that was built around 20 years ago. It was state of the art at the time it was built, but it was several million lines of code to solve problems that could be solved differently today.
So I had the opportunity to spend time understanding the critical features it delivered, and then imagine: how would I do this today? It was as if I was creating my own startup, innovating and solving that problem with no constraints. And often as the case in our role. I spent time actually building a proof of concept. So trying out some ideas, writing some code, proving certain ideas worked. And then I was able to write authoritatively about why this solution would work for building out an innovative and new approach to solving a problem that companies really do have.
What's your advice for someone who wants to follow in your footsteps?
I'd advise anybody as they're thinking about career choices to look first for challenge and then for challenge, and then for challenge. Because how you learn and how you acquire skills is driven by the opportunities you have to learn and solve hard problems and get things done.