Back to dashboard

Generalist Quiz -

You scored between the 80th and 100th percentile

of all the engineers who took the quiz on our platform.

Performance
Candidates

80th - 100thpercentile

You’re eligible for FastTrack
Quiz taken on:

ELIGIBLE FOR FastTrack

Your performance

You are strongest in
Back-end Web
and could improve in
Programmatic Problem Solving
.
The generalist track covers a range of subjects, but most emphasizes general application development, particularly the back-end of web applications. When you took it, you demonstrated particular strength in Back-end Web. If you want to improve your performance on this track, we recommend starting with Programmatic Problem Solving.
Strongest
Back-end Web
Low-level Systems
Academic CS
System Architecture
Programmatic Problem Solving
Weakest

Resources to improve in ...

System Architecture
System architecture is particularly important for senior engineers, who are expected to take on design and leadership roles. But some understanding of the underlying principles can be useful for understanding the context in which smaller-scale implementation work takes place.
This gist Reddit lessons from scaling mistakes
Programmatic Problem Solving
Gaining better intuitions for programatic problem solving is often a matter of developing stronger instincts for code, and one of the best ways to do that is to practice writing programs, and then taking the time to dive deep into the details of why each solution worked. Check our these sources of small problems to practice with!
LeetCode Project Euler

Sample Questions

Sample question #2

Which of the following is NOT one of the claimed benefits of a microservice architecture?

Select the correct answer:

Continuous delivery or deployment
Lower network latency
Improved modularity
Resiliency against failures

Explanation

Quiz area:

System Architecture

A microservice architecture involves many services that are each responsible for a small amount of functionality.

These services must communicate with each other over a network; since such communication would not be necessary in other architectures (e.g. monolithic), lower network latency is not a claimed benefit of microservice architecture.

Since the services are mostly self-contained, there’s less coupling and improved modularity between the various services.

By distributing functionality among multiple services, failure in part of the system does not necessarily result in failure of the entire system; this graceful degradation can lead to improved resiliency against failures. Furthermore, a microservice architecture makes it easier to introduce redundancy for critical components.

Finally, since it’s easier for developers to work on a particular service without affecting the rest of the system, it’s also easier to achieve continuous delivery.

More from our blog

Visit Blog
Common Interviewing Mistakes that Engineers Make
By June Kreml on Oct 29, 2018
Every engineer has bombed an interview. Sometimes even very talented engineers unexpectedly bomb them, and this can be really frustrating for all parties involved. As one of Triplebyte’s content writers, I’ve read interview notes on hundreds of successful candidates and hundreds of candidates who didn’t make it through our process. Although we've put a lot of effort into designing a background-blind technical screen, our process is still probabilistic and sometimes things other than raw engineering talent impact outcomes. Sometimes candidates make mistakes which make it impossible for us to accurately assess their ability. What follows is based on my own observations and those of our interviewing team, who have been doing this for even longer than I have.
How to Pass a Programming Interview
By Ammon Bartram on Sep 14, 2017
Being a good programmer has a surprisingly small role in passing programming interviews. To be a productive programmer, you need to be able to solve large, sprawling problems over weeks and months. Each question in an interview, in contrast, lasts less than one hour. To do well in an interview, then, you need to be able to solve small problems quickly, under duress, while explaining your thoughts clearly. This is a different skill. On top of this, interviewers are often poorly trained and inattentive (they would rather be programming), and ask questions far removed from actual work. They bring bias, pattern matching, and a lack of standardization.