srakalogin.blogg.se - Observer system redux walkthrough

#OBSERVER SYSTEM REDUX WALKTHROUGH CODE#

With whatever you choose to walk us through, if you’re stuck where to start, choose a test case or how the project/library is initialized. As an example, with Mux you could compare what problems it solves or introduces versus the Go standard library.Īs an example for Ristretto perhaps you’d highlight it’s usage in other projects and some of the underlying caching mechanisms. For a backend position you may choose a library that you’ve used heavily, for example Mux or Ristretto.With Redux perhaps you want to dive into the internals and compare it’s technical proposition With a smaller library like DateJs you can walk us through it’s usage in other projects, what problems you’ve solved, how you’d approach testing it.

For a full-stack position you may choose a library that you’ve used heavily, for example DateJs.

To show us it’s usage contextually within other projects (these may be your personal projects too) and what problems you’ve solved with it historically. Walkthroughs can be done inĪny language, we do have a preference if possible that they are close to the domain you’d be working in. The following are sample ideas, the most important thing is you choose something that you are comfortable and familiar with.

Can effectively teach and share their knowledge.įor this interview you’ll drive a walkthrough of either a personal project or library of your choice.

Can tailor the technical depth and scope of a conversation dependent on the audience.

Have a time-efficient process for yourself and Sourcegraph.

Use the discussion as a proxy for technical aptitude and programming skills.

Allow a dialogue that simulates a technical discussion between your potential future peers.

Allow you as the candidate to focus on an area that you are comfortable in.

What do we want to be true about this interview? We need to help our team understand areas where we are the domain expert.We’re functioning in an asynchronous environment where clear communication is key.

#OBSERVER SYSTEM REDUX WALKTHROUGH CODE#

We’re often reading code we haven’t written.What is the day to day engineering experience at Sourcegraph? The following page details how we approach technical hiring within the Code Intelligence team instead of take home projects. Handbook / departments / engineering / dev / code-graph / code-intelligence / code-walkthrough Code walkthrough