IT - Senior Consultant | Reactive Programming | react JS

POC:
Brenda

•

Job title:

UI Lead Developer

• Duration of the project: 7 months to 1 year. Client might extend it based on requirement and candidate's performance

• Work Location with Zip code:
Charlotte, NC, 28217, US

• Please confirm if this would be onsite from day one OR Initial remote for 2-3 months and then expecting candidate to work from office OR 100% Remote:
Onsite from day one

• Is this an 100% remote role? No, 3 days a week from client office

• Vendor Rate Range (min to max rate you can offer): 6

XXX - 7

XXX per hour

• Do you have budget approved for this request? This is confirmed demand from the client

• Minimum years of experience required: 8 years of experience including leading/handling the team

• Would you require the candidates to meet you for in person interview? Yes. There will be three rounds of interviews. One will be internal. Two client rounds, first will be virtual and second will be in person.

• Is Skype/Web Ex interview, OK? Internal and Client first round will be MS Teams.

• Please Confirm Must Have Skills (TOP 3 SKILLS) - React.js, Type Script, Redux and Redux Sagas

Lead Level Engineer Responsibilities

Core Responsibilities
UI and API Leads are responsible for ensuring technical execution aligns with established patterns, frameworks, and guidelines. They are expected to identify gaps in those standards and collaborate with Architects to clarify or expand them. They lead by example, writing production-grade code, reviewing pull requests, and handling complex or ambiguous implementation work. In this capacity, they act as a first line of defense for code quality and are the go-to individuals when incidents or unclear behaviors arise in their domain.

As part of their role, leads are required reviewers for all production code changes. When faced with unclear guidance, they are empowered to make context-aware decisions. If the situation exceeds their depth or scope, they are expected to engage with Architects for support. Code quality should be deciding factor in reviews. Architects may at will participate in some of those reviews (especially for new applications), and verify the review quality.
In addition to day-to-day engineering, UI and API Leads are responsible for contributing to the Architecture Documentation for new features when those features can be implemented using known approaches, building a traceable knowledge base. Proposed solutions are expected to be reviewed and approved by Architects.

Leads also participate in Discovery and Design phases to provide input on technical feasibility and highlight any limitations in proposed solutions. That said, the majority of their time - approximately 80% - should remain focused on implementation and engineering work, with no more than 20% devoted to product and design discussions.

UI and API Leads also serve as the primary point of contact for engaging with the Architecture team on reusable components, unknown capabilities, or anticipated technical needs. They are expected to initiate those conversations early, recognizing that upstream architectural solutions require time to develop and validate.

Leads are integral to the production deployment process. In instances where a lead cannot be present for a scheduled deployment, it is their responsibility to ensure a designated and qualified representative attends in their stead. The Lead should notify their manager of the conflict for transparency and to help managers in their work. Leads are accountable for addressing and resolving any issues that arise following the deployment of a solution.

Leads are expected to prioritize and actively monitor the performance of the solutions under their purview, ensuring optimal functionality and efficiency. In case performance criteria are vague, Leads should collaborate with Engineering Manager and Architect to define improvement points and make a plan how to get there.

Our basic requirements for UI developers are:
1. We're looking for recent experience with pure React+Typescript, with best practices from React 18 (like no CLASSical components or CLASSical HOCs). Frameworks on top of React (like NextJS) aren't what we're looking for.
2. No frameworks.…