Senior Software Engineer - Banking and Money Movement Team

View full description

Requirements:

• 5+ years of experience as a backend engineer with a Bachelor’s degree; or 3 years of experience with an advanced degree.
• Experience developing in Java.
• Experience with Web Services and Microservices.
• Experience with SQL.
• Experience working with distributed systems.
• Experience working at a SaaS based product company.
• Ability to decompose business problems into solutions that may require designs with multiple interacting components.
• Ability to to build correct, maintainable software components.
• A focus on quality and meeting deadlines.
• A strong grasp of the libraries, platforms, and systems.
• Ability to present clear and concise messages tailored to various audiences; able to communicate in a clear, concise, and respectful manner both verbally and in writing.
• Ability to share relevant information including if difficult task-level trade-offs that impact the product need to be made.
• Ability to work with cross-functional stakeholders to identify technical blindspots and clarify ambiguity.

Responsibilities:

• Define and deliver well-scoped milestones for projects and may be a technical lead for projects on your team.
• Actively keep customer needs in mind and leverage input from product stakeholders to determine the right technical solutions to deliver customer value quickly.
• Actively level up less-experienced members of your team by helping them with their craft, providing guidance, and setting a good example.
• Independently write code that is clear with minimal bugs that captures the essential nature of the solution and is appropriately flexible, reusable, efficient, and adaptable to changing requirements.
• Identify gaps and propose plans for addressing those gaps.
• Challenge the status quo and come up with innovative ideas.
• Lead design for small-medium components/features and participate in design for larger components/features (moving from task level impact to small-medium project level impact).
• Have significant ownership of a component/feature of the system.
• Independently design software components in well-scoped scenarios, with simplicity and maintenance as key considerations, ensuring components are testable, debuggable, and have logical APIs that are not easily misused.
• Participate in on-call coverage