Full Stack Engineer

American IT Systems; Palo Alto (CA); On-site; USD 180,000 - 260,000; Full time

Job summary

We are looking for experienced full stack contractors to build production-grade web applications and APIs. You will own features end to end - from database schema through backend services to the user interface.

This is a hands-on build role for engineers who are comfortable working through ambiguity, shaping the design as much as writing the code, and operating as an owner rather than a ticket-taker. Candidates should have strong frontend and backend skills, including JS/React, Python with

Qualifications

• 8+ years hands-on full stack development.
• Proficient in Python and REST APIs.
• Experience with relational databases and schema design.
• Strong frontend skills with JavaScript/React.
• Familiarity with DevOps and CI/CD.

Responsibilities

• Own features end-to-end from database schema to UI.
• Build production-grade web applications and APIs.
• Collaborate with security/AI teams to ship robust software.
• Identify scalable solutions and design trade-offs.
• Write tests for reliability and maintainability.

Skills

JavaScript (ES6+)

React

Python

REST API design

SQL databases

System design

DevOps basics

Testing (unit/integration)

Claude Code awareness

Tools

Docker

Git

Swagger/OpenAPI

CI/CD

Linux

Job description

About the Client

Client is a Security and AI company. They help organizations achieve cyber resilience by securing their data across enterprise, cloud, and SaaS environments - protecting against ransomware, accelerating recovery, and turning data into intelligence. As AI reshapes how enterprises operate and defend themselves, our AI Engineering team builds the agentic systems that make our platform smarter, faster, and more autonomous.

ZIP Code - Palo Alto, CA 94304

Full Stack Engineer

Experience required: At least 8+ years handson in full stack development.

Role Summary

We are looking for experienced full stack contractors to build production-grade web applications and APIs. You will own features end to end - from database schema through backend services to the user interface. This is a hands-on build role for engineers who are comfortable working through ambiguity, shaping the design as much as writing the code, and operating as an owner rather than a ticket-taker.

Must-Have Skills

Frontend

• Strong JavaScript fundamentals (ES6+, async/await, closures)
• React experience preferred (hooks, state management, component architecture)

Backend

• Proficient in Python, writing production-grade code
• Hands-on experience with FastAPI or Flask for building REST APIs

Database

• Experience with relational databases (PostgreSQL, MySQL, SQL Server, or equivalent)
• Good understanding of schema design, joins, indexing, and query optimization

Architecture & Problem Solving

• Ability to think through system design and build scalable solutions
• Strong analytical mindset to break down complex or ambiguous problems

Good-to-Have Skills

• Experience with Claude Code or other AI-assisted development tools - extra points for this
• desktop app based on Electron framework - Extra points for this
• Agentic Frameworks (ADK, Langraph )
• API documentation (Swagger / OpenAPI)
• Git and version control best practices
• Basic DevOps awareness (Docker, CI/CD)
• Testing experience, both unit and integration

Behavioral Expectations (Non-Negotiable)

These are weighed equally with technical skill. Candidates who are strong engineers but weak here will not be fit.

Expectation

What it looks like in practice

Proactive communication

Shares updates without being asked and flags blockers early

Asks the right questions

Clarifies requirements upfront before jumping into implementation

No working in silos

Collaborates openly, seeks feedback, and loops in stakeholders regularly

Ownership mindset

Treats the project as their own rather than just completing tickets

Transparency

Speaks up when something is unclear instead of making assumptions

What Success Looks Like

• Features shipped end to end - schema, API, and UI - with minimal hand-holding
• Requirements clarified early, so rework is rare
• Blockers surfaced the day they appear, not at the end of the sprint
• Code that others can read, test, and extend