• This is a contract to hire position for the first six-months. For high performers, you'll be offered an opportunity to convert to the FTE/direct-hire employment of our client.
• This position is for full-time direct hires only. We kindly ask that consultants or C2Cs refrain from applying, as their profiles will be promptly deleted.
• Unfortunately at this time we can not sponsor or transfer H1b work visas.
• This role is located in the Phoenix area and must be onsite a minimum of three days a week in order to be considered.

Our client, a global leader in Financial Technology. With a valuation exceeding $150 billion and annual revenue of over $50 billion, they stand as a formidable force in the industry. Serving a vast customer base of 141.2 million worldwide, their reach is unmatched. Specializing in mission-critical, highly scalable, and impeccably secure financial systems, they set the standard for reliability and innovation in the sector.

JOB DESCRIPTION

Help shape the future of database technology with our client! We are seeking top technical talent to enhance our Database Engineering team. This R&D team within our client's technology division is responsible for selecting and optimizing operational database technologies. We define, design, implement, test, and communicate architectures, configurations, best practices, and standards for optimal database use across the company, both on-premises and in the cloud. We evaluate new and upgraded database versions, features, components, and extensions for performance, scalability, availability, and security. Additionally, we collaborate with hosting, database administration, and operational support teams to operationalize and fortify OLTP technology for our client's premier financial applications.
As part of integrating and enabling new database technologies, we also evaluate the technologies from a developer perspective. How should developers write code to connect to these databases? What are the capabilities and limitations of the database driver software? How should connection pooling be implemented? What amount of traffic can this database type take from application code? What latencies can developers expect? If one node in a multi-node database cluster fails, how should application code reconnect to the cluster? Should developers use retry logic in case of connection failure? How best should an application authenticate itself to the database? And so on.

JOB RESPONSIBILITIES

• This specific career posting is for a software engineer with experience coding in Java, Python, Go and/or other popular languages, who has a special interest in database technology and how best to use it from application code.
• Working under the guidance of an existing lead developer, the candidate will write test harnesses and sample code to connect to and interact with databases of various types, including MongoDB, Couchbase, Cassandra, Oracle, Postgres, SQL Server, and with public cloud databases like AWS Aurora Postgres, RDS SQL Server, DynamoDB, and Google CloudSQL, Spanner, BigTable and more.
• The candidate will research and explore, test, document, and share the best practices for various programming languages connecting to and using lots of different database technologies.

EXPERIENCE

• Full Stack Engineering experience is preferred, but will consider a candidate who will lean more toward the backend as well.

REQUIRED EXPERIENCE

• 3 years of Java development experience, ideally in v17, but will also consider v8.
• Experience with Spring Boot.
• Experience authoring Restful APIs.
• Experience deploying to production clouds such as AWS or Google Cloud Platform.
• Experience building applications upon RDBMS and NoSQL databases.