1

Elasticsearch Observability Engineer Jobs in Connecticut

Elasticsearch Observability Engineer information

What does an Elasticsearch Observability Engineer do?

An Elasticsearch Observability Engineer is responsible for designing, implementing, and maintaining observability solutions using the Elasticsearch stack (Elasticsearch, Logstash, Kibana, and Beats). Their primary role is to ensure that systems are monitored effectively, logs and metrics are collected and analyzed, and issues are detected and diagnosed quickly. They collaborate with development and operations teams to build dashboards, set up alerts, and optimize performance for monitoring infrastructure and applications. These engineers play a key role in improving system reliability and supporting incident response.

How does an Elasticsearch Observability Engineer typically collaborate with development and operations teams?

As an Elasticsearch Observability Engineer, you frequently partner with both development and operations teams to design and implement monitoring solutions using the Elastic Stack. You'll help developers instrument applications for better traceability and support operations in troubleshooting and optimizing system performance. Regular communication is key, as you'll often lead workshops, create dashboards, and respond to incidents collaboratively. This cross-functional teamwork ensures observability solutions align with organizational goals and provide actionable insights.

What are the key skills and qualifications needed to thrive as an Elasticsearch Observability Engineer, and why are they important?

To thrive as an Elasticsearch Observability Engineer, you need expertise in Elasticsearch, log management, and data analysis, often supported by a degree in computer science or a related field. Familiarity with observability tools such as Kibana, Logstash, Beats, and experience with cloud platforms and scripting languages like Python or Bash are typically required. Strong problem-solving abilities, attention to detail, and effective communication skills help you stand out in this role. These competencies are vital for ensuring system reliability, quickly detecting issues, and delivering actionable insights for continuous improvement.

What is the difference between Elasticsearch Observability Engineer vs Elasticsearch Developer?

AspectElasticsearch Observability EngineerElasticsearch Developer
Primary FocusMonitoring, logging, and observability of Elasticsearch clusters and related systemsDeveloping, customizing, and optimizing Elasticsearch applications and integrations
Skills & CertificationsKnowledge of Elasticsearch, Prometheus, Grafana, scripting, and monitoring toolsProficiency in Elasticsearch APIs, Java, REST, and development frameworks
Work EnvironmentOperations teams, DevOps, SREs, cloud environmentsDevelopment teams, software engineers, backend developers

While both roles require expertise in Elasticsearch, the Elasticsearch Observability Engineer focuses on system monitoring and ensuring Elasticsearch health, whereas the Elasticsearch Developer concentrates on building and customizing Elasticsearch-based applications. Their skills and daily tasks differ, but both are essential in Elasticsearch-centric environments.

What are popular job titles related to Elasticsearch Observability Engineer jobs in Connecticut?

For Elasticsearch Observability Engineer jobs in Connecticut, the most frequently searched job titles are:

What job categories do people searching Elasticsearch Observability Engineer jobs in Connecticut look for?

The top searched job categories for Elasticsearch Observability Engineer jobs in Connecticut are:

Software Engineer: Redis and Valkey on Openshift

IKCON Technologies Inc

Windsor, CT • On-site

$52.50 - $72/hr

Contractor

Re-posted 10 days ago


Job description

IKCON TECHNOLOGIES INC delivers exceptional IT services and solutions that provide clients with definite edge over competitors and promoting highest standards of quality. We are currently looking for a Software Engineer: Redis and Valkey on Openshift with one of our clients in Hybrid (Multiple Locations). If you are actively looking for opportunities, please send us your updated resume with your contact details. 

“U.S. Citizens and those authorized to work in the U.S. are encouraged to apply.” 

JOB TITLE 

 Software Engineer: Redis & Valkey on Openshift

CITY 

 Windsor

STATE 

 Connecticut

TAX TERMS 

 W2, C2C

EXPERIENCE 

 12-18

INTERVIEW MODE 

 Teams Video Call/Telephonic

Title: Senior Engineer: Redis and Valkey on OpenShift
Location: Hybrid (New York, NY, Windsor, CT, Atlanta, GA, Minneapolis, MN, Scottsdale, AZ, Jacksonville, FL, Braintree, MA)

1. Experience & Qualifications

Professional Experience

  • 10+ years of professional experience in infrastructure, DevOps, or platform engineering roles, with at least:
    • 5+ years of hands-on experience with OpenShift or Kubernetes.
    • 5+ years of experience with Redis (including production deployments, performance tuning, and advanced setups like clustering and Sentinel).
    • Proven expertise in deploying and managing stateful applications in cloud-native environments.
    • Track record of managing high-throughput, low-latency databases in real-time distributed systems.

Production Scale Experience

  • Experience operating Redis or similar in-memory databases (e.g., Memcached, Hazelcast) and key-value stores at enterprise scale with:
    • Millions of queries per second.
    • Large datasets requiring optimized memory usage.
    • Reliability demands of >99.99% uptime.

2. Core Technical Skills

A. Redis & Valkey (Highly Advanced Proficiency)

  • Expert-level knowledge of Redis:
    • Master-slave replication.
    • Redis Sentinel for high availability.
    • Redis Cluster for horizontal sharding and distributed data management.
    • Memory optimization techniques for efficient handling of large datasets.
    • Ability to debug, scale, and fine-tune Redis (e.g., handling eviction policies, tuning buffer utilization, and optimizing AOF/RDB persistence mechanisms).
  • Advanced knowledge of Valkey (or similar key-value database architectures), with a focus on scalability across distributed systems.

B. Automation (Infrastructure-as-Code):

  • Infrastructure-as-code expertise with:
    • Helm charts to deploy and manage Redis/Valkey.
    • Developing and managing Operators with automation built in Ansible, Kustomize, or Terraform.
    • OpenShift-native CI/CD pipelines (Tekton/Red Hat Pipelines) for automated deployments and scaling.

C. Monitoring & Observability:

  • End-to-end monitoring of Redis and Valkey deployments with:
    • Prometheus (e.g., Redis exporter for Redis metrics).
    • Grafana dashboards for cluster state, replication lag, memory usage, and query performance.
    • Centralized logging with the ELK stack (Elasticsearch, Logstash, Kibana) and OpenShift native logging solutions.
  • Expertise in interpreting metrics and logs for incident response.

D. Networking and Security:

  • Advanced knowledge of securing Redis/Valkey in cloud environments:
    • TLS certificates for encryption in transit.
    • IP-based firewalls or OpenShift Network Policy for endpoint restrictions.
    • External Secrets or OpenShift secrets for managing authentication credentials.
  • Expertise in debugging ingress, load balancing, and network latency issues.

3. Soft Skills

As a highly senior engineer, the individual is expected to bring advanced leadership and team collaboration skills:

  • Technical Leadership:
    • Mentor developers, DevOps engineers, and platform teams on Kubernetes/OpenShift setups and database best practices.
    • Own technical decisions around critical Redis/Valkey architecture, ensuring scalability and uptime.
  • Collaboration and Communication:
    • Strong ability to coordinate with product teams, infrastructure architects, and security teams.
    • Prepare detailed technical design documents and present system architectures.
  • Ownership and Problem Solving:
    • Take end-to-end accountability for Redis/Valkey in production environments.
    • Anticipate issues and proactively build systems to mitigate risks.

Challenges They Should Be Capable of Handling

  1. Migrating Redis or Valkey deployments to OpenShift.
  2. Zero-downtime upgrades for Redis clusters.
  3. Guaranteeing max performance at peak loads (e.g., 1M+, high-throughput workloads).
  4. Developing automated scaling and healing mechanisms for Redis on OpenShift.