Production Support Engineer

Job: Production Support Engineer

Location: Chicago, Illinois

Remote: hybrid roles – they go onsite 2-3 days a week

Duration: until Dec. 31

In-person interview

Project/Day to Day: Supporting the development and fixing issues, and helping with releases // make sure all systems are 100% and support the queries, monitoring systems and platforms, vast experience in AI to maintain systems and accelerating the time of issue management, accelerating automation

TOP SKILLS:

• Candidates should have 5+ years of relevant experience, primarily in operations support, with administrative support experience also considered highly desirable.
• Operationally – how do these things work; monitor and manage and fine-tune Kong (or general knowledge in API gateways), Kubernetes, Microservices and working knowledge of tools Splunk
• This is almost like a site reliability engineer; if they have SRE on this tech stack or tools that is the person he is looking for
• Open to the idea of a (50/50) (Dev/Support Candidate), Ideal Candidate is a resource from SRE/ProdSupport within a Microservices/Dev Team.
• 80%+ of their Microservices are sitting within OpenShift (OCP), as they mature within their environment, they will be adding more within Azure (AKS). Open to both options.
• Strong expertise in Microservices architecture with practical experience designing, deploying, and supporting distributed systems in production environments. **they own and monitors the Microservices environment – need an understanding of architecture from container, pod and cloud perspective
• Deep hands-on knowledge of Kubernetes (deployment management, scaling, upgrades, troubleshooting, cluster operations) with a focus on reliability, resilience, and performance. **This is going to be on the Operation side—will be troubleshooting, upscaling, working with OCP engineer team or Azure partners
• Working proficiency with API Gateway platforms such as Azure API Management (APIM), Kong, and IBM API Connect (APIC) for traffic management, rate limiting, routing, and API observability. **Most API’s are passthroughs but if there are service layers than this is where the microservices comes in; they will limit routing