Questrade interview questions

Finance · 5 questions · last reported Nov 2025
Report an interview →

Browse 5 Questrade interview questions for finance interview preparation. Questions in this collection are tagged for full-time, internship roles. Explore the topics and stages below and filter the collection to plan your practice.

Interview stages in this collection
Onsite
Practice topics
.NET (2), Architecture (2), Async (1), Backend (1), C# (1), CI/CD (1), Clean Architecture (1), Containers (1)

Questions come from candidate contributions and online research. Reports reflect past experiences and do not guarantee what Questrade will ask. Locked question details require points. Public examples below are free to read.

Read 3 free Questrade interview question examples

Browse all Questrade questions

5 questions

Free Questrade interview question examples

Read the full problem statements and use the links to revisit or share a specific example.

SOLID Basics

Easy · Onsite · Full-time

They asked me to explain the SOLID concepts during the technical interview. The round also covered clean architecture, previous work experience, and some C#, .NET, and Google Cloud Platform experience. It didn't feel like a heavy coding round, more like they wanted to see if I understood backend design basics. The process was pretty smooth and the technical questions were common ones.

Dockerfile Basics

Easy · Onsite · Internship

This was for a Software Engineering Intern interview, and the technical part was pretty light DevOps. They asked me foundational Docker and containerization stuff instead of anything advanced around Kubernetes or cloud orchestration. The clearest question was what the first line of a Dockerfile should be. The round also touched on basic environment setup and simple CI/CD understanding.

Promise Usage

Medium · Onsite · Full-time

One of the senior engineering questions was around JavaScript Promises. They wanted me to explain Promise-related behavior and when I'd use one option over another. It came up in the technical video call after the recruiter screen. The question wasn't really LeetCode, it was more about knowing JavaScript well enough to make practical choices.