Med/Senior Fullstack Engineer

Javascript
Experience Woven for Free

This fullstack engineer understands web architecture and APIs as a connected system. This engineer can be productive writing code for both the front end and backend. They’re also an effective code reviewer, leveling up their teammates and driving quality.

Capabilities
Debugging
Technical Communication
Systems Thinking
Backend Programming
Frontend Programming
Experience Woven for Free
Real assessment scenarios for candidates applying to this role:

Systems Debugging (Two-Part Scenario)

Time Limit: 20 min

A new (and very important) customer launched today. We’re seeing serious performance problems loading their admin dashboard. This is impacting service for other customers. We’ve identified several bottlenecks. Help your team brainstorm ideas on what to do by drafting an email.

Expand to read the full scenario...
Part I: Brainstorming
View real candidate answers to this scenario:
Here’s the candidate’s sample brainstorming:
Let’s quickly deploy a feature flipper around that expensive table/report and flip it off for this large customer until we can get a bigger fix in place
Is that table actually important for this page? Could we hide the expensive parts behind another click?
Are we hitting a DB index with the query? Modify the query or add an index, possibly multi-column
Can we batch API requests?
90
Woven Analysis
Analysis by:
Matt J.
John W.

What we liked:
Suggested a very quick fix idea to mitigate impact for other customers

Suggested ideas in 5 out of the 6 area of the system we look for, including: hardware, DB/Query optimization, batching, caching, cutting scope

What we look for that we didn’t see:
Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Receive candidate scores automatically in your ATS and Slack:
Woven Slackbot
10:24 AM
🔥  This candidate scored an 90 out of 100!
Part II: Sample Email
View real candidate answers to this scenario:
Here’s the candidate’s sample email:
Development Team
dev-all@acme.com

Hi team,

Let’s quickly deploy a feature flipper around that expensive table/report and flip it off for this large customer until we can get a bigger fix in place

Is that table actually important for this page? Could we hide the expensive parts behind another click?

Are we hitting a DB index with the query? Modify the query or add an index, possibly multi-column

Can we batch API requests?

Let’s avoid (N+1) queries on that table…

87
Woven Analysis
Analysis by:
Matt J.
John W.

What we liked:
Suggested a very quick fix idea to mitigate impact for other customers

Suggested ideas in 5 out of the 6 area of the system we look for, including: hardware, DB/Query optimization, batching, caching, cutting scope

What we look for that we didn’t see:
Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Didn’t suggest strategies for dealing with slow/degraded 3rd party services.

Receive candidate scores automatically in your ATS and Slack:
Woven Slackbot
11:49 AM
🔥  This candidate scored an 87 out of 100!

Code Review Part 1: Frontend pagination

Time Limit: 20 min

Perform code review for both a frontend and backend pull request related to the complex dashboard performance improvements. After restoring performance for other customers, your team prioritized two performance improvements. Both of these pull requests are up for your review. Review frontend pull request that adds support for server-side pagination.

Expand to read the full scenario...
View real candidate answers to this scenario:
Here’s the candidate’s sample email:
7
8
      "GlossList": {
          "GlossEntry": {

Matt J.
Nam porttitor blandit accumsan. Ut vel dictum sem, a pretium dui. In malesuada enim in dolor euismod, id commodo mi consectetur.

15
16
       "para": "A meta-markup language, used to create markup languages such as DocBook

Matt J.
Nam porttitor blandit accumsan. Ut vel dictum sem, a pretium dui. In malesuada enim in dolor euismod, id commodo mi consectetur.

56
Woven Analysis
Analysis by:
Matt J.
John W.
What we liked:
   •    What we Gave feedback on critical bug
   •    Gave defensive coding feedback
            ⁃    lack of error handling
   •    Gave feedback on idiomatic usage
            ⁃    setState():

What we look for that we didn’t see
   •    Any positive feedback for work done well
   •    Any indication of importance of feedback that is blocking versus optional
Receive candidate scores automatically in your ATS and Slack:
Woven Slackbot
10:24 AM
🛑  This candidate scored an 56 out of 100.

Programming with a Business Algorithm and Data

Time Limit: 20 min

Evolve existing code to meet a new requirement that adds several layers of abstraction. After stabilizing performance of the admin dashboard, it’s time to update the departments report to support a new feature. We’ve added groups to our role-based access control system. You made great progress this morning and are diving into make more progress before your team retro in 40 minutes.

Expand to read the full scenario...
This scenario response is hidden. Sign up to reveal our full assessment.
Sign Up Free