Position Title: Monitoring Engineer
Location: Plano, TX
Duration: 6+ Months Contract
Monitoring Engineer
" As a Monitoring Engineer, you will be responsible for initial analysis and triage of issues before they are assigned to individual development teams for root cause and fix.
" You will continuously monitor the infrastructure, applications, logs, service availability, and work closely with PO, Eval & Development team members to clarify issues and track them to closure.
" Create dashboards and reports for management and other stakeholders.
" Have great problem-solving skills, analytical, tools & development experience, and ability to evaluate and identify issues at a code level.
" Able to summarize key points and work with others to cut through ambiguity and bring issues to resolution.
" A history of working with cross-functional teams to ensure successful product.
" You must be a self-starter with excellent communication skills, attention to detail and a knack for solving problems creatively.
" The fast-paced nature of the job requires that you be able to work well under pressure.
Skills:
" Experienced in Automotive Infotainment domain with exposure to embedded software development in C/C++/ Linux/Java-Spring boot.
" Experience in Observability and monitoring tool Datadog, AppDynamics.
" Experience or knowledge in cloud computing (AWS Services)
" Knowledge in AWS services like AWS ECS, AWS Lambda, AWS FARGATE, AWS CloudWatch. etc.
" Experience and knowledge in MongoDB.
" Knowledge of how to use JIRA, Confluence and Logs Analysis Tools.
" High Level System Architecture Knowledge - SW Design, Sequence diagrams, APIs, HTTP error codes.
" Conversant with Linux commands, utilities and basic Python scripting
" Experience in Agile and Scrum methodologies.
" Requirement Analysis and understanding.
" Thinking on the feet and aptitude to learn.
Preferable but not mandatory skill sets
" Experience in designing, developing, and debugging software in a real-time embedded environment.
" Knowledge of how to read DLT logs, DLT-Viewer and how to apply filters in DLT logs