1

Python React Full Stack Jobs in Phoenix, AZ (NOW HIRING)

Full Stack Engineer

AZ · On-site +1

Full-Stack Software Engineer On-site, Tempe, AZ About the role Mint Cannabis runs 39+ stores across ... Strong with TypeScript and comfortable in Python (or strong in Python with TS fluency) * Shipped to ...

Python) and front-end frameworks/libraries (ex: React, Angular, TypeScript/Modern Java Script) • ... Qualifications: • Full Stack Development • Proficiency with programming language (ex: Python ...

Work on all parts of the stack, from AWS / GoLang / PostgreSQL to EmberJS / React or even React Native. * Take full ownership and responsibility for building, shipping, and maintaining core Moov ...

Required : • Experience in Full-stack software engineering with proficiency in Java/Python, and Angular. • Experience building and scaling applications on AWS. • Experience in Java Full Stack ...

Lead end-to-end design and development of modern full-stack solutions using Java (Spring Boot), React * Define and enforce coding standards, best practices, and architectural patterns. * Make key ...

Job Summary : Diverse Lynx is seeking a Full Stack Developer with strong experience in .NET and React. The role involves developing high-quality full stack applications, building secure ...

next page

Showing results 1-20

Python React Full Stack information

See Phoenix, AZ salary details

$59.1K

$128.9K

$182.2K

How much do python react full stack jobs pay per year?

As of Jul 10, 2026, the average yearly pay for python react full stack in Phoenix, AZ is $128,881.00, according to ZipRecruiter salary data. Most workers in this role earn between $108,200.00 and $149,900.00 per year, depending on experience, location, and employer.

What is the difference between Python React Full Stack vs Python Backend Developer?

AspectPython React Full StackPython Backend Developer
Primary FocusFront-end and back-end development using React and PythonBack-end development primarily with Python
Skills RequiredPython, React, HTML, CSS, JavaScript, REST APIsPython, Django/Flask, SQL, APIs
Work EnvironmentFull-stack projects, collaborative teams, client-facingBack-end systems, server-side logic, database management
Common UsageStartups, tech companies, full-stack rolesBackend services, API development, data processing

While both roles involve Python, Python React Full Stack professionals handle both front-end and back-end tasks, especially with React, whereas Python Backend Developers focus solely on server-side logic and database management. The full-stack role requires knowledge of front-end technologies, making it broader in scope.

What cities near Phoenix, AZ are hiring for Python React Full Stack jobs? Cities near Phoenix, AZ with the most Python React Full Stack job openings:
Full Stack Engineer

Full Stack Engineer

The Mint Dispensary

AZ • On-site, Remote

Full-time

Posted 10 days ago


Job description

Full-Stack Software Engineer
On-site, Tempe, AZ
About the role
Mint Cannabis runs 39+ stores across six states. Our entire tech stack - the storefront, our ERP that runs the business, the inventory pipeline, the POS integration, and the K8s cluster on GCP that hosts the supporting services - is currently built and maintained by one developer. You'd be the second. That means real ownership from day one, an unusually wide view of how a vertically-integrated retail business actually works, and direct mentorship from someone who's already touched every layer of the stack.
What you'll work on - Day-one focus
  • Storefront features - Astro 5 + Tailwind 4, deployed to Cloudflare Pages. New pages, components, and UX flows on the customer-facing e-commerce site.
  • ERP backend work - Python modules for the multi-company ERP, custom website routes, POS integration, internal admin tooling.
  • Inventory & discount pipeline - Node service syncing product and inventory data into Redis + Postgres. Features that affect what customers see and pay.
  • Deploys across Cloudflare Pages, Railway, and our GKE cluster on GCP - you'll ship to all three from week one.
  • Bug-fixing and incident response across the stack - you'll learn the system by fixing it.

Stretch areas (over 12 months): deeper platform ownership (GKE administration, CI/CD pipeline design, networking); LLM-powered features (we use agentic workflows heavily, in product and in our dev workflow); vendor integrations (Dutchie, PostHog, Google Business Profile, Telnyx SMS).
What we're looking for - Required
  • 5+ years building production web applications
  • Strong with TypeScript and comfortable in Python (or strong in Python with TS fluency)
  • Shipped to a modern SSR framework (Astro, Next, Remix, SvelteKit, or similar)
  • Comfortable with relational databases (Postgres preferred) and at least one cache layer (Redis, Memcached)
  • Integrated with at least one third-party API that has real consequences when it fails
  • Production GCP experience - gcloud CLI, IAM, service accounts, Cloud Storage, Cloud SQL or equivalent
  • Comfortable in Kubernetes (GKE preferred) - reads manifests, debugs pods with kubectl, understands services and ingress
  • Networking/IP/DNS fundamentals - TCP/IP, CIDR, routing, firewall rules; DNS records (A, AAAA, CNAME, MX, TXT, NS) and SPF/DKIM/DMARC; reads traceroute and dig +trace
  • Web hosting & edge infra - hands-on with 2+ of: Cloudflare (Pages/Workers/DNS/WAF), VPS/cPanel, AWS (Route 53, S3, CloudFront), GCP (Cloud DNS, Cloud Run, Load Balancing), Vercel/Netlify
  • Docker fluency - writes/debugs Dockerfiles, layer caching, multi-stage builds, container networking
  • YAML fluency - K8s manifests, GitHub Actions, Docker Compose, Helm values
  • Strong git workflow - branching, rebase vs. merge, conflict resolution, code review
  • CI/CD experience - built/maintained pipelines (GitHub Actions, GitLab CI, CircleCI, or similar)
  • Observability with Grafana + Loki (or equivalent) - dashboards, LogQL/PromQL, alerting, real incident diagnosis
  • Multi-cloud literacy - worked across 2+ providers (we run GCP + Cloudflare + Railway)
  • Solid SDLC knowledge end-to-end
  • Test-driven development as a habit - Playwright for storefront, pytest for Odoo modules
  • On-call triage discipline - owned production incidents end-to-end, can write the postmortem
  • Standard app-sec competencies - OWASP (XSS, SQLi, CSRF, auth pitfalls, secret hygiene)
  • LLM-specific security awareness - treats model output as untrusted, understands prompt injection, guardrails tool calls
  • Communication, documentation, presentation - explains decisions at the right altitude for engineers, ops, and execs
  • Articulates engineering reasoning - trade-offs, alternatives, the data behind the call
  • Real Big-O literacy - N+1 queries, denormalization trade-offs, when a hash map beats a tree
  • Reads logs and stack traces fluently; debugs by evidence, not guessing
  • Container orchestration depth - Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, rolling updates, probes, resource limits
  • Can work on-site in Tempe, AZ
Bonus points
  • Odoo experience at the developer level
  • Cannabis industry experience
  • Built/maintained a Dutchie, Metrc, or similar retail-system integration
  • Owned a GKE cluster, written Helm charts, or set up complex CI/CD into Kubernetes
  • Shipped a production feature backed by an LLM (prompt engineering, context management, MCP servers, evals)
  • Tailwind, Storybook, Playwright
  • Cloudflare Workers, Pages, or KV
  • Prometheus, Tempo, or Wazuh SIEM
  • Published technical writing, talks, or open-source maintainership
How you work
  • You debug by reading code and logs, not by guessing
  • You verify your changes work before saying they do
  • You ask questions instead of guessing when the requirement is unclear
  • Comfortable being the only person on a problem, equally comfortable handing it off
  • You prefer boring code that doesn't break to clever code that does
How we work
  • Small team - you, the CTO, and the rest of the Mint org. Real ownership from week one.
  • We ship multiple times a day. Code review is the default, not a ceremony.
  • Light on-call rotation, shared with the CTO. Fewer than 2 pages per rotation.