API Engineer
Work Location : Charlotte - 601 S. Tryon Street (601 S. Tryon Street,
Charlotte, NC 28202)/ Onsite in
Charlotte or Detroit for Hybrid model - 3 days a week
** Video conference interview; provide location and best time to interview – 2
Interviews – video-on screen.
Ally Financial
Rate - $70 on c2c
Mandatory skills - **API
Engineer - **API – building API solution – integration layer – ERP migration of
40+ systems; ** AWS services - EC2, RDS, Lambda, S3, CloudFront, etc.; **Python
– scripting; ** Gitlab; *Terraform**DevSecOps and Security understanding;
**Cloud - Architectural understanding /Global view. **10+ years of experience;
Excellent communication skills – written and verbal; able to work with global –
matrixed team; Professional demeanor and curious mindset; Able to deliver on
requirements without a lot of direction; Proactive go-getter – independent,
self-starter – autonomous worker who will take initiative but can work well
collaboratively.
Job Description
Create and maintain technical design documents and requirements including workflow design of company's API's. Participate in design and planning meetings with company's API customer Programmers and Systems Architects. Work with development teams from project initiation through to production implementation in a consultative role. Provide status updates on assigned project deliverables. Work with application support teams to ensure API environment availability through effective proactive monitoring and prevention to avoid unplanned outages. Ensure API failures are handled effectively and resolved in a timely fashion. Analyze dumps, traces, and logs to determine root cause of specific problems. Identify and prioritize enhancements to existing API's and ensure execution per plan. Work with team lead and team members to determine best value service improvement opportunities. Actively seek opportunities to increase customer satisfaction. Ability to define, document, implement, and operate repeatable, well purposed processes. Identify assumptions, constraints, and anticipate and manage risks. Design services, applications, and/or API functional and non-functional requirements are considered (i.e. security, compatibility and maintainability).
Best regards,