Full Stack React Developer Job at Amtex Enterprises Inc in California
Amtex Enterprises Inc, California, MO, United States
Job Title: Full Stack React Developer
Location: EL Segundo CA (Hybrid, 3 days)
Duration: 10+ Months (Can Convert)
Rate: $55-65/hr on Vendor W2
Role Overview
We are looking for a Full Stack React Developer (Contract) to join an established team of five developers as a replacement hire. This role is front‑end‑focused with a strong emphasis on React expertise, while also requiring backend awareness to work effectively with APIs, cloud infrastructure, and CI/CD workflows.
Intake Notes
Looking for a highly qualified react dev with some backend understanding. If Sr React dev, should already understand working APIs, github
This role will be kind of like a Lead for front end. Manage and understand those capabilities. Current team doesn’t really have the react knowledge, they are all learning it. So this person can be more of a SME.
Nice to have is GraphQL /API experience and CI/CD understanding. These were identified as must‑haves.
We work with Drupal, nice to have.
Front‑end tech stack includes Storybook and Figma templates; a good developer can work with these.
Astro, an open‑source framework.
Project: converting sites previously built on Drupal to a headless architecture. The team is building public sites in an Atlas‑style fashion.
GraphQL would be helpful.
New development; existing public site is being converted to Atlas.
Astro is a 70% must‑have; knowledge gaps will be addressed.
70% front end / 30% backend; GitHub proficiency is a must‑have.
5–8 years of experience. Expectation includes solid understanding of CI/CD pipelines, GraphQL, and REST APIs.
Nice to have: AWS cloud services knowledge.
Ideally 4–5 years with React, but 2–3 years elsewhere within the 5–8 year range is acceptable.
Relevance to past projects matters.
Core Responsibilities & Expectations
Strong emphasis on:
React
JavaScript fundamentals
Full‑stack awareness required, but role is frontend‑heavy
Expected to:
Be highly motivated
Be self‑sufficient
Ramp up quickly with minimal hand‑holding
Team:
5 developers
Role includes a frontend lead capacity
Not a people manager
This role will:
Oversee frontend source code
Guide frontend best practices
Support team transitioning to new tech stack
Project Scope & Work Type
New development, not maintenance‑heavy.
Primary initiative:
Converting public‑facing sites from a Drupal monolith to a headless architecture
Frontend rebuilt largely from scratch
Maintenance handled by other developers
Tech Stack & Requirements
Must‑Haves
React (strong proficiency)
JavaScript
Experience working with
APIs
Git / GitHub
CI/CD pipelines (GitHub Actions)
Strongly Preferred / Nice‑to‑Haves
Astro framework (used instead of Next.js)
Performance‑oriented static rendering
70% must‑have, but flexibility given it’s a newer framework
GraphQL (helpful, not mandatory)
Drupal (nice to have)
Tailwind CSS
Storybook
Figma (design integration)
AWS cloud services (nice to have)
Frontend vs Backend Balance
70% frontend / 30% backend
Backend expectations are conceptual and integrative, not deep backend ownership: REST APIs, GraphQL, CI/CD concepts, understanding of backend infrastructure
Interested candidates send your resume to alex@amtexenterprises.com
#J-18808-Ljbffr
Location: EL Segundo CA (Hybrid, 3 days)
Duration: 10+ Months (Can Convert)
Rate: $55-65/hr on Vendor W2
Role Overview
We are looking for a Full Stack React Developer (Contract) to join an established team of five developers as a replacement hire. This role is front‑end‑focused with a strong emphasis on React expertise, while also requiring backend awareness to work effectively with APIs, cloud infrastructure, and CI/CD workflows.
Intake Notes
Looking for a highly qualified react dev with some backend understanding. If Sr React dev, should already understand working APIs, github
This role will be kind of like a Lead for front end. Manage and understand those capabilities. Current team doesn’t really have the react knowledge, they are all learning it. So this person can be more of a SME.
Nice to have is GraphQL /API experience and CI/CD understanding. These were identified as must‑haves.
We work with Drupal, nice to have.
Front‑end tech stack includes Storybook and Figma templates; a good developer can work with these.
Astro, an open‑source framework.
Project: converting sites previously built on Drupal to a headless architecture. The team is building public sites in an Atlas‑style fashion.
GraphQL would be helpful.
New development; existing public site is being converted to Atlas.
Astro is a 70% must‑have; knowledge gaps will be addressed.
70% front end / 30% backend; GitHub proficiency is a must‑have.
5–8 years of experience. Expectation includes solid understanding of CI/CD pipelines, GraphQL, and REST APIs.
Nice to have: AWS cloud services knowledge.
Ideally 4–5 years with React, but 2–3 years elsewhere within the 5–8 year range is acceptable.
Relevance to past projects matters.
Core Responsibilities & Expectations
Strong emphasis on:
React
JavaScript fundamentals
Full‑stack awareness required, but role is frontend‑heavy
Expected to:
Be highly motivated
Be self‑sufficient
Ramp up quickly with minimal hand‑holding
Team:
5 developers
Role includes a frontend lead capacity
Not a people manager
This role will:
Oversee frontend source code
Guide frontend best practices
Support team transitioning to new tech stack
Project Scope & Work Type
New development, not maintenance‑heavy.
Primary initiative:
Converting public‑facing sites from a Drupal monolith to a headless architecture
Frontend rebuilt largely from scratch
Maintenance handled by other developers
Tech Stack & Requirements
Must‑Haves
React (strong proficiency)
JavaScript
Experience working with
APIs
Git / GitHub
CI/CD pipelines (GitHub Actions)
Strongly Preferred / Nice‑to‑Haves
Astro framework (used instead of Next.js)
Performance‑oriented static rendering
70% must‑have, but flexibility given it’s a newer framework
GraphQL (helpful, not mandatory)
Drupal (nice to have)
Tailwind CSS
Storybook
Figma (design integration)
AWS cloud services (nice to have)
Frontend vs Backend Balance
70% frontend / 30% backend
Backend expectations are conceptual and integrative, not deep backend ownership: REST APIs, GraphQL, CI/CD concepts, understanding of backend infrastructure
Interested candidates send your resume to alex@amtexenterprises.com
#J-18808-Ljbffr