Full Stack JavaScript Web Developer

This role is suitable for a Middle-level Full Stack JavaScript Developer with 3–5+ years of professional experience, particularly in React, TypeScript, Node.js, Express, REST APIs, AWS, and SQL/NoSQL databases. The candidate should be skilled in building responsive frontends, secure cloud-native microservices, CI/CD pipelines, authentication systems, and AWS integrations including Lambda, API Gateway, ECS, S3, and ideally OpenSearch or Kendra. They should be familiar with agile, client-facing delivery, translating designs into reusable components, developing search and data pipelines, participating in architecture and code reviews, and collaborating with product and design teams.

How would you structure a scalable React and TypeScript application for an enterprise client?

I would organize the application by business domain, using reusable, accessible components and clearly defined TypeScript interfaces. I would separate presentation, state management, API services, and routing concerns to improve maintainability and enable independent feature development.

What techniques would you use to improve React application performance?

I would measure performance using tools such as Lighthouse and React Profiler, then apply techniques such as code splitting, lazy loading, memoization, virtualization, and optimized data fetching. I would also minimize unnecessary renders and ensure assets and API responses are efficiently cached.

How would you design a secure REST API using Node.js and Express?

I would separate routing, controllers, services, and data-access layers, validate all inputs, and use centralized error handling. Security measures would include authentication and authorization, rate limiting, secure headers, parameterized queries, logging, and careful management of secrets.

When would you choose AWS Lambda and API Gateway over ECS for a backend service?

Lambda and API Gateway are well suited to event-driven, variable workloads where rapid scaling and minimal infrastructure management are priorities. I would choose ECS when the service requires long-running processes, specialized runtime configuration, predictable resource allocation, or more control over networking and deployment.

How would you model data across PostgreSQL, DynamoDB, and S3?

I would use PostgreSQL or RDS for relational data, transactions, and complex queries, DynamoDB for high-scale access patterns with predictable key-based lookups, and S3 for durable storage of documents and large objects. The design should begin with access patterns, consistency requirements, lifecycle needs, and compliance constraints.

How would you implement authentication and authorization with Amazon Cognito?

I would use Cognito User Pools for user authentication and JWT tokens for API access, validating token signatures, issuers, audiences, and expiration on the backend. Authorization would be enforced through groups, claims, scopes, or application-level policies rather than relying solely on frontend controls.

What is your approach to designing an Amazon OpenSearch indexing pipeline?

I would define an explicit document schema, mappings, analyzers, and searchable fields before indexing data. An ETL or event-driven pipeline could extract and transform source data, load documents in batches, handle retries and dead-letter cases, and support versioned mappings and reindexing strategies.

How would you decide between Amazon OpenSearch and Amazon Kendra for enterprise search?

OpenSearch is a strong choice when the team needs control over indexing, analyzers, relevance tuning, aggregations, and custom search behavior. Kendra is better suited to managed enterprise search across diverse content sources with built-in relevance features and natural-language query capabilities.

How would you build a semantic search pipeline using embeddings or LLM technologies?

I would chunk and normalize source content, generate embeddings, store them in a vector-capable search system, and combine semantic retrieval with keyword and metadata filtering. I would evaluate relevance with representative queries and consider access controls, freshness, hallucination risks, and protection of sensitive data.

How would you create a reliable CI/CD and testing strategy for this stack?

I would use GitHub workflows to run formatting, linting, TypeScript checks, unit tests, integration tests, and security scans before deployment. Deployments should use environment-specific configuration, infrastructure automation, staged releases where appropriate, observability, and automated rollback or recovery procedures.

RevStar, an AI-first innovation shop and AWS Advanced Tier Partner, is hiring a contract Full Stack JavaScript Web Developer to build enterprise-grade cloud applications for forward-thinking clients. You’ll develop React and TypeScript interfaces, Node.js and Express microservices, AWS serverless solutions, CI/CD pipelines, and advanced search and data workflows with OpenSearch, Kendra, SQL, NoSQL, and Cognito. This is a remote, US-based role, with preference for candidates in Eastern or Central Time; salary is not specified. Apply to work on cutting-edge AWS, data, and AI projects in a collaborative, client-facing environment with strong opportunities for growth.