Position: NOC Engineer
Company: Globallogic
Experience required: 1y
Category: Sysadmin
English level: intermediate
Published: 2020-09-01T00:00:00+03:00

Tools/solutions that are used in the project:
- Linux and Windows servers on-premises and deployed in the cloud environments (AWS).
- Apache, Nginx, IIS, MySQL, MSSQL, Couchbase, ElasticSearch, Redis, Memcached, Sphinx, RabbitMQ, Celery.
- Components on C++, JAVA, PHP, Node.js, Python.
- CI/CD toolset: Jenkins, Git, Ansible, Chef, Terraform, CloudFormation, Docker, Kubernetes

Monitoring solutions used in the project:
– OpsGenie alerts and incidents management platform
– Prometheus, Grafana, Kibana
– AWS Cloudwatch for native AWS environments events collecting
– PRTG, Zenoss
– External availability monitoring using Dotcom-Monitor
– Witbe robots for FE end-to-end scenarios monitoring
– Youbora for end-user experience analytics
– Logz.io as central logs and traffic aggregator

Requirements
- At least 1-year experience in a similar position (NOC/Tech Support/System administrator or relevant experience etc.) – a must
- Good English language skills (at least intermediate spoken and written level) – a must
- Systems administration, automation scripting, and tech support skills
Cloud computing and networking understanding
- Web applications and servers architecture understanding, HTTP, REST API
- Monitoring tools and principles
- Eager to learn and great customer service attitude
- Strong troubleshooting and problem-solving skills
- Drive to preventing incidents
- Willingness to work shifts (24/7) – at least 4 days a week

Preferences:
Grafana, Python, bash scripting, Powershell Scripting, DevOps Tools, Customer Support, Zabbix, Nagios, Kubernetes

NOC engineer responsibilities
–    Network, Infrastructure, Services monitoring
–    Respond to incidents according to the incident management policy
–    Finetune checks and alerts thresholds
–    NOC toolset maintaining
–    Service monitoring during the maintenances
–    Performance reports (i.e. uptime, response times and services status)
–    Production quality control (end-users service level monitoring and ability to check it after changes take place)
–    Keep and update a directory of all 3rd parties (store partners contacts and keep escalation schemas up to date)
 
NOC department responsibilities
–    One focal point that always knows the service level and issues status
–    Drive to continuous improvement between all departments on monitoring needs
–    Defining reliable and preventive monitoring requirements as part of the product development life cycle
–    Drive to run recovery procedures that regain service as soon as possible
–    Communication, coordination, collaboration