Looking for Senior TypeScript Developer || Atlanta/Columbus/Dallas (Hybrid)

[Himanshu Sharma]

Title:  Senior TypeScript  Developer

Location:  Atlanta/Columbus/Dallas (Hybrid)

Duration: Long Term Contract

Job Description:

 

•  Develop and maintain responsive, high‐performance web applications using Angular (v10+) or React (v16+) with TypeScript on the front end.
• Build and integrate RESTful/GraphQL APIs using Node.js (Express, NestJS, or similar) with strong TypeScript usage.
• Collaborate with business analysts and product owners to translate insurance‐domain requirements into technical designs and UIs.
• Write clean, modular, reusable, and testable TypeScript code across both front‐end and back‐end and participate in peer code reviews.
• Optimize application performance, accessibility, and cross‐browser compatibility across SPA and API layers.
• Integrate with databases (SQL/NoSQL), third‐party vendor APIs, and messaging systems in a cloud‐native environment.
• Support incident triage, debugging, and production deployments in collaboration with DevOps and SRE teams.

Mandatory Requirements (8+ Years)

• 8+ years of professional software development experience, with at least 5+ years using TypeScript and Node.js in production systems.
• Strong TypeScript expertise across both front‐end and back‐end (modules, async/await, generics, interfaces, decorators, etc.).
• Back‐end experience with Node.js (Express, NestJS, or similar) and RESTful/GraphQL API design.
• Front‐end experience with one of the following:
• Angular (v10+) using TypeScript, RxJS, modules, routing, and state management concepts.
• React (v16+) using TypeScript, Hooks, and state management (Redux, Context, or similar).
• Solid understanding of modern web architecture, SPA patterns, and API‐centric design.
• Experience with Git, branching strategies, and working in Agile/Scrum environments.
• Familiarity with cloud‐native environments (AWS/Azure/GCP) and basic CI/CD / DevOps practices.

Strong problem‐solving skills and comfort debugging complex issues across full stack