Elasticsearch Engineer

Duration: 12+ mo. Contract; potential to extend

Address: Lehi, UT or 100% Remote

Work Schedule: Monday 9am 5pm MST preferred.

Dress Code: Business casual/casual

Why is the position open: The skillsets needed for a current project that is up and running currently in a testing phase are already on the team. This role is to provide additional capacity to the team. The role is most closely aligned with Cloud Engineer title compared to Data/Analytics or DevOps.

Main responsibilities:

• They have 16 ElasticSearch clusters in AWS so this person will help the team identify when additional clusters will need to be created as they add customers. Needs to help with capacity planning and help look at how many more clusters need to be created when they add clients with their own documents that need to be stored. Do they need to move documents from one cluster because hardware on that isn t as fast as required? This person must have technical expertise to identify and answer that question.
• Manage data ingestion pipelines and involved in optimizing/managing data ingestion pipelines. Also involved with incident management and troubleshooting so need to understand how data flows into Elastic.

Requirements:

• MUST HAVE
• 5+ years' experience designing and managing production ready multi-cluster Elasticsearch instances in AWS public cloud
• Unix/Linux experience managing and implementing and troubleshooting it
• Great understanding of how search works across different platforms is fine, but knows in terms of indexes, every component that supports ecosystem like Kafka which they use. (Could be RabbitMQ, AMQ experience)

• Soft skills:
• Excellent communication and collaboration skills, with the ability to work ask for help from team members and proactively find additional work
• Willing to speak up and share best practices from their own past experiences to help team avoid pitfalls
• NICE TO HAVE
• Using Elastic as a Document management platform strongly preferred
• Python for scripting/automation, using PowerShell in current environment now but that will shift to Python over time
• TerraForm they are building it out as Infrastructure as Code