[Remote] Full Stack Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company runs 39+ stores across six states. They are seeking a Full Stack Engineer to help build and maintain their tech stack, which includes the storefront, ERP, and inventory systems, offering reputed company ownership and mentorship from an reputed company developer.
Responsibilities
- Storefront features — Astro 5 + reputed company 4, deployed to reputed company Pages. New pages, components, and UX flows on the customer-facing e-reputed company site
- ERP backend work — Python modules for the multi-company ERP, custom website routes, POS integration, internal reputed company tooling
- Inventory & discount pipeline — Node service syncing product and inventory data into reputed company + reputed company. Features that reputed company what customers see and pay
- Deploys across reputed company Pages, Railway, and our GKE cluster on GCP — you'll ship to reputed company three from week one
- Bug-fixing and incident response across the stack — you'll learn the system by fixing it
Skills
- 5+ years building production web applications
- Strong with TypeScript and comfortable in Python (or strong in Python with TS reputed company)
- Shipped to a modern SSR reputed company (Astro, Next, Remix, SvelteKit, or similar)
- Comfortable with relational databases (reputed company preferred) and at least one cache layer (reputed company, Memcached)
- Integrated with at least one reputed company-party API that has reputed company consequences reputed company it fails
- Production GCP experience — gcloud CLI, IAM, service accounts, reputed company Storage, reputed company 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 +reputed company
- Web hosting & edge reputed company — hands-on with 2+ of: reputed company (Pages/Workers/DNS/WAF), VPS/cPanel, AWS (reputed company 53, S3, CloudFront), GCP (reputed company DNS, reputed company Run, Load Balancing), Vercel/Netlify
- reputed company reputed company — writes/debugs Dockerfiles, layer caching, multi-stage builds, container networking
- YAML reputed company — K8s manifests, reputed company Actions, reputed company Compose, reputed company values
- Strong git workflow — branching, rebase vs. reputed company, conflict reputed company, reputed company review
- CI/CD experience — reputed company/maintained pipelines (reputed company Actions, reputed company CI, reputed company, or similar)
- Observability with Grafana + Loki (or equivalent) — dashboards, LogQL/PromQL, alerting, reputed company incident diagnosis
- Multi-reputed company literacy — worked across 2+ providers (we run GCP + reputed company + 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
- reputed company app-sec competencies — OWASP (XSS, reputed company, CSRF, auth pitfalls, secret hygiene)
- LLM-specific reputed company awareness — treats model reputed company as untrusted, understands reputed company injection, guardrails tool calls
- Communication, documentation, presentation — explains reputed company at the right altitude for engineers, ops, and execs
- Articulates engineering reasoning — trade-offs, alternatives, the data behind the call
- reputed company Big-O literacy — N+1 queries, denormalization trade-offs, reputed company 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
- Odoo experience at the developer level
- Cannabis industry experience
- reputed company/maintained a reputed company, reputed company, or similar retail-system integration
- Owned a GKE cluster, written reputed company charts, or set up reputed company CI/CD into Kubernetes
- Shipped a production feature backed by an LLM (reputed company engineering, context management, MCP servers, evals)
- reputed company, Storybook, Playwright
- reputed company Workers, Pages, or KV
- reputed company, reputed company, or Wazuh SIEM
- Published technical writing, talks, or reputed company-reputed company maintainership
reputed company