Product / Domain Engineer — Fintech

Interview process

After application review and an intro call, shortlisted candidates join three 90-minute onsite working sessions on separate days within one week at our Montréal office:Ideation (product concept, presentation and UI designs),Specifications (PRD, issues/subissues and acceptance criteria), andWorking prototype (one end-to-end flow using our provided hackathon stack and agents).

Each session includes discussion and review within the 90 minutes. Total practical assessment time is 4.5 hours, with no required homework between sessions. We provide tools, documentation, agent access and synthetic data. Expectations are adapted to the role and level; prior SweetOS knowledge is not required. We send the full guide and agree dates after the intro call. Sessions take place at our Montréal office. Please discuss scheduling or accessibility needs with us in advance. Travel, accommodation and relocation expenses are not covered.

Location: Fintech Station — SweetTech Suite, 4 Place Ville-Marie, Suite 300, Montréal, QC H3B2E7.Build reusable financial products with lasting value

SweetTech builds financial applications on SweetOS, our platform of shared capabilities. We are looking for a Product / Domain Engineer to turn important business capabilities into dependable products that can be reused across customer deployments and developed as products in their own right.

How we build applications

You will work through SweetTech’s autonomous agentic development systems. These systems carry out implementation; your primary responsibility is to define intent, understand the application architecture, direct the agents, and validate the result rather than write application code directly.

SweetOS provides reusable building blocks for assembling applications repeatedly. A capability developed for one application can be made available to other applications through shared components and well-defined interfaces. You will learn how those building blocks fit together, how applications use shared capabilities, and where a change belongs so it can benefit more than one product.

This requires strong engineering judgment: break down requirements, specify behavior and constraints, understand data flows and permissions, review agent-generated changes, and verify correctness, security, and production readiness. You remain accountable for the outcome even when the systems perform the coding.

SweetTech has its own Software Development Life Cycle (SDLC) and Agentic Development Life Cycle. You will learn and follow these internal processes when defining work, directing autonomous agents, validating results, and delivering changes. Understanding our architecture and working within these development lifecycles are core responsibilities of the role.

Your role

You will combine architectural and engineering judgment with deep ownership of a product domain, directing autonomous systems to perform implementation. Working with product stakeholders, customer-facing engineers, and platform engineers, you will define how a capability should behave, guide its agent-driven implementation, and improve it through real usage. Our product areas include digital signing, decisioning and workflow logic, and core financial capabilities.

What you will own

• Translate business concepts into clear domain models, rules, state transitions, APIs, and usable product experiences.

• Specify and direct autonomous agents to build and evolve reusable capabilities across products such as SweetSign, SweetLogic, and SweetCore, with a defined ownership area.

• Own correctness: specify invariants, edge cases, validation, audit trails, and failure behavior; turn them into meaningful automated tests.

• Orchestrate delivery of full-stack capabilities, from the interface and user workflow to services, persistence, and integration contracts, so other applications can reuse them.

• Work with forward deployed engineers to distinguish recurring product needs from customer-specific extensions and design appropriate reuse.

• Maintain versioned contracts, migration paths, documentation, and examples so other teams can adopt the product confidently.

• Use customer feedback and operational evidence to prioritize improvements, remove friction, and resolve production issues.

• Partner with platform engineers on identity, permissions, deployment, and observability while retaining ownership of the domain behavior.

What you bring

• Experience building and maintaining production software across frontend and backend components.

• Strong data modeling and API design skills, with attention to business rules, consistency, and maintainable boundaries.

• Ability to learn a complex domain, ask precise questions, and explain how requirements translate into software behavior.

• Practical experience testing edge cases, diagnosing production failures, and making changes without breaking existing users or integrations.

• Product judgment: balance usability, correctness, scope, and delivery speed while owning the result after release.

• Ability to work through autonomous development systems, including understanding application architecture, writing clear task specifications, reviewing generated changes, and independently verifying important behavior.

Helpful experience

Financial systems, ledgers or reconciliation, decision engines, rules and workflows, digital signatures, or products with strong auditability requirements. You do not need experience in every product area; evidence of learning a demanding domain and delivering reliable software matters.

What success looks like

Your product has clear behavior, tested business rules, and a usable interface. Multiple deployments can reuse it without divergent implementations. Customers and engineers can understand its contracts, diagnose failures, and upgrade safely. Product improvements are guided by adoption, quality, and measurable customer value.

Equity participation

Proposed total stock option grant:18,000–26,000 options, vesting over four years with a one-year cliff. This is a total grant, not an annual award or an ownership percentage. The final grant is subject to board approval, confirmation of the applicable share basis, and the company’s equity plan and grant terms.

On-the-job training

Our on-the-job training program covers SweetTech’s internal processes, Software Development Life Cycle (SDLC), Agentic Development Life Cycle, agentic technology stack, and SweetOS operations. You will learn how to work with our autonomous development systems, navigate the application architecture, compose and reuse building blocks, and follow our workflows for validating and delivering changes.

Training includes guided work on real tasks, feedback from experienced team members, and practical learning in operating and troubleshooting SweetOS applications. Responsibilities will grow with your demonstrated understanding and readiness. Prior knowledge of SweetTech’s internal systems is not required.

Working at SweetTech

Full-time, on-site in Montréal. You must be authorized to work in Canada; visa sponsorship is not available. We value hands-on problem solving, learning, clear communication, and ownership from implementation through production.

Apply

Share your résumé and an example of a product or complex business capability you built. Explain the domain rules, your contribution, a difficult trade-off, and how you tested correctness and measured the outcome. Public code is welcome, but a clear description of confidential work is equally useful.