DirectJobHub
Jobs · Information Technology · California

Sr Software Engineer (Backend)

Happen Bank · San Francisco, CA · 3 wk ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements/Qualifications (About You), maybe Skills, Benefits, Pay, Schedule. Must include only sections with real specific content. We have: - About The Role: paragraph description. - What You'll Do: list of duties (bulleted). Should be
  • . - About You: list of requirements/qualifications (bulleted). Should be
    • . - Nice to Have: could be separate section? Could be under Requirements or separate "Preferred Qualifications". The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About The Role ->

      About the role

      . What You'll Do ->

      Responsibilities

      . About You ->

      Requirements

      (or Qualifications). Nice to Have could be under Requirements as separate list? Could be separate

      Preferred Qualifications

      but not in list; but we can include as part of Requirements with sub-bullets? Better to keep as separate section "Preferred Qualifications". The instruction says use those headings; but we can also add other headings if needed? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. We could put Nice to Have under Requirements as a sublist? Might be okay. - Work Location: includes hybrid schedule, in-office days, relocation, time zone, travel. This could be Schedule section? Not exactly schedule but location/hybrid. Could be under Schedule? The schedule is hybrid Tue-Thu in-office. Could be placed under Schedule heading. Also mention relocation, time zone, travel. Those are details. - Compensation: includes base salary range, bonus, equity, benefits. So we can have Pay section with salary range, and Benefits section with benefits list. - Benefits: medical, dental, vision, 401(k) match, health and wellness programs, flexible time off, up to 16 weeks paid parental leave, etc. - Pay: target base salary range 190,000-207,000, plus long-term awards (equity) and annual bonus. - Schedule: hybrid work model, in-office Tuesdays, Wednesdays, Thursdays, remote not considered, relocation based on job level, time zone primarily PT, travel as needed. We must not include boilerplate like EEO, AI tool use notice, privacy, etc. Also remove duplicated lines, navigation, cookie, legal, EEO, equal-opportunity, scam-warning, application instructions. Also remove "Current Employees of Happen Bank: Please apply via your internal Workday Account". Also remove "Happen Bank (formerly LendingClub) is built around a simple purpose..." maybe that's introductory but not a section; we can keep as part of About the role? Actually it's generic company description; could be included in About the role paragraph? The About the role section already has description; we could keep the introductory paragraph as part of About the role? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company purpose paragraph somewhere. It could be placed before About the role heading as a

      . Since we cannot repeat job title as heading, but we can have a paragraph about company. That's fine. We must not include "Happen Bank offers relocation, based on actual job level." That's substantive, keep in Schedule or maybe a separate paragraph. We must not include "Time Zone Requirements Primarily PT" etc. We must not include "Travel Requirements As needed travel to Happen Bank offices and/or other locations, as needed." We must not include "Compensation The target base salary range for this position is 190,000-207,000." etc. We must not include "We’re creating new financial services solutions..." etc (that's fluff but maybe substantive? It's about mission; could be kept but it's similar to earlier purpose. Might be considered boilerplate? It's not EEO but it's still generic. Safer to keep it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's about mission; could keep. But we already have purpose paragraph earlier; could be duplicate. Might be considered duplicated lines? It's similar but not identical. Might be okay to keep but we could omit to avoid duplication. However instruction says preserve ALL substantive information; not to invent or summarize away detail. If we omit it, we lose some substantive info about mission. But we already have similar purpose paragraph earlier; maybe it's okay to keep one. The earlier paragraph: "Happen Bank (formerly LendingClub) is built around a simple purpose: to clear the way to help people turn intention into action, and action into financial progress. That means offering focused products, a frictionless mobile-first experience, and clear terms with no gotchas. Respect and fairness is part of our DNA, and that ideal shapes how we work, how we treat each other, and how we invest in our employees and our community. Join us in using data, bold thinking, and a commitment to innovation to help clear the way for millions of Americans to achieve more." That's substantive. The later paragraph: "We’re creating new financial services solutions for our members based on fairness, simplicity, and heart, and we treat our employees the same way." That's also substantive but similar. Could keep both; not duplicate exactly. I'd keep both as separate

      before About the role. Now structure:

      Company purpose paragraph.

      Second mission paragraph.

      About the role

      As a Sr Software Engineer, you'll drive complex initiatives across our authentication and user profile management systems, owning the user-management service end to end and leading software design, development, and delivery. This role focuses on taking ambiguous, complex problems and transforming them into reliable, well-architected systems that every product surface — and every user session — depends on. The systems you'll own sit at the center of our platform: authentication and identity for millions of users across lending, banking, and investment products, with strict PII handling, field-level encryption, and the login/session reliability that everything else in the platform is built on top of.

      Responsibilities

      • Lead initiatives end to end across the authentication and user profile domain, from technical analysis and system design through delivery and operation
      • Own the reliability of systems that authenticate users and manage their profile and account data credentials, sessions, MFA/SSO, contact and preference data, and account recovery flows
      • Design and operate distributed systems on AWS, including event-driven flows on AWS Lambda, addressing consistency, fault tolerance, and scale for high-throughput authentication traffic (login, token refresh, session validation)
      • Make and document technical decisions, weighing tradeoffs in scalability, cost, and maintainability for systems built on Java and cloud technologies
      • Lead system design discussions and design reviews, partnering with software architects, product managers, and business stakeholders to align technical direction with business goals
      • Harden authentication and profile APIs consumed by every downstream service, ensuring data integrity, backward compatibility, and resilience as the platform scales
      • Diagnose and resolve complex production issues across services, using strong debugging skills to trace problems through distributed systems and cloud infrastructure
      • Integrate AI tools into day-to-day engineering, accelerating analysis, coding, and review, and show peers practical, responsible ways to apply them
      • Improve how the team works by strengthening engineering practices, workflows, and standards for quality, testing, and observability, and by mentoring engineers through code review and pairing

      Requirements

      • 4+ years of software engineering experience; bachelor's degree or higher, or equivalent combination of education and experience
      • Deep understanding of RESTful API design and build clean, well-versioned, and resilient APIs for internal and external consumers
      • SME in Java and its ecosystem, including Spring Boot, JPA / Hibernate, JVM - OpenJDK, Oracle JDK, or Amazon Corretto
      • Strong system design skills and experienced designing distributed systems that stay reliable under scale, failure, and change
      • Experienced building and operating cloud-native services on AWS and designing data models on relational databases such as MySQL, PostgreSQL, or Oracle
      • Strong debugger who can trace issues across service boundaries, infrastructure, and third-party dependencies to root cause
      • Hands-on experience integrating with external vendors and partner systems, and you design for resilience when dependencies are outside your control
      • Take ownership of your domain — driving outcomes independently, anticipating risk, and following through
      • Hands-on experience using AI tools to accelerate your work and improve output quality, you're equally using them yourself and showing colleagues how, and you're thoughtful about their limitations and where human judgment matters most
      • Set a high bar for security, maintainability, and the long-term cost of decisions made in the name of speed
      • Collaborate effectively across engineering, product, and business, and you adapt your approach based on feedback and context

      Preferred Qualifications

      (but not in allowed list). Could we incorporate into Requirements as a sublist? Might be okay to add a separate heading; risk of violating instruction? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but suggests those examples. Safer to maybe incorporate Preferred Qualifications into Requirements as a separate
        with a preceding

        "Preferred qualifications:" but that adds extra text not in original? Could be okay. However we need to preserve the Nice to Have content. We could add a

        Preferred Qualifications

        as it's substantive and not covered elsewhere. I'd risk it but maybe acceptable. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. I'll include Preferred Qualifications.

        Preferred Qualifications

        • Experience in banking, trading platforms, or other regulated financial industries
        • Experience with working front end technologies
        • Experience with event-driven architectures and high-throughput, low-latency systems
        • Track record of building partner or third-party integrations at scale

        Pay

        The target base salary range for this position is $190,000‑$207,000. Base salary is just one part of LendingClub’s Total Rewards package. You may also be eligible for long‑term awards (equity) and an annual bonus (which is based on company performance, employee performance and eligible earnings).

        Benefits

        • Medical, dental and vision plans for employees and their families
        • 401(k) match
        • Health and wellness programs
        • Flexible time off policies for salaried employees
        • Up to 16 weeks paid parental leave
        • Additional benefits as part of the competitive benefits package

        Schedule

        Hybrid work model: in‑office Tuesdays, Wednesdays, and Thursdays; remote placement will not be considered. Relocation assistance is available based on actual job level.

Similar jobs