Solutions Engineer
Job description
About the role
This role partners with enterprise sales to translate complex regulatory requirements into clear product narratives and live demonstrations for financial services clients. You will act as a trusted technical advisor, bridging gaps between customer needs and CUBE's compliance automation capabilities. The position operates across discovery, design, and collaborative validation to support compelling, evidence-based sales engagement.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
You engage prospects to understand business requirements and regulatory use cases, ensuring solutions address real compliance and risk management needs. You deliver tailored product demonstrations that highlight how CUBE's SaaS platform tackles specific financial services workflows. You design and present proof-of-concept scenarios that reflect client environments and demonstrate tangible value. You serve as a technical point of contact throughout the sales cycle, clarifying capabilities and managing expectations.
Requirements
You bring 5 or more years of experience in solutions, pre-sales, sales engineering, or compliance advisory roles focused on regulatory and compliance products within financial services. You demonstrate a strong understanding of financial services operations, regulatory workflows, and the systems that support compliance and risk management. You show familiarity with RegTech platforms used for compliance automation, surveillance, and risk management. You communicate effectively with both technical and non-technical audiences, adapting your language to match stakeholder priorities. You lead discovery sessions that clarify needs, articulate value, and highlight return on investment for prospective clients.
Practical notes
This role is hybrid and based in Toronto. You will work across EMEA, the Americas, and APAC as part of a globally distributed RegTech team. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
The role focuses on customer-facing technical sales within a regulated industry. Success depends on deep product knowledge, structured discovery, and collaborative solution design. The team leverages AI-powered SaaS tools to simplify complex compliance challenges for financial institutions. Continuous learning about regulations and technology trends is essential. The position supports enterprise sales cycles that involve cross-functional collaboration with product and engineering.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.