Generalist Quiz -
You scored between the 80th and 100th percentile
of all the engineers who took the quiz on our platform.
Performance
Candidates
You’re eligible for FastTrack
Quiz taken on:
ELIGIBLE FOR FastTrack
Your performance
You are strongest in
Back-end Web
and could improve inProgrammatic 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
5 / 5
Back-end Web
Excellent
Back-end web, for our purposes, means web development on the server side, not in a user's browser. Important topics include databases, HTTP, authentication, and API creation. This is a very broad field that encompasses a large percentage of engineering jobs, and it's a good place to start if you want to maximize your chances of finding work.
Your score
Engineers who get a score of 3 or above on back-end web know most of what they need to build basic applications, but often struggle with performance improvements and scaling. They'll benefit from reading up on caching and database optimization.
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.
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!
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
More from our blog
Visit BlogProgramming Interview Questions Are Too Hard and Too Short
By Charles Treichler on Feb 18, 2019
_tl;dr Programming interview questions can feel unnecessarily difficult. Sometimes they actually are. And this isn't just because they make interviews excessively stressful. Our data shows that harder programming questions actually do a **worse** job of predicting final outcomes than easier ones._
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.