Senior Software Engineer - CPM Disputes

View full description

Requirements:

• 5+ years of hands-on software engineering with a Bachelor’s degree; or 3 years and a Master’s degree; or a PhD. In lieu of a degree, 8+ years of relevant experience may suffice.
• 3+ years of backend experience in Java
• 3+ years of full stack/frontend experience
• Experience in developing applications with modern Java backend stack using Spring Boot and Kubernetes on AWS.
• Experience both building and consuming RESTful APIs
• Experience with SQL, data modeling, and database technologies (MySQL preferred)
• Experience developing scalable microservices on cloud platforms like AWS (preferred), Azure, or GCP
• Strong analytical and problem-solving skills with a high attention to detail
• Strong collaboration and communication (verbal and written) skills. Can effectively work cross-functionally and deliver a project.
• Experience working in modern software engineering ecosystems that leverage frameworks, methodologies and technologies such as CI/CD, containerized apps, Agile (Scrum)
• 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:

• Design, build, test, and continually improve the services that support Marqeta’s Dispute management platform.
• 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 towards addressing those gaps.
• Challenge the status quo and come up with innovative ideas.
• Lead design for medium components/features and participate in design for larger components/features (moving from task level impact to medium-size 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