Sr. Engineering Team Lead - InfoSec

Unisoft International, Inc. dba Continuous is a company focused on building trust infrastructure for financial institutions. They are seeking a Senior Engineering Team Lead to take technical ownership of their IAM governance product, Permission Assist, ensuring high code quality and driving AI-centric workflows within the engineering team.

Responsibilities:

• You’ll join the Engineering team, reporting to our CTO
• 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
• You will build a culture where other engineers develop those same reflexes
• 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
• You will translate technical reality into language that drives confident decisions — without dumbing it down or drowning them in jargon
• You will use Paycom, our standard internal tooling, and the technologies baked into Permission Assist: SQL Server, NHibernate, ASP.NET MVC, Autofac, Quartz.NET, PostgreSQL, AWS, Docker, and a CQRS-lite / Result pattern architecture that is convention-enforced and well-documented
• Understand the codebase deeply enough to make decisions in it — not just read it
• 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
• 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
• Deliver a phased .NET migration strategy with a clear recommendation, risk assessment, and sequencing plan that the CTO and Engineering Manager can greenlight
• Be recognized by compliance officers and executives as a trusted technical voice — someone who explains complex decisions clearly and instills confidence
• Demonstrate that AI-centric workflows are producing meaningful velocity gains across the team, not just in your own work

Requirements:

• Brownfield .NET Fluency — You can read, reason about, and make consequential decisions in a complex, evolving .NET codebase without hand-holding. You understand the difference between legacy patterns worth preserving and technical debt worth retiring. Specifically, you are comfortable in C# and the broader .NET ecosystem and can work effectively in a codebase that spans .NET Framework conventions alongside modern practices
• System Design Ownership — You have made architecture-level decisions on a production system and lived with the consequences — not executed someone else's design. You think in tradeoffs, document your reasoning, and can defend your choices to a CTO or a skeptical auditor. You understand that architecture is not a diagram; it is a set of decisions that compound over time
• Security-First Engineering — XSS, SQL injection, auth bypass, and secrets management are not afterthoughts — they are reflexes baked into how you design and review code. You operate in a regulated environment where a security gap is not just a technical failure; it is a compliance and reputational event. You think about security before writing the first line of code
• AI Tool Fluency as a Daily Practice — You have shipped real work using Claude Code, GitHub Copilot, or equivalent AI coding tools — not experimented with them. You understand how to use AI assistance to accelerate delivery without eroding quality or introducing risk, and you can model this workflow for others. In a small, high-growth team, this is the multiplier that makes everything else possible
• Influence Through Mastery — You lead without org chart authority. Engineers align behind your technical direction because you earn that alignment through expertise, consistency, and the quality of your reasoning. You can direct and unblock teammates, set the standard through code reviews, and drive architectural decisions — all without a single direct report. You persuade through vision, not hierarchy
• Technical Communication Across Audiences — You translate architectural decisions and security posture into language that resonates with compliance officers, auditors, and executives. You don't simplify by removing accuracy; you simplify by removing noise. This skill is what makes the difference between a technical team that gets trusted and one that gets managed around
• Precision as a Practice — You build systems, reviews, and conventions that prevent errors rather than catching them after the fact. Every detail matters — not because you are perfectionistic, but because you understand that in a regulated financial services environment, the cost of a defect compounds. You hold yourself and others to a high bar without making that bar feel arbitrary
• Curiosity in Ambiguity — There is no senior architect above you telling you what the right answer is. The product is complex, the regulatory environment is nuanced, and the technology has history. You are energized — not paralyzed — by that ambiguity. You ask the right questions, form a point of view, and move