Senior Front End Developer

• Languages: Javascript, Typescript, CSS
• Framework: React 17, knowledge of React hooks is important and knowledge about react context and redux is required too
• Packages manager: npm, yarn
• Knowledge of REST and GraphQL
• Control version: Git
• Hosting & deployment: AWS Amplify
• The automation UI was written in Vue therefore knowing about Vue may be a plus

How many hours are they expected to work? 

• - Full time position ( 40+ hours a week) 
•  

What hours should they work?

•  - Prefer 9-5 EST but there is wiggle room
•  

Will there be nights and weekends? 

• - Nights and weekends are not scheduled, however we are looking for someone that takes pride in their work and will lean in to hit a deadline or to fix a bug if it has a significant impact on the platform.
•  

Should they be expected to lead?

• - Yes, you should be expected to lead and to communicate/ cooperate with other devs as a team. Some coding might be alone but the hope of the app is that it all works seamlessly together and to ensure that there needs to be communication among all devs front end and back end. 
•  

Who will they report to?

• - They will report to Product OwnerRob and Product ManagerJulietta daily for standups and well as pushing tasks through the appropriate structure of review, QA, and production. 
• They will also report and check in with Client SuccessCourtney as we look to make the app have a seamless customer experience and customer value. The goal of Attribute should be to try and give as much value as quickly and easily as possible.

Will they work alone or in a team?

• In some spots they might be expected to work alone and on a separate sprint from others, however, everything needs to tie in and work together, because of that the developer must be team oriented in both development and problem solving.
• Additionally, there will be times that they should expect to work with people who are not particularly tech savvy ( ie. sales, marketing, customer success etc.) to collaborate on a specific feature to produce the best thing for the product.

Accountability

• The developer is both accountable for their code and the code of the team. They should take care and responsibility in the work that is done and if there are problems with the code in QA or production work as diligently as possible to fix that problem ( whether it is their code directly or not).
• As part of this all code will be attached from Github to Jira for developers to constantly upload their commits to Jira tasks
• A mistake is completely fine and expected, bugs are to be expected. What is asked is that you report it as soon as possible and are honest about it so that we can move forward in resolving it as soon as possible.

Customer, Usability, and Value Focused

• The end user of our product will be marketing professionals/head of marketing. At all times the developers need to take this into account and spend time thinking of the ease and the use cases that people will utilize their code or features in real life versus what is a way to make something work but in a vacuum. 

Quality focused

• Pushing out code is awesome, but if the code has a ton of bugs and does not do the required action that is practical for the user then it does not matter. We want a developer who is Quality focused and also hold their other developers accountable.

Focused on the whole 

• When producing a feature it is easy to sometime get sucked into how that features works in a vacuum. The developers need to be able to work together and understand the software architecture as a whole in order to make whatever feature they are working on be able to work with the other features that are built within the app ( and will be built or are on the roadmap for the future).

Creativity and Experimentation

• Developers are expected to work within structures, however, they are always encouraged to take time to think of creative solutions and to collaborate on new features or ways of making the product better.

Unfeathered, Honest, Respectful Communication

• Every developer should feel free to speak their mind in a respectful manner to other developers as well as anyone else in the entirety of the company. Any opinion, thought, or perspective will be listened to and valued. 

Next Man or Woman Up Mentality

• Never should anyone on the team defer a problem and say “ thats not my fault or problem”. We are one unit and one company. One problem is everyone's problem and should lean in to the “next man up philosophy” if you have the time and can help to fix the problem and bring it to a solution you should be willing to.

Upward Mobility and Vesting Opportunity

• This position will allow for upward mobility, increased responsibility, and for people who constantly go above and beyond an opportunity to vest into and own equity in the company