Senior Software Engineer - Risk

Based in Canada and headquartered in Toronto, Paramount Commerce is a fintech company focused on making payments simpler and more secure. We've been helping reshape online payments since the early 2000s, enabling people to pay directly from their bank accounts, without relying on credit cards or e-wallets.

As a proud member of Payments Canada, we're deeply connected to the evolving financial landscape, helping ensure our solutions remain compliant, reliable, and future ready. Security, risk management, and data integrity are at the core of everything we build, and we power payment solutions that are seamless, thoughtfully designed, and built to scale.

As we continue to grow our business across Canada and prepare for expansion into new markets, we're looking for curious, thoughtful, data driven individuals who enjoy directly solving complex problems themselves and pushing ideas from concept to execution, in a rapid iterative environment with highly capable peers. If you're excited about building the future of payments – and want to be part of a team that's shaping what's next – we'd love to hear from you.

We're on the lookout for a Senior Software Engineer to join our Risk Engineering Team. Our Risk team sits at the heart of our payments platform, responsible for protecting our customers from financial fraud, ensuring compliance with the regulatory bodies that oversee our financial partners, and making high confidence decisions in real time as money moves through the system. We're building the next generation of our risk platform: low‑latency orchestration + configurable rules + event‑driven auditability.

As a Senior Software Engineer on the Risk team, you'll help design and build the systems that analyze every transaction as it happens, validating bank accounts, screening for sanctions, detecting fraud, and identifying money laundering and layering patterns. This is complex, high impact work that blends distributed systems, data‑driven decision making, and deep levels of responsibility and ownership.

The systems you build won't just process data, they'll actively prevent financial crime, safeguard our platform, and enable secure, compliant payments at scale.

You’ll own meaningful parts of our real‑time risk platform end to end, from early ambiguity and technical design through implementation, deployment, and iteration. Your work will include:

• Risk Scoring & Orchestration: designing low‑latency systems end to end with parallel checks, strict timeouts, fail‑open behavior, and safe cancellation semantics
• Rule Engine Foundations: building configurable rules, evaluation strategies, test modes, and merchant specific logic
• Risk Signals & Checks: implementing name matching, sanctions and negative lists, third‑party fraud checks, and device/IP/location signals
• Event Pipelines & Audit Trails: ensuring reliable event production using patterns like outbox, with strong consistency and no silent drops
• Performance & Reliability: improving p95/p99 latency, handling back pressure, retries, idempotency, and hardening systems for production incidents
• Production Ownership: building and operating services (primarily Golang & Kubernetes based), adding observability that answers real questions, and sharing on‑call responsibility
• Collaboration & Influence: partnering closely with Product, Data, and Risk stakeholders to ship iteratively, mentor teammates, and drive thoughtful technical decisions
• AI‑Assisted Development: using AI tools to accelerate understanding and validate assumptions, while maintaining strong engineering judgment

• Golang + Kubernetes for real‑time services
• Postgres (CNPG) + Redis for low‑latency storage/caching
• Warp Stream (Kafka‑compatible) for event streaming + outbox/replay
• Big Query as the analytics warehouse (risk insights, reporting, model evaluation)
• Airbyte for ingestion/ELT into Big Query
• Observability:
  Grafana + Prometheus (+ tracing/logging)
• React + Microfront ends for self‑serve/configuration/investigation tools
• CI/CD and multi‑cloud (AWS/GCP)

• In your first 30‑60 days, you’ll ship a real production feature and take ownership of a subsystem with…