Role Description This role is for engineers who can independently own meaningful parts of a system. As an Engineer II, you are expected to move beyond execution and take responsibility for how systems behave in production. You will design, build, and improve services while owning their reliability, performance, and long-term maintainability. You will work across backend systems, infrastructure, and reliability, with increasing responsibility for decision-making and system design. You are not just implementing tasks—you are accountable for outcomes. What You Will Do - Design, build, and maintain backend services and APIs - Own specific systems or components, including their reliability in production - Debug complex issues across services, infrastructure, and data flows - Improve system performance, scalability, and fault tolerance - Contribute to CI/CD pipelines, deployment processes, and release quality - Use LLM tools effectively to accelerate development while maintaining quality - Participate in incident response and lead root cause analysis efforts - Collaborate with product and engineering to define clear, testable solutions - Contribute to system design decisions and technical tradeoffs Qualifications - 3–5 years of experience building production software systems - Strong proficiency in at least one backend language (Python preferred) - Experience designing and building APIs and working with databases - Solid understanding of system design fundamentals (scalability, reliability, failure modes) - Ability to debug across layers (application, infrastructure, data) - Demonstrated ownership of systems or major features - Comfort working in environments with real operational constraints Strong Signals - You have owned a system or service in production - You proactively identify and fix reliability or performance issues - You think in terms of tradeoffs, not just implementation - You improve systems beyond your immediate scope - You use tools (including AI) to increase speed without sacrificing quality - You help raise the bar for those around you What Success Looks Like - Systems you own are stable, reliable, and well understood - Production issues are identified, resolved, and learned from quickly - You reduce dependency on more senior engineers for execution - You make sound technical decisions with limited guidance - You improve how the team builds, tests, and ships software How We Work We operate with a small set of principles: - Focus on a small number of important goals - Measure what matters and make it visible - Own outcomes, not just activity - Ship consistently and improve through discipline You are expected to lead by example in how you apply these principles. Who Should NOT Apply - You are looking for a purely remote role - You prefer narrowly scoped tasks over system-level ownership - You are not interested in production responsibility or operational accountability - You rely heavily on direction for technical decisions - You avoid debugging complex, ambiguous problems - You are not interested in improving systems beyond your assigned work Compensation - Competitive, market-aligned salary - Additional compensation and growth tied to performance and impact Why This Role This is an opportunity to become a strong mid-level engineer by owning real systems. You will work on infrastructure and applications used by financial institutions, operate under real constraints, and develop the judgment required to design, build, and maintain production systems. If you want to take the step from contributor to owner—and are willing to be held accountable for system outcomes—this is the role.