Skip to main content

Site Reliability Engineer

Posted 2 days ago

acestackJacksonville (FL)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Site Reliability Engineer Site Reliability Engineers are expected to be able to drive technology triage efforts to completion by assisting with restoral steps, identifying root cause, and work with different ITIL teams to improve environment stability. Must have a background of server management (Windows/Linux), understand distributed application flow, level of understanding code (Java/.NET), scripting, database knowledge (SQL/Oracle) and network transport layer. Primary Skill: Splunk, Dynatrace, Linux/Windows Administration, Java, SQL, Autosys, Spring Boot, Kafka, Cockroach DB, Redis, JIRA, NetScout or related. Secondary: Oracle, MS SQL, Sybase, Mainframe, and DB2, ITIL Certified.
Experience: Minimum 8 years.
Roles & Responsibilities:
  • Experience with Remedy, Service now, JIRA in creating/updating/closing incident tickets
  • Executing Bladelogic scripts to route traffic/recycle JVMs/enable/disable MQsRouting traffic using AIC tool
  • Experience in using SoapUI/PostMan tool to test SOAP/REST APIsProven experience in production support or a related role
  • Experience in supporting Java/Java web services based applications with high volume transactions
  • Working knowledge of Splunk and Dynatrace tools to identify issues in production quickly
  • Basic knowledge of using Unix/Linux commands to login into servers, fetch logs, copy/delete files, run shell scripts
  • Strong analytical and problem-solving skills
  • Familiarity with incident and problem management processes
Excellent communication skills and ability to understand customer-based requirements and expectations. Strong documentation skills. Highly effective at driving process improvement based on lessons learned analysis. Ability to work effectively in a team environment and independently Willingness to work in shifts and provide weekend support on a rotational basis Strong Mulesoft experience (4.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this