Senior Lead Software Engineer, Full Stack (Bank Tech)

Key Responsibilities

• Own technical delivery on active engagements — writing production code, making architecture decisions, conducting code reviews, and building prototypes that meet acceptance criteria
• Lead a small team of engineers (2–5) through engagement delivery, setting technical direction and removing blockers
• Decompose complex, ambiguous problems into practical implementations with clear milestones
• Ensure quality across engagements: performance, testability, operability, and security
• Make pragmatic technology choices that balance engineering ideals with delivery timelines
• Rapidly onboard to unfamiliar codebases and domains, becoming productive in days rather than weeks

Relationship Building & Collaboration

• Build trusted working relationships with engineering managers, tech leads, and senior engineers on stakeholder teams
• Communicate progress, risks, and technical trade-offs clearly to both technical and non-technical stakeholders
• Partner with receiving teams during knowledge transfer to ensure clean handovers and long-term ownership
• Represent Solutions Engineering credibility through the quality of your work and your ability to earn trust quickly in new environments

Domain Breadth & Bank Context

• Develop working knowledge across Bank Tech's systems landscape: payments, account servicing, data platforms, core banking systems, and cloud infrastructure
• Apply growing institutional context to accelerate delivery — understanding regulatory constraints, deployment patterns, and operational realities
• Stay current on bank-wide technical initiatives and apply that context to engagement work

Mentorship & Engineering Culture

• Mentor engineers on your engagement teams, helping them grow technically and navigate the unique demands of a professional services model
• Contribute to a culture of engineering excellence, continuous learning, and knowledge sharing
• Lead by example through high-quality code, clear documentation, and principled technical decisions

Engagement Model

• Operate effectively in a SWAT-style model: rapidly orient to new problem domains, deliver high-impact work in compressed timelines, then transition cleanly to the next priority
• Typically own one primary engagement while contributing to a second
• Thrive with variety — this role serves multiple stakeholders across different domains rather than deep-diving into a single product for years