Front End Engineer
Hatch
Posted 4 years ago
Job Description
Hatch is looking for an addition to our front-end engineering team to help us take the company to the next level! This role will be working closely with a small team of experienced Javascript developers, focused on React and Redux. You will work closely with the Product and Design teams to implement world-class designs that wow our customers. If you love Javascript and React and have a knack for obsessing over design details, top-tier UX and writing self-documenting code that scales… we want to speak with you!
Responsibilities
-Developing new user-facing features in React + Redux
-Building reusable components that scale
-Translating designs into scalable, maintainable, self-documenting code
-Optimizing Javascript for maximum performance across a vast array of web-capable devices and browsers
Skills
-Strong proficiency in Javascript
-Thorough understanding of React and its core principles
-Experience with hooks (useState, useEffect, etc)
-Experience with state management architecture in Redux
-Experience writing ES6 syntax
-Familiarity with RESTful APIs
-Experience with front-end build tools such as Webpack and Parcel
-Experience with transpilers such as Babel or SWC
-Ability to understand business requirements and translate them into technical requirements
-Experience with benchmarking and optimization
-A working understanding of memoization and caching
-Experience with git for code versioning
-Exposure to Web Workers and Service Workers is a plus
In your first 30 days you will……
· Meet with members of Engineering team to get onboarded
· Start to understand our tech stack
· Meet with the Product team to get a better understanding of our customers
· Understand our clients - sitting in on, and listening to/watching sales presentations and implementation calls to best understand prospect and client wants/needs and common questions
· Meet with Leadership from Engineering, Product, Sales and Marketing to gain an understanding of the company and our values (affectionately termed “Hatchitudes”).
· Start to get integrated into our sprint process
After 90 days you should be able to……
· See your code in production!
· Fully understand the Hatch feature set
· Collaborate with Engineering team to solve problems
· Collaborate with product team on deliverables and timelines
· Coordinate with leadership on planning
After 6 months you will…….
· Own and manage your commits and timelines for work completion
· Have Ownership of Hatch’s features or products
· Be Fully integrated with the team
· Follow and embody the “Hatchitudes”
· Be a dependable leader and team player
· Be seen as a go-to person for the front-end
What we look for….
-3+ years of React experience
-3+ years of Redux experience
-5+ years of successful production Javascript
-Experience developing for mobile browsers (Safari + Chrome)
-Be able to explain what Webpack/Parcel and Babel/SWC are and how they relate
-Strong grasp of responsive design implementation using flexbox
-Strong grasp of functional programming concepts and why they are good (or bad)
Apply for this jobHatch is looking for an addition to our front-end engineering team to help us take the company to the next level! This role will be working closely with a small team of experienced Javascript developers, focused on React and Redux. You will work closely with the Product and Design teams to implement world-class designs that wow our customers. If you love Javascript and React and have a knack for obsessing over design details, top-tier UX and writing self-documenting code that scales… we want to speak with you!
Responsibilities
-Developing new user-facing features in React + Redux
-Building reusable components that scale
-Translating designs into scalable, maintainable, self-documenting code
-Optimizing Javascript for maximum performance across a vast array of web-capable devices and browsers
Skills
-Strong proficiency in Javascript
-Thorough understanding of React and its core principles
-Experience with hooks (useState, useEffect, etc)
-Experience with state management architecture in Redux
-Experience writing ES6 syntax
-Familiarity with RESTful APIs
-Experience with front-end build tools such as Webpack and Parcel
-Experience with transpilers such as Babel or SWC
-Ability to understand business requirements and translate them into technical requirements
-Experience with benchmarking and optimization
-A working understanding of memoization and caching
-Experience with git for code versioning
-Exposure to Web Workers and Service Workers is a plus
In your first 30 days you will……
· Meet with members of Engineering team to get onboarded
· Start to understand our tech stack
· Meet with the Product team to get a better understanding of our customers
· Understand our clients - sitting in on, and listening to/watching sales presentations and implementation calls to best understand prospect and client wants/needs and common questions
· Meet with Leadership from Engineering, Product, Sales and Marketing to gain an understanding of the company and our values (affectionately termed “Hatchitudes”).
· Start to get integrated into our sprint process
After 90 days you should be able to……
· See your code in production!
· Fully understand the Hatch feature set
· Collaborate with Engineering team to solve problems
· Collaborate with product team on deliverables and timelines
· Coordinate with leadership on planning
After 6 months you will…….
· Own and manage your commits and timelines for work completion
· Have Ownership of Hatch’s features or products
· Be Fully integrated with the team
· Follow and embody the “Hatchitudes”
· Be a dependable leader and team player
· Be seen as a go-to person for the front-end
What we look for….
-3+ years of React experience
-3+ years of Redux experience
-5+ years of successful production Javascript
-Experience developing for mobile browsers (Safari + Chrome)
-Be able to explain what Webpack/Parcel and Babel/SWC are and how they relate
-Strong grasp of responsive design implementation using flexbox
-Strong grasp of functional programming concepts and why they are good (or bad)