ZipRecruiter

Log In

2

Entry Level Site Reliability Engineer Jobs in Connecticut

LCR EPC LLC

Solar Design Engineer

Enfield, CT · On-site

... and site analysis methods. * Understanding of construction practices related to solar installations. * Knowledge of systems engineering approaches to optimize performance and reliability.

W3Global Inc.

Senior Quality Engineer

Avon, CT · On-site

$90K - $100K/yr

... visits, supplier/site audits, complaint handling, and statistical analysis. Qualifications ... Strong skills in applied statistics, MSA, reliability, and project coordination. * Proficiency with ...

PHOTRONICS INC

Equipment Engineer I

Brookfield, CT · On-site

This is an on-site position, and we are not open to remote candidates at this time. Essential ... reliability. * Perform routine support for corrective maintenance, preventive maintenance, and ...

Swagelok

Field Engineer

Wallingford, CT · On-site

$100 - $125/hr

This role partners closely with customers to improve system safety, reliability, efficiency, and performance through on-site evaluations, engineering recommendations, and technical consultation. The ...

previous page

Showing results 41-60

All JobsSite Reliability Engineer JobsEntry Level Site Reliability Engineer JobsEntry Level Site Reliability Engineer Jobs in Connecticut

Entry Level Site Reliability Engineer information

See Connecticut salary details

$10

$60

$87

How much do entry level site reliability engineer jobs pay per hour?

As of Sep 8, 2026, the average hourly pay for entry level site reliability engineer in Connecticut is $60.64, according to ZipRecruiter salary data. Most workers in this role earn between $52.12 and $69.28 per hour, depending on experience, location, and employer.

What is an entry level site reliability engineer?

An Entry Level Site Reliability Engineer (SRE) is responsible for maintaining the reliability, scalability, and performance of software systems. They help bridge the gap between software development and IT operations by automating processes, monitoring system health, and responding to incidents. Entry-level SREs typically work on tasks such as writing scripts, managing cloud infrastructure, and improving deployment pipelines. They collaborate with development and operations teams to ensure systems run efficiently and with minimal downtime. Strong problem-solving skills and a foundational understanding of coding, networking, and cloud services are essential for success in this role.

What are some typical responsibilities I can expect as an entry level site reliability engineer?

As an Entry Level Site Reliability Engineer, you’ll often be responsible for monitoring system performance, responding to incidents, automating operational tasks, and assisting with software deployments. You may also support your team in troubleshooting issues, documenting solutions and procedures, and participating in on-call rotations. Collaboration with software developers, IT support, and other SREs is common to ensure systems are reliable and scalable. Over time, you’ll gain exposure to more advanced tasks like infrastructure improvement projects and building new automation tools, setting a strong foundation for career growth in site reliability engineering.

What are the key skills and qualifications needed to thrive in the entry level site reliability engineer position?

To thrive as an Entry Level Site Reliability Engineer, you need a solid understanding of Linux systems, networking fundamentals, basic programming or scripting (such as Python or Bash), and generally a bachelor's degree in computer science or a related field. Familiarity with cloud platforms (like AWS, GCP, or Azure), configuration management tools (such as Ansible or Terraform), and version control systems (like Git) is commonly expected, while certifications can be a plus. Strong problem-solving skills, attention to detail, excellent communication, and a collaborative mindset will help you stand out in this position. These skills and qualities are vital for maintaining system reliability, quickly resolving incidents, and effectively supporting development teams in a dynamic operations environment.

Are entry level site reliability engineers in demand?

Entry level site reliability engineers are in high demand due to the increasing reliance on cloud infrastructure, automation, and system stability. Employers seek candidates with skills in scripting, monitoring tools, and cloud platforms like AWS or Azure, making this a growing field for new professionals.

How do I get into an Entry Level Site Reliability Engineer?

To become an entry-level Site Reliability Engineer, candidates typically need a bachelor's degree in computer science, engineering, or a related field, along with foundational knowledge of Linux systems, scripting, and cloud platforms like AWS or GCP. Gaining experience through internships, personal projects, or certifications such as the Google Cloud Associate Engineer or AWS Certified Solutions Architect can improve job prospects. Familiarity with monitoring tools, automation, and understanding of system reliability principles are also beneficial for entry-level roles.

What are the most commonly searched types of Site Reliability Engineer jobs in Connecticut?

The most popular types of Site Reliability Engineer jobs in Connecticut are:

What are popular job titles related to Entry Level Site Reliability Engineer jobs in Connecticut?

For Entry Level Site Reliability Engineer jobs in Connecticut, the most frequently searched job titles are:

What job categories do people searching Entry Level Site Reliability Engineer jobs in Connecticut look for?

The top searched job categories for Entry Level Site Reliability Engineer jobs in Connecticut are:

What cities in Connecticut are hiring for Entry Level Site Reliability Engineer jobs?

Cities in Connecticut with the most Entry Level Site Reliability Engineer job openings:

Entry Level Site Reliability Engineer jobs near you
Infographic showing various Entry Level Site Reliability Engineer job openings in Connecticut as of August 2026, with employment types broken down into 1% As Needed, 82% Full Time, 13% Part Time, 2% Temporary, and 2% Contract. Highlights an 93% Physical, 3% Hybrid, and 4% Remote job distribution, with an average salary of $126,124 per year, or $60.6 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Hamden, CT • On-site

$20 - $30/hr

Full-time

Posted 7 days ago

Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.

Apply