Sr. Engineering Team Lead - InfoSec

Mission — Why We Need You

The role is anything but. At Continuous, our engineers don’t just write code; they build the infrastructure of trust that financial institutions depend on to govern access, manage risk, and satisfy regulators. When that infrastructure is sound, our clients can do their jobs. When it isn’t, audits fail, access creeps, and reputations suffer. This role exists because we need someone who feels the weight of that responsibility and builds accordingly — someone who has taken ownership of a production system, made architectural decisions they couldn’t undo, and learned from both outcomes. At Continuous, we make complex simple for financial institutions — and we need someone who can do the same for our engineering team.

Objectives — The Problems You’ll Solve

• You will join the Engineering team, reporting to our CTO. Your mandate is technical ownership — not coordination, not oversight from a distance. You will be in the codebase every day, making decisions that matter and setting the standard that everyone else builds to.
• You own the architecture of Permission Assist. You own code quality. You own the decisions about where the platform goes technically, and you live with the consequences of those decisions.
• Permission Assist is your product. This is Continuous' core IAM governance platform — a brownfield .NET application operating in a regulated financial services environment across 30+ states. You will take full technical ownership of this system: its architecture, its health, its evolution.
• The biggest technical decision on the horizon is the phased evolution from .NET Framework 4.8 toward modern .NET — a migration strategy that requires thoughtful planning, not a rewrite-and-pray approach.
• Code quality is your gate. You will be the standard-bearer for how code gets written and reviewed at Continuous. That means establishing and enforcing conventions through pull request reviews that catch security vulnerabilities, correctness issues, and architectural drift — consistently, without becoming a bottleneck.
• AI-accelerated delivery is your multiplier. You will bring proven, daily fluency with AI coding tools — Claude Code, Copilot, or equivalent — and you will model what that workflow looks like for the rest of the team.
• Technical communication is your bridge. Permission Assist operates in a regulated environment. Compliance officers, auditors, and executives will ask you to explain architectural decisions, security posture, and risk tradeoffs. You will translate technical reality into language that drives confident decisions — without dumbing it down or drowning them in jargon.

How You’ll Get There

• In your first 6 weeks — Learn the system, earn the trust: Understand the codebase deeply enough to make decisions in it — not just read it. Permission Assist has history, patterns, and conventions that aren’t obvious from a first pass. You will map them, document your observations, and begin to develop a point of view on what’s healthy, what’s technical debt, and what’s intentional.
• Complete a structured audit of the Permission Assist architecture: identify the three to five areas of highest risk or drift from stated conventions. Build working relationships with the Engineering Manager, CTO, and engineering team; understand how decisions get made and where your voice will matter most. Establish your code review presence — begin reviewing PRs within the first two weeks and demonstrate that your feedback is consistent, fair, constructive, and fast. Set up your AI-assisted workflow within the codebase; identify the first opportunities to accelerate delivery with AI tooling.
• In your first 3 months — Take full ownership, establish the standard: You own Permission Assist. That ownership becomes visible in this window — through the quality of your decisions, the consistency of your reviews, and the degree to which the rest of the team begins to look to you as the technical authority. Deliver your first architectural recommendation to the CTO — a clear, defensible point of view on the most pressing technical decision facing the platform. Drive AI-assisted workflows into at least one critical business process, demonstrating measurable throughput improvement. Establish code review norms that the full team adopts; track reduction in rework and security issues surfacing post-merge. Begin partnering with the Engineering Manager to identify where individual engineers need technical mentorship and provide it.
• Within 9 Months — Mastery, Momentum, And Migration Strategy You are the technical lead for Permission Assist in every meaningful sense. Your architecture decisions are shaping the roadmap. Your code review culture has raised the floor for the entire team. And the most important strategic decision ahead — the migration path — has a plan that leadership can act on. Deliver a phased .NET migration strategy with a clear recommendation, risk assessment, and sequencing plan that the CTO and Engineering Manager can greenlight. Demonstrate that AI-centric workflows are producing meaningful velocity gains across the team, not just in your own work. Partner with the Engineering Manager so that every engineer on the team has clear technical direction, active mentorship, and a credible path to their next level.