When I joined Found as CTO 4.5 years ago, we had 3 engineers and a straightforward (read non existent) approach to levels. Today, with our engineering and data org hitting 35 folks and growing, our IC levels have evolved into something more structured - not because we love process, but because clarity helps our engineers understand how to grow, and helps us build the right team for our mission of making self-employment easier.
Our levels are hyper specific to Found, reflecting the unique challenges of building banking infrastructure for millions of self employed Americans, while still mapping to generalizable skill sets you’d find at any technology company. We’ve spent years refining these levels based on what actually matters for our work – building reliable financial systems, solving real problems for real people, and scaling a platform that handles billions of dollars in transactions. The framework isn’t perfect, but its honest about what we value and how we evaluate growth.
Our Philosophy: Conservative, transparent, and impact-focused
We treat levels as conservative, lagging indicators of performance. This means you need to demonstrate sustained performance at the next level before promotion, not just show potential. Some engineers find this frustrating initially, especially those coming from companies with more aggressive promotion cycles. But we've seen how premature promotions hurt both the individual and the team—setting people up for stress and potential failure rather than sustainable success.
We've chosen radical transparency with our level framework internally. Every engineer can see the exact criteria for every level, understand where they stand, and know what's needed to grow.
Four Dimensions that Matter
We evaluate engineers across four key areas, with the weight shifting as you progress:
Craft isn't just about writing clean code—it's understanding the difference between a solution that works and one that will scale with us. At junior levels, craft means following our patterns and writing maintainable code. At senior levels, it means defining those patterns and making architectural decisions that will serve us for years.
Impact & Execution evolves from "shipped the feature" to "transformed how we serve customers." Early-career engineers demonstrate impact by reliably delivering their assigned work. Senior engineers identify problems we didn't know we had and build solutions that unlock new possibilities for the business.
Collaboration matters at every level because building financial products is inherently cross-functional. Junior engineers collaborate within their team; senior engineers work across engineering, product, risk, compliance, and directly with banking partners. Our best engineers make everyone around them better.
Hiring & Growth becomes increasingly important at higher levels. L3s participate in interviews and mentor interns. L5s shape our hiring process and build programs that accelerate team growth. This isn't about management—it's about multiplicative impact through people.
The Evolution Path (isn’t always linear)
Not everyone needs to climb to L6, and that's completely fine. Some of our best engineers have found their sweet spot at L3 or L4, becoming deep experts in specific areas like payment processing or tax calculations. We've designed our compensation bands so you can have a successful, well-rewarded career without chasing the next level.
We also recognize that growth isn't always upward. Engineers might take on stretch projects that don't work out, or step back to focus on craft after a period of heavy leadership. Our levels support these movements because real careers aren't straight lines.
Some engineers also choose the manager track. This is a lateral move, not a promotion. Our EM and IC tracks have equivalent levels and compensation. The skills are different, not better, not worse.
Summary | Craft | Impact & Execution | Collaboration | Hiring & Growth | |
L1 | Owns individual tasks and contributes to team execution through defined responsibilities and collaboration. | My code is free of obvious bugs and clearly structured. I can read, understand, and debug code that I didn't originally write. I am able to unblock myself, either independently or with guidance from another engineer. | I execute on clearly defined tasks and designs assigned to me. I ask questions proactively and incorporate feedback effectively. | I adopt team processes and practices that help my team operate smoothly. | I actively seek learning opportunities and contribute to my professional growth. |
L2 | Owns complete features, independently delivering quality code and actively engaging in product definition and team practices. | I effectively contribute to a large, existing codebase, debugging and extending code from others. I demonstrate strong familiarity with the common patterns and libraries in my programming ecosystem. I can independently break problems into smaller tasks and develop code with clear separation of concerns. I document systems and features clearly and retroactively when needed. | I own the delivery of complete features, balancing timely shipping with quality. I proactively communicate project progress, potential risks, and necessary tradeoffs clearly. I ensure the successful rollout of the feature I develop by responding to issues as they come up. | I partner effectively with product and design to define and scope new features. I collaborate closely with my team on technical approaches, ensuring realistic timelines and task breakdowns. I contribute to the team culture, supporting a collaborative and inclusive environment. | I actively participate in the interview process and represent our company positively to candidates. I proactively seek feedback and work on identified areas for personal and professional growth. |
L3 | Owns significant areas of product functionality, drives technical excellence, and contributes strategically to team and organizational goals. | I deliver high-quality, well-tested, maintainable, and performant code that anticipates potential failure domains. I proactively document complex systems and features clearly for cross-functional stakeholders. | I independently roll out substantial features, proactively address risks, and follow through on the impact of my work (such as by reviewing user sessions, building and maintaining reporting / dashboards / alerting, reviewing amplitude dashboards, and iterating based on real-world feedback). I identify and clearly articulate tradeoffs, influencing product and technical decisions. | I mentor junior engineers primarily through code reviews, pairing, and sharing best practices. I help teammates learn how to approach problems, offering frameworks or guiding questions. In lieu of opportunities to provide structured mentorship, I consistently and willingly support my peers. I proactively solve team-level technical and process issues, enabling faster and more efficient execution. I advocate for improvements to team culture and processes, ensuring inclusive collaboration. I communicate my team’s goals and technical strategy clearly to peers and stakeholders. I help break down well-scoped problems into smaller, tractable tasks for myself and teammates. | I regularly participate in interviewing when opportunities arise and represent Found positively. (Expectation is about quality, not frequency.) I support the growth of my teammates through tech talks, and pair programming. I continuously seek and act upon constructive feedback from peers and leadership. |
L4 | Owns complex, cross-team initiatives, drives proactive ownership and mentors others in tackling complex problems, and influences strategic technical direction. | I architect and define high-level system designs that achieve our strategic roadmap. I address cross-system technical issues efficiently, demonstrating deep expertise in our stack. I maintain and continuously raise our engineering quality bar, identifying common pitfalls and advocating effective solutions. | I own complex, multi-team spanning initiatives (e.g., KYB across Risk and GP, check access). I deliver execution impact (ensuring complex projects are delivered reliably) and also shape roadmap influence (helping define technical direction). Follow-through and proactive ownership are key differentiators: I carry initiatives end-to-end, anticipate blockers, and ensure adoption and iteration. I identify, prioritize, and drive initiatives based on their measurable impact on company goals, consistently seeing tedious and challenging tasks through to completion. I refine and scale team strategies, ensuring they align clearly with broader organizational priorities and are communicated effectively. | I mentor engineers beyond code reviews and RFC feedback by: - Helping others break down large, ambiguous, cross-team problems into tractable pieces. - Teaching teammates approaches for completing complex work. Cross-team mentorship is valuable but not always available; consistent impactful mentorship within and across immediate teams is the baseline. I foster mentorship culture within the team, actively supporting teammates’ career growth. I identify and proactively address organizational bottlenecks and barriers to team success. | I contribute meaningfully to hiring when opportunities exist, focusing on raising the bar in interviews and candidate evaluation (quality, not frequency). I help refine and improve hiring practices (e.g., interview questions, evaluation rubrics, and process improvements). I mentor and coach peers by sharing approaches, frameworks, and feedback that elevate others’ professional growth, regardless of team boundaries. I actively engage in public or internal forums (e.g., tech talks, blog posts) to represent Found's engineering. |
L5 | Leads major technical areas with company-wide impact, defines long-term strategy, acts as a culture carrier, and drives engineering-wide improvements. | I set and uphold engineering standards across the organization, making consequential technical choices backed by clear rationale. I ensure our major product areas align with company goals and have a clear technical direction. I take on high-risk or ambiguous engineering projects, guiding them to successful outcomes. | I am responsible for end-to-end ownership and success of major product areas (e.g. the entirety of onboarding, multiple businesses, multi owner), clearly understanding and driving strategic cross-functional implications. I consistently demonstrate the ability to manage ambiguity, complex technical problems, and drive organizational improvements. I take initiative to modernize infrastructure, streamline development processes, or increase engineering leverage across the org. | I influence engineering-wide culture by leading by example, sharing best practices, and elevating expectations around quality, process, and effectiveness. I drive systemic changes in how engineering teams operate, such as improving our on-call practices, architecture documentation, incident response, or roadmap planning processes. I represent engineering externally, fostering recognition as a technical leader beyond the immediate organization. I am trusted to work independently on impactful problems and am often brought in to drive or redirect critical initiatives. I proactively partner with Engineering Managers and Product Managers to shape product strategy, influence roadmap priorities, and align technical execution with business outcomes. | I shape and lead hiring initiatives to meet long-term technical needs, ensuring bar-raising evaluation and thoughtful role definition. I coach others in interviewing, candidate assessment, and thoughtful team composition — balancing skills, seniority, and diversity to meet long-term org needs. I mentor extensively, developing engineers and engineering leaders across multiple teams. I am a culture carrier: I actively shape and sustain Found’s engineering culture, values, and community. Examples include leading dev drop-ins, organizing internal meetups, or championing inclusivity and collaboration. |
L6 | Provides visionary technical leadership, drives strategic initiatives across the entire company, and represents Found at the highest organizational levels externally. | While not always hands-on, I maintain deep technical expertise, guiding the company's technical strategy and decisions. | I lead complex, company-wide initiatives with significant strategic impact. I define and communicate long-term strategic direction across product, design, and technical domains. | I represent Found strategically at the highest levels, including to the Board, investors, and external stakeholders. I am recognized internally and externally as a thought leader, effectively influencing industry and community standards. At this level, external engagement (industry events, thought leadership, recognition) is an explicit expectation. | I build high-performing, strategically-aligned teams through rigorous hiring standards, effective performance management, and mentoring. I drive organizational knowledge sharing and mentor senior leaders across the company. |
Evolution and Growth
L1 to L2: Develop independent problem-solving, consistently deliver well-defined features, and engage proactively in team collaboration.
L2 to L3: Take ownership of broader feature areas, show strategic thinking, and begin mentoring peers through reviews and knowledge sharing.
L3 to L4: Differentiate through proactive ownership and follow-through, expand mentorship to helping others break down complex problems, and start shaping roadmap influence.
L4 to L5: Own large-scale technical areas with org-wide impact, act as a culture carrier, and broaden influence primarily inside the company.
L5 to L6:Provide visionary technical leadership, drive company-wide strategy, and take on external thought leadership as a core expectation.

for the self-employed
Found is a financial technology company, not a bank. Banking services are provided by Lead Bank, Member FDIC.