Taro Logo

Senior Site Reliability Engineer Interview Experience - Colorado Springs, Colorado

July 1, 2026
Negative ExperienceNo Offer

Process

As many other reviews state, don't waste your time with this company.

The initial call with the recruiter was promising. Pay was transparent and good, and the recruiter I interacted with was warm and professional. She promised follow-up and delivered immediately after our call- a rarity with tech recruiters. After the recruiter screen, you set up a 30 minute conversation with the lead for the team, where you get a primer on what to expect for the interview.

The interview process is a 2 week challenge prompting the candidate to build an HTTP or gRPC server that interacts with a Kubernetes cluster to read and scale deployment replicas. You can find the full prompt on their public GitHub. You will be added to a Slack with the interview panel, and are expected to submit several PRs in sequence. Each PR goes through a review process. Teleport requires 2 approvals before they give you the go ahead to proceed to the next phase of the challenge.

Phase 1 is to submit a design document (RFD). They suggest using the Teleport RFD template, which is available publicly. Several sections can be pruned from this template, but it will still be pretty detailed. My submission was 600 lines of markdown. When the PR is up, you notify the team for review. Expect it to take 48-72 hours for each member of the panel to leave you comments. I received a mix of feedback. Some were genuinely good, probing questions that revealed an oversight in some part of my proposed design.

For example, I initially scoped my service's RBAC to the deployments resource- one reviewer asked how I might tighten this to prevent the service from making other, out-of-scope changes to deployments. The fix was to scope to the deployments/scale subresource. I replied with this change and made updates within an hour of receiving the question. Other comments were pedantic and nit-picky.

I was added to the Slack around noon on day 1. I had my design PR up at 11am on day 2, after spending ~4 hours putting it together. I received no feedback that day. On day 3, one reviewer left some comments early in the day, which I responded to. He acknowledged my responses with :thumps_up:, but no other feedback. At the end of day 3, I received more feedback from another reviewer. He did not acknowledge any of my responses.

Neither reviewer approved my PR, so the following day I asked in Slack for more feedback. No response all day. On day 5 (a Friday), I asked again whether there was additional feedback, or if I was good to merge and move on to implementation. Once again, no response all day.

Feeling like I might run out of time, I built out separate worktrees implementing my solution in phases over the weekend. My plan was to ask for approval again on Monday, then immediately get my code PRs up, since the feedback cycle was clearly slowly than advertised. Monday morning, I again asked for feedback or approval to proceed. I received no response. At noon, I posted again that I had gone ahead and opened the first of three code PRs since I wanted to stay on track to finish. No response, no engagement with the PR.

At 5pm that day, the team lead emailed me to let me know I was being rejected. He gave me some feedback I suspect came straight from a Claude prompt (“tell me what to say to this candidate I’m rejecting”). He mentioned two specific technical points in my design that were explicit comments by that first reviewer on day 3. His suggestions for how I could have solved those problems were almost verbatim quotes of my replies on the PR. So he either didn’t bother reading any of my responses on the PR, or the entire feedback cycle described in their hiring process is a farce.

Look, I get it. The job seeker is, by definition, going to be devoting more effort to the interview process than the organization with the opening. I don’t expect the interview panel to be at my beck-and-call, but the lack of engagement was frankly disrespectful. Accept interview requests at your own risk; they will almost certainly waste your time.

Questions

Design and build an HTTP or gRPC server, to be deployed to a Kubernetes cluster, which can read and scale replica counts for deployment resources on the cluster.

Google "teleport sre challenge" to find the public GitHub prompt.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Teleport Senior Site Reliability Engineer role in Colorado Springs, Colorado.

Success Rate

0%
Pass Rate

Teleport's interview process for their Senior Site Reliability Engineer roles in Colorado Springs, Colorado is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Teleport's Senior Site Reliability Engineer interview process in Colorado Springs, Colorado.

Teleport Work Experiences