About LTi Technology Solutions

LTi Technology Solutions is a leading provider of asset finance and leasing software, purpose-built for the financial services industry. Our flagship platform, ASPIRE, powers the full asset finance lifecycle, from origination and credit decisioning through portfolio management, billing, accounting, and end-of-term; for banks, captives, independent finance companies, and specialty lenders across North America and internationally.

Backed by private equity and in active growth mode, LTi is making the most significant platform investment in the company's history: a ground-up re-platform of ASPIRE onto a modern .NET and React architecture running on Microsoft Azure. Our customers manage billions of dollars in lease and loan portfolios on ASPIRE, and the next generation of the product will carry that mission-critical workload forward on a foundation built for scale, extensibility, and speed of delivery.

This is a rare opportunity to join a profitable, established software company at an inflection point, where foundational engineering investment will directly shape product strategy, customer outcomes, and competitive differentiation.

Position Summary

LTi is hiring a Senior Platform Engineer to build and own the cloud platform beneath the next-generation ASPIRE product. This is a greenfield Azure build: subscription and landing zone design, infrastructure as code, CI/CD, identity and secrets, observability, and the security controls a mission-critical financial services platform requires.

Reporting to the VP of Engineering, the Senior Platform Engineer works as part of a small senior team. Platform decisions and architecture decisions get made together rather than handed across a wall. This is an individual contributor role without direct reports.

You will write the Bicep or Terraform, build the pipelines, wire the telemetry, and set the security posture. The operating principle is that the platform is a product and its customers are the engineers who ship on it, so automation, self-service, and documentation matter more than gatekeeping. The ideal candidate has built this foundation before and knows which controls pay for themselves and which only add friction.

Essential Functions & Duties

Cloud Foundation & Infrastructure as Code

• Design and build the Azure foundation, including subscription and resource group topology, networking and private connectivity, environment tiers, and the isolation boundaries that support secure multi-tenancy
• Express all infrastructure as versioned, reviewable code in Bicep or Terraform, with reusable modules, environment parameterization, drift detection, and no click-ops path to production
• Stand up the managed Azure services the product depends on (App Service, Container Apps or AKS, Azure SQL, Service Bus, Key Vault, App Configuration, Storage, Redis, Front Door), making explicit managed-versus-self-run tradeoffs with the team
• Establish backup, restore, and disaster recovery for data and infrastructure, and prove the recovery path through scheduled exercises rather than documentation

CI/CD & Developer Experience

• Build CI/CD pipelines in Azure DevOps or GitHub Actions covering build, test, scanning, artifact management, environment promotion, progressive deployment, and automated rollback
• Help define PR quality gates, branching and release strategy, and database migration practice that let the team ship continuously without ceremony
• Partner on the local developer inner loop, including containerized dependencies, seed data, one-command environment setup, and fast test execution, so a new engineer can ship a meaningful change within their first week
• Provide ephemeral, on-demand environments so feature work, migration dry runs, and customer-facing demos do not queue behind a shared environment
• Extend LTi's AI-assisted development practices into platform work, including agentic workflows for pipeline, infrastructure, and operational tooling, leveraging LTi's existing Claude Code environment

Security & Compliance

• Own the security posture of the platform, including identity and access through Microsoft Entra ID, workload identity, least-privilege RBAC, secrets management in Key Vault, and certificate lifecycle
• Build security into the pipeline rather than after it, with SAST, dependency and container scanning, IaC scanning, secret detection, SBOM generation, and a defined triage and remediation path
• Implement software supply chain controls including artifact signing, provenance, base image management, and patch cadence
• Produce the evidence trail that customers, auditors, and SOC 2 style examinations require, including access reviews, change history, and log retention, and treat audit readiness as a continuous state rather than an annual scramble

Reliability & Observability

• Establish observability from day one, including structured logging, distributed tracing, metrics, and dashboards in Application Insights and Azure Monitor, with tenant-aware correlation across HTTP, messaging, and background jobs
• Define SLOs, alerting, and on-call practice for a platform carrying mission-critical lease and loan portfolios, tuning for signal rather than volume
• Lead incident response practice, including runbooks, escalation paths, and blameless postmortems that produce durable fixes
• Own performance and capacity work, including load and soak testing, scaling policy, noisy-neighbor mitigation, and cloud cost visibility and accountability by environment and tenant

Partnership & Practice

• Serve as the platform counterpart to the Principal Software Engineer, participating in architecture and design review so that deployability, security, and operability are settled early rather than discovered late
• Author and maintain runbooks, ADRs for platform decisions, and the standards by which infrastructure changes are reviewed
• Support the re-platform migration effort with the environments, pipelines, and operational tooling that repeatable customer cutovers and rollbacks require
• Raise the operational bar across the team through code review, pairing, and enablement, with the explicit goal of making the team independent of any single person