Mission — Why We Need You Sr. Engineering Team Lead — the title is straightforward. 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. You will be the technical backbone of Permission Assist, our flagship IAM governance product. This is a backfill and a growth play. The person before you helped build this foundation; you will take it further — hardening the architecture, elevating the team’s craft, and driving the AI-centric workflows that make a lean engineering team capable of punching well above its weight. You’ll report directly to the CTO and partner closely with our Engineering Manager to ensure the team succeeds both technically and professionally. Objectives — The Problems You’ll Solve You’ll 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. You will know it deeply enough to make defensible decisions about what to change, what to leave alone, and what to plan for migration. 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. XSS, SQL injection, auth bypass, and secrets management are not checklists; they are reflexes. You will build a culture where other engineers develop those same reflexes. 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. This isn’t experimentation; this is how we make a small, talented team capable of moving faster than our competitors. You will drive AI-centric workflows into critical business processes and help the team adopt practices that meaningfully expand what we can ship. 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. This is a differentiating skill in this role, and it matters as much as your code. You’ll partner closely with the Engineering Manager on team effectiveness — contributing to a culture where engineers have clear technical direction, know what good looks like, and have a trusted senior voice helping them grow. 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. 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 - 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 - 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 Competencies — What We’re Looking For 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. What’s In It For You? At Continuous, we practice what we preach — our total rewards reflect our commitment to our people: - A remote-first environment – Work from wherever you thrive in the contiguous U.S. - Everything you need to succeed – Mac or Dell laptop, $100/month connectivity stipend, monitors, and a $250 setup allowance - Comprehensive health coverage – 100% company-paid medical, dental, and vision for you and your family, plus $1,800 annual HSA contribution - Financial protection – 100% company-paid LTD, AD&D, and life insurance - True flexibility – Flexible PTO and working hours that respect your life outside of work - Time to recharge – 11 paid holidays plus two Wellness Days - Investment in your growth – $2,500 annual professional development stipend How We Work — Our Core Values Be Kind — We are kind and helpful. We care and act with empathy. We take care of ourselves, each other, and our customers. We understand boundaries. We believe clear is kind. We exhibit healthy behaviors and are self-aware. Be Authentic — We are genuine. We are real. No pretenses. We know ourselves and celebrate our differences of thoughts, ideas, and skills. We show our true self — our whole self — every day. We unlock our teams’ potential by unlocking our own and each other’s potential. There is only one you and we want to see YOU every day. Be Collaborative — We unite for a common cause. We are in pursuit of the best idea — not our own idea. As a remote company, we must collaborate and communicate to make a difference — an impact. We do this for our teams and for our customers. Be Determined — Giving up is not in our nature. We are smart people who solve tough problems. We have a bias toward action. We strive for great outcomes. We achieve our goals. We deliver success for customers, ourselves, and each other. Work Environment and Physical Requirements This is a remote position performed primarily in a home office setting. The role involves extended computer use and virtual collaboration. Occasional travel (up to 5%) for team gatherings, open enrollment events, or vendor meetings. EEO/AAP Statement Unisoft International, Inc. dba Continuous is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, pregnancy, genetic information, disability, status as a protected veteran, or any other protected category under applicable federal, state, and local laws. If you are an individual with a disability and require a reasonable accommodation to complete any part of the application process, or are limited in the ability or unable to access or use this online application process and need an alternative method for applying, you may contact 281-348-9606 or recruiting@smatechnologies.com for assistance. We will never ask you to send us money, perform a money transfers, or use Bitcoin during our hiring or onboarding process. If someone claiming to represent us requests money or a Bitcoin, it is a scam. Please report any suspicious activity immediately. We only post job openings through official channels and will never ask applicants to transfer funds.