For anyone meeting you for the first time, how do you explain what a solutions engineer does?
Solutions engineering is actually very similar to what Batman does.
On the front end, when someone needs help, whether it’s a sales executive or a customer, we show up and get involved. That might mean showcasing features, answering questions, or working through what a solution could look like in practice.
On the back end, there’s a lot of internal support. We help colleagues feel confident navigating demo environments and sandboxes, and we support them with technical questions as they come up.
At its core, the role is about acting as a trusted advisor. If someone asks a question about Canvas, my job is to guide them to the most accurate answer in the shortest amount of time. There’s also an important, less visible part of the role, helping people across the business understand the product and feel confident talking about it.
What drew you to solutions engineering, and what’s kept you in it?
I didn’t start out in education technology. I studied culinary arts and spent several years working as a chef, including time in Michelin-star kitchens in Hong Kong and later in Melbourne. It was intense work, and eventually I realised it wasn’t the right long-term fit.
When I returned to the Philippines, I did some self-reflection and came back to something I’d always wanted to do when I was younger, teaching. I started teaching English on the side, mainly to Korean and other Asian students, and that experience stayed with me.
I went on to complete a master’s degree in communication, which was mostly sales. Looking back, I find that pretty funny, because I’ve never actually been part of a sales team. At the time, none of my steps seemed to point directly to what I’m doing now, but somehow everything fell into place.
Throughout that journey, Canvas kept appearing in different ways. Working at Instructure became something I kept coming back to, and when I eventually joined the team, everything clicked.
When you join a first conversation with a school or institution, what are you listening for beneath the surface?
The first thing I listen for is pain points. Across Asia-Pacific, institutions often have similar requirements, whether they’re in Singapore, Malaysia, or the Philippines. What really differs is what they’re struggling with day to day.
Before a call, I’ll usually check in with the account executive to see if there are specific challenges the institution has already raised. If it’s not clear, I’ll ask directly. Coming from an education background helps shape what I show and how I approach the conversation.
I also prefer demos to feel more like discussions. Rather than running through everything, I focus on listening and responding. This approach works particularly well in developing markets, where institutions may still be working out what they want from an LMS. Often, simple questions lead to stories, and those stories tell you what really matters.
What’s a common challenge you see organisations facing with learning technology right now?
In many parts of Asia, the challenge is less about tools and more about mindset. Education can be very traditional, and one of the biggest hurdles is faculty buy-in, not just to an LMS, but to edtech more broadly.
When people are comfortable with familiar ways of working, change can feel unnecessary or disruptive. A big part of the challenge is helping institutions break down those barriers and ensure everyone can use these tools effectively, regardless of their comfort level with technology.
What’s one misconception people often have when they’re exploring an LMS?
A common misconception is that an LMS replaces the classroom. Many educators strongly believe in the value of face-to-face learning, and they’re not wrong.
An LMS isn’t there to replace that experience, it’s there to enhance it. Learning doesn’t only happen inside the classroom. It can happen anywhere, whether that’s on a commute, at home, or in remote areas with limited connectivity.
The LMS supports that kind of learning, making it more accessible, while the classroom experience still remains important.
What’s been one of the most memorable customer moments you’ve had in this role?
I really enjoy field marketing events like EduTECH and CanvasCon. They help solutions engineers stay grounded by giving us the chance to talk directly with customers about their experiences.
Those conversations are valuable. Customers will share what they’re struggling with, and that opens the door to showing them solutions they might not have realised were possible. It’s also a valuable way to gather feedback and strengthen long-term relationships.
What’s a Canvas capability you genuinely love showing, and why?
That’s changed over time.
When I first joined Instructure, it was the rich content editor. When I was building modules as an educator, I didn’t have HTML knowledge, and Canvas made it possible to create content without that technical barrier. That ease of use really stood out, especially for educators without an IT background.
More recently, I’ve been exploring newer AI capabilities. Seeing how these tools can support content creation and save time has been really useful, and there’s a lot of potential in how they’ll continue to evolve.
What’s one practical piece of advice you’d give to a team preparing for an LMS change?
Changing an LMS is a long-term relationship.
There will be moments where people compare the new system to the old one, and that’s natural. What’s important is remembering why the change is happening in the first place.
It takes time, effort, and commitment from everyone involved. Not everything transfers instantly, and that’s okay. With the right support and patience, things start to click and progress builds from there.
What’s a small detail about your job that most people don’t realise?
A lot of preparation happens before a customer call ever starts. We’re encouraged to take time beforehand to research the institution, understand their context, and think through whether Canvas is actually the right fit for their needs.
Another less visible part of the role is adapting how we communicate. I work with organisations across K–12, higher education, and vocational education, and the language we use matters. Choosing the right terminology shows we’ve done our homework and understand who we’re speaking with.
What’s the best piece of advice you’ve received?
Rather than one specific piece of advice, it’s the mentoring I’ve received since joining Instructure that’s made the biggest difference.
Having support that helped me connect everything I’d learned in previous roles and apply it here has been incredibly valuable. This role feels like a culmination of my experiences in education and edtech.
If your job had a theme song, what would it be?
Backstreet Boys, I Want It That Way.
Every customer comes into a conversation looking for something specific. That “tell me why” question is at the heart of what we do as solutions engineers, understanding why Canvas is the right fit for their needs.
It’s cheesy, but it works.