Taro Logo

Software Engineer Interview Experience - United States

December 29, 2021
Negative ExperienceNo Offer

Process

The interview was a two-week exercise that is published on their GitHub account. It consists of candidates writing a design document and implementing three Golang-based software components. They provide a Slack channel on which candidates can interact with the panel. The panel reviews the design document using Google docs, and the panel reviews the implementation using GitHub PRs.

Questions

The following is an excerpt from the exercise description:


Library Worker library with methods to start/stop/query status and get the output of a job. Library should be able to stream the output of a running job. Output should be from start of process execution. Multiple concurrent clients should be supported. Add resource control for CPU, Memory and Disk IO per job using cgroups. Add resource isolation for using PID, mount, and networking namespaces.

API GRPC API to start/stop/get status/stream output of a running process. Use mTLS authentication and verify client certificate. Set up strong set of cipher suites for TLS and good crypto setup for certificates. Do not use any other authentication protocols on top of mTLS. Use a simple authorization scheme.

Client CLI should be able to connect to worker service and start, stop, get status, and stream output of a job.

When they say that this is a "two-week exercise," they mean that it's a two-week, full-time commitment. They do not take into consideration that candidates currently have full-time jobs. I took this as an indication that they have no respect for employees' work/life balance.

For the implementation component, I found the review comments to be very authoritarian with no room for open discussion, and certainly no room for the candidate to contribute any ideas/approaches beyond those of the reviews'. If you organize your solution in a way that differs from that of the reviews, you're wrong. If you test your code in a way that differs from the reviewers, you're wrong.

All of my interactions with the team on the Slack channel were very dry. There was no humor or any sort of friendly comments/conversation. If I asked a question, someone from the panel would answer the question succinctly. No more, no less.

I appreciated the opportunity to have this interaction with the team tremendously. While the exercise is clearly designed to enable the panel to evaluate candidates' fitness for the role, it's also an awesome opportunity for candidates to evaluate the team's fitness as colleagues. What I saw gave me serious reservations about the team/company culture.

I completed the exercise but did not receive an offer. Based on my experience during the interview process, I had already decided to decline an offer if one was made.

Was this helpful?

Interview Statistics

The following metrics were computed from 10 interview experiences for the Teleport Software Engineer role in United States.

Success Rate

0%
Pass Rate

Teleport's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive20%
Neutral0%
Negative80%

Candidates reported having very negative feelings for Teleport's Software Engineer interview process in United States.

Teleport Work Experiences