Frontend Engineer - remote

vidIQ
Posted 4 years ago
We Work Remotely

What you will be doing


As part of our growing Frontend Team, you’ll work with team members at all levels to improve our existing products and develop new ones.

The tools we use most heavily right now are React and JavaScript, though we still have Backbone and Flux in some of our codebases as well. We use Asana for project management, GitHub for code reviews, and Slack for daily communication. We also have a Rails API and consider it a major bonus if you have experience working on Rails applications.

Some projects you may work on include:
  • Research and implement architectural changes such as migrating our browser extension to Redux.
  • Help measure the effectiveness of certain features by building a reusable analytics module to use across our products.
  • Improve our brand and usability by reskinning components according to our new design system.
  • Make our products more reliable by writing integration tests to cover common user workflows.
  • Simplify our API interactions by building a GraphQL layer.
  • Level up the team by reviewing code and suggesting improvements.
Over time, you’ll become an owner of some areas of our codebase and have the freedom to improve them as you see fit.

Who you are
  • A builder - Frontend development is full of helpful tools, libraries, and patterns, and you enjoy using these to build products people will love. You like new challenges and strive to ship new features to customers on a regular basis.
  • Life long learner  - You enjoy keeping up with the latest trends in frontend space. If a project uses a framework that’s new to you, you dive into the docs and tutorials to figure it out.
  • Have an owner mentality - When bugs appear, you document and fix them. When projects are too complex, you work with others to refine the scope until it’s something you believe can be built in a reasonable amount of time and maintained in the long run.
  • Care about code quality - You believe simple is better and strive to write code that is easy to read and maintain. You consider edge cases and write tests to handle them. When you come across legacy code that is difficult to understand, you add comments or refactor it to make it easier for the next person.
  •  Balancing Act - Great products must balance performance, customer value, code quality, dependencies, and so on. You know how to consider all of these concerns while keeping your focus on shipping things.
  • The great communicator - If a project is off-track, you bring it up proactively and suggest ways to simplify and get things going. You proactively share status updates without being asked and strive to keep things as honest and transparent as possible.