Site Reliability Engineer (SRE)

Bright Vision Technologies is looking for a Site Reliability Engineer (SRE)(remote). This isn’t a gig where you just sit around waiting for a ticket to drop or blindly restart servers. They want a true software engineer who looks at broken, manual operations infrastructure and says, “I can code my way out of this nightmare so it never happens again.”

Before we look at the tech stack, let’s talk about the hiring logistics. The company is incredibly strict about their employment structure, so let’s make sure you don’t waste your time applying if it’s a bad fit:

• Strictly Direct W2 Only: If you are a recruiter trying to broker a candidate, or an independent contractor looking for a C2C (Corp-to-Corp) or 1099 setup, it’s a hard pass. They only want full-time, direct employees on their payroll.
• Where You Need to Live: This is a 100% work-from-home job, but you must be physically living within the Continental United States.
• The Visa Situation: They cannot sponsor brand-new H1B visas. However, if you already have a valid H1B visa and just need to transfer it to a new employer, they are completely happy to sponsor that transfer for the right engineer.
• Yes, There’s a Technical Quiz: You will have to do a live coding and systems assessment. No exceptions. They want to make sure you can actually write clean code under pressure, not just talk about it.

Experience & Pay

They are looking for someone with at least 5 years of hands-on experience keeping large, highly distributed systems alive. The pay is competitive and depends entirely on how deep your expertise goes, and it comes with full health benefits, retirement, and long-term job stability since you’ll be working on their core multi-year internal product roadmap.

What Your Daily Work Actually Looks Like

You’ll be sitting right at the boundary line where the software development and infrastructure operations teams meet. Your main goal? Eliminate “toil”—that boring, repetitive manual work that burns engineers out and build systems that heal themselves.

Here is what you’ll be doing:

• Acting as Incident Commander: When production breaks and everything hits the fan, you’re the calm voice in the room guiding the team to fix it. Afterward, you’ll lead blameless post-mortems to figure out the root cause, not to point fingers, but to ensure the system is hardened against that specific failure next time.
• Defining Real Metrics (SLOs and SLIs): You’ll help set realistic targets for system uptime and performance, using error budgets to tell the dev team when they need to stop pushing new features and start fixing structural bugs.
• Building Deep Visibility: You’ll design comprehensive monitoring, tracing, and logging setups using tools like Prometheus, Grafana, OpenTelemetry, ELK, or Datadog so the team can spot weird system behavior before it causes a major outage.
• Coding Automation Tooling: You’ll spend a massive chunk of your time writing actual production-grade internal tools and scripts using Python, Go, or Bash to replace clunky manual workflows.
• Wrangling Kubernetes: You will architect, optimize, and manage large-scale K8s clusters, keeping an eye on autoscaling, capacity planning, and how traffic moves through service meshes.
• Playing with Chaos Engineering: You’ll intentionally inject faults and run stress/load tests to see exactly how the platform breaks under pressure, adding circuit breakers, timeouts, and smart failover paths to keep it resilient.

Are You the Person They’re Looking For?

• A Bachelor’s degree in Computer Science, Engineering, or a related technical field.
• Strong programming skills in Python, Go, or Java. You need to be a capable developer, not just someone who writes simple 5-line bash scripts.
• Serious Linux mastery. You know how the kernel works, how to tune network performance, and how to troubleshoot low-level system issues when a server locks up.
• True production experience running live containers on Kubernetes.
• Solid communication and documentation skills—because an automated system is only good if the rest of the team knows how to use it and read the runbooks.

Bonus Points If You Have:

• Experience setting up real error budgets and SLOs that teams actually follow.
• Experience with chaos tools like Chaos Monkey, Gremlin, or Litmus.
• Deep familiarity with at least one major cloud provider (AWS, GCP, or Azure).
• Hands-on time with service meshes like Istio, Linkerd, or Consul.