We are obsessed with Web Performance.
- Talking about your work - we love open source software, we heavily use them, and talking about how we use them is the least we can do to help the community.
Skills & Experience:-
- 4-5 Years of Experience
- Work Experience with TypeScript
- Deep understanding of how the browsers work.
- Regard for optimizations that focus to deliver content to the user as quickly as possible.
- Awesome Debugging Skills.
- Passion to write automated tests to verify the working of libraries (You can’t possibly verify things on all devices and on all browsers manually). We use Cypress for this.
- Understanding the similarities and differences across browsers (young and old).
- Knowledge of high-level programming concepts like promises, data-binding.
- Passion to stay up to date with the constantly evolving world of front-end development.
We have the following levels within different grades in our engineering team
Senior Software Engineer 1
Senior Software Engineer 2
Lead Engineer 1
Senior Engineering Manager
Chief Technology Officer
Expectations from you to succeed in this role
We have identified some must-have expectations from this role. As a senior software engineer, you will be meeting expectations (which is a good indicator of your performance) if you qualify for all must-have expectations for most sprints. Differentiators are not explicit expectations but would exceed expectations from this role and would likely put you as a great performer.
Timely delivery (Must Have)
- The most important expectation from any individual. This expectation is independent of the experience level.
- Can be defined as the delivery of the tasks within the agreed time frame along with agreed quality standards.
- Can be broadly categorized into the following streams:
- Feature Requests - To deliver new feature requests as per the agreed scope at the start of the sprint. Definition of Done (DOD) still needs to mature.
- Customer Bugs - To be delivered in a linked sprint. In certain cases, some critical bugs can take the highest priority.
- Tech Debt - Timely delivery of tech debt tasks with scope finalized at the start of the sprint. Again, quality standards must be followed.
Ownership & Accountability (Must Have)
- This expectation will vary according to the experience level as well as the role.
- Junior team members are expected to deliver their tasks with help from others.
- Senior team members are expected to help junior team members as well as deliver their own tasks. They are also expected to take ownership of the end-to-end delivery of projects including stakeholders management.
- Some individuals performing some specific roles like Scrum Masters are expected to perform role-specific duties.
Quality delivery (Must Have)
- Deliver tasks adhering to the existing quality standards.
- Quality standards may vary from service to service. Everyone should agree on the benchmark and should follow it strictly
- Dev Testing is very crucial before handing over anything for QA. Any obvious misses in requirements or bugs should be considered as bad quality delivery.
- Repeated misses in pull requests will be considered bad quality
Teamwork (Must Have)
- Coordination among team members during sprints.
- How well team members can resolve blockers without external help.
- Effective communication between team members. If things are getting delayed because of poor communication, it’s a bad sign.
- For senior members, coordination with other teams i.e. Product, Design, other stakeholders is also important
- Ideas to improve current architecture and to take the ideas to completion
- If something crucial is being reported, how fast someone is resolving it
- How are people reacting to their free time? Are they always trying to utilize it by working on things from backlog or tech debt items?
Engineering Performance Process
We follow a continuous performance cycle inline with our sprint cycles. A 360 review based on agile principles is rolled out after every two sprints that covers feedback on and from scrum masters and peers.
A formal review is kicked off twice a year and the feedback from sprint cycles is accommodated for a holistic evaluation.
Its not all work!
Between work and learning, we don’t forget to have fun!
→ As an engineering team member working remotely, you get an allowance of 35k INR to set up your home office.
→ Health insurance of 5 Lakhs for you and dependents
→ A self-initiated learning and development budget of $400/year for training courses and online certifications
→ Executive coaching for engineering leaders
→ Access to free unlimited mental health sessions