experience, including hooks and modern development patterns, and are comfortable with a fast toolchain such as Vite. We have solid backend experience with Node.js and frameworks such as Fastify, Express, or NestJS, along…
Backend Developer jobs in Phoenix, AZ
Backend developers build the server-side logic, APIs, and data layers that applications run on. The job is designing services that stay correct, fast, and secure as usage grows.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open backend developer roles
12 shown of 237 · sorted by freshness
Job Title: Backend Engineer - Java Location: Phoenix, AZ (3 days onsite 2 days remote ) Duration: C2C Job Description: Perform hands-on architecture, design, and software development. Identify opportunities to adopt new…
Backend Application Engineer - Remote Bright Vision Technologies is a technology consulting and software development company... ...expertise with strong platform-engineering instincts, values internal developer experienc…
Backend Engineer Candidates with 12-month validity Phoenix AZ Only Nearby candidates as F2F is required Must have: Java + Spring Boot + mongo/Cassandra + Kotlin(preferred) Qualifications: ~ Preferably a BS or MS degree i…
Job Summary Backend Engineer (American Express, Phoenix AZ) - Develop, test, and maintain backend services using Java, Spring Boot, and Kotlin. - Work with NoSQL databases such as MongoDB or Cassandra. - Integrate and bu…
projects when needed. We promote and implement departmental best practices, standards, and development guidelines. We design and develop real-time and file-based integrations, while improving database-level processing wh…
About The Position Corjl Software is looking for a Backend Software Engineer to help us roll out the next generation of our graphic... ...wide variety of complex problems. You will also mentor junior developers to help t…
Job Title: Full Stack Developer Status: Full-time, On-site Department: Technology Reports to: Director of Engineering About the Role We're seeking full stack engineers to expand our platform's API and service capabilitie…
Description Job Description Benefits: ~401(k) Java Full Stack Developer (Java and React) Candidates should be willing to work onsite... ...EITACIES is seeking a Java Full Stack Developer with strong backend engineering e…
code meets concrete, this is your spot. As a Senior Python Backend Engineer at AIAEC, you will be a key architect and builder of... .... Key Responsibilities : ? API Architecture: Design, develop, and maintain high-perfo…
TypeScript experience to help build and scale our platform. This role is hands-on across our React web app, React Native mobile app, backend services, and AWS infrastructure. You’ll work closely with our small engineerin…
Description Job Description Benefits: ~401(k) Python Backend Engineer - APIs Phoenix, AZ (Onsite 3 days/week - Hybrid)... ...scalable microservices. Core Responsibilities Design and develop RESTful APIs using Python Buil…
What backend developers earn in Phoenix
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$49 | $73k–$102k |
| Mid level | $49–$71 | $102k–$148k |
| Senior | $69–$93 | $143k–$194k |
Adjusted for the Phoenix market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Design an API for a feature like comments or notifications.
Clarify requirements, then cover endpoints, data model, pagination, and error handling. Mentioning versioning and rate limits shows production experience.
How would you find and fix a slow database query?
Walk through reading the query plan, checking indexes, and considering caching or denormalization. Ground it in a query you actually fixed.
How do you keep two services consistent when both need to update data?
Discuss transactions, idempotency, and eventual consistency with outbox or saga patterns. Acknowledge tradeoffs rather than promising perfect consistency.
What do you monitor on a service you own?
Name the basics — latency, error rate, saturation — plus business-level signals. Bonus points for talking about alerts you tuned to reduce noise.
Tell me about a production incident you handled.
Structure it: detection, mitigation, root cause, prevention. Emphasize what changed afterward, not just the firefight.
How do you approach securing an API?
Cover authentication, authorization, input validation, and secrets handling. Naming OWASP-style risks concretely is enough; you are not expected to be a security engineer.
When would you choose a message queue over a direct call?
Talk about decoupling, retries, and absorbing spikes, and be honest about the added complexity of async debugging.
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
Name the databases and infrastructure you ran in production, not just languages.
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
If you designed an API others consume, say so and note how many teams or clients depend on it.
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
Where this role goes
Typical progression
Applying for backend developer jobs in Phoenix?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.