Development Assignment: Front-end engineer

We ship high quality code, we’re highly confident in providing the best experience for our users, and we deliver frontend stories to contribute to the team’s success and keep progress moving forward.


Expectations / Description

  • We ship high quality code
    • Minimal (less than average) number of regrettable recycles on stories owned. For example:
    • ~90% test coverage
      • So we can (Shared) increase confidence that our code will work as expected
      • Not-you, engineering experience
    • Performance concerns
    • Security concerns
    • Style guide concerns
    • Architectural pattern concerns
    • Hygienic (common conventions) concerns
  • We’re highly confident in providing the best experience for our users
    • Minimal (less than average) number of regrettable remediations on stories owned. For example:
    • Performance issues
    • Authorization issues
    • Functionality issues
    • Error handling issues
  • Delivers frontend stories to contribute to the team’s success and keep progress moving forward
    • Better than average cycle time of active states (as defined in OurGruuv)

Requirements

Configuration Health

  • ✅ Has 8 Abilities
  • ✅ Is a part of 20 Positions
  • ✅ Has been referenced in 7 pieces of public recognition
  • ℹ️ Fewer than five people (1) have reacted to this Assignment. To ensure anonymity, analysis will only appear after at least five people have reacted.
  • ℹ️ 7 people have an official rating on this Assignment: 3 people are working towards meeting expectations and 2 people are meeting expectations
  • ⛔️ Last updated: over 4 years ago
  • ℹ️ Never conversed about

Examples / Observations

  Observation created over 4 years ago

Double shout out to our residential front end wizards (or wizard and witch, if you prefer) and "honorary" Practice members, Carolyn and Ethan, for super-ly putting the team first!

When Ellie was here, they both jumped in to help her sort through front end issues and learn the ropes of our codebase, and now that John and I don't have our own React-Gandalf to look to, they have both made time (lots of it) to answer questions and help us navigate through some weird bugs on a difficult project.

Carolyn and Ethan, we really appreciate how you've generously given us your time and have been so positive and helpful!

  Observation created about 5 years ago

Donnie is also very patient with me. He has been a great (frontend) partner on a shared project. He’s always been able to help me improve something I’ve written and or walk me through some of his tips on reviewing. I really appreciate the atmosphere you bring any time we collaborate as well. Thanks

  Observation created about 5 years ago

This is long overdue. Ethan is always very patient with me and no matter how trivial of a question I have, he always gives me his full attention and time. I have been trying to enhance my frontend skills and he is always very willing to help out and I really appreciate it.

  Observation created almost 6 years ago

I am grateful for how these 4 have been communicating on this project. This is a complex project for a variety of reasons. We are splitting up the frontend and the backend. Linking elements in our app is a difficult endeavor. The way these four have communicated to one another and to me has been such a joy. Whether it be Waseem posting killer updates in the channel, Joshua and Joseph presenting their findings on technical deep dives, or Ethan walking me through expectations on epic breakdown, everyone has chipped in to really get this off the ground.

I have been inspired to bring the level of clarity I have found here in other aspects of my job.

  Observation created almost 6 years ago

Last week, I did a code review for Conlin. In the PR description, he did a phenomenal job at leaving detailed testing steps and notes around why the story was necessary. Beyond that, however, he also went out of his way to thoroughly talk through the issue on a deeper level. He explained the research he did on the problem, potential solutions (and why they wouldn't work), his decided solution (and why it does work), as well as the history and potential future of the problem. As both a reviewer and fellow engineer, I was really impressed by how much thought and effort went into this.
While I already find myself aiming to be as clear and informative as possible in my PR descriptions, seeing this inspired me to raise my standard going forward, and left me feeling grateful to work with Conlin.

PR of Reference - https://github.com/lessonly/lessonly/pull/7482

Official Front End Engineers

Manager Details:
This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Teams needing a Front-end Engineer

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Positions that reference being a Front-end Engineer

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Conversations about Front-end engineer

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Embed code

<iframe src="http://ourgruuv.com/our/roles/2?embed=true&name=front_end_engineer&organization=lessonly"></iframe>