1

Mid Backend Developer Jobs in California (NOW HIRING)

Those services have to stay consistent when WiFi drops mid-service. As a backend engineer on this team, you will design and scale the services behind order orchestration, payment flows, offline-first ...

Frontend Developer

Fremont, CA · On-site

$113K - $132K/yr

W2 Job Summary We are seeking a Mid-Level Frontend Software Engineer with strong hands-on ... NET backend services and within the automotive industry is highly preferred. Key Responsibilities ...

Those services have to stay consistent when WiFi drops mid-service. As a backend engineer on this team, you will design and scale the services behind order orchestration, payment flows, offline-first ...

... and engineers. What you'll do You'll work across the whole backend: the SvelteKit app and its ... fail mid-flight * Improving our public API. Designing a clean, well-documented API surface with ...

Looking for a Mid to Senior level JavaScript developer with expetise in JavaScript, NodeJS, Kafka, HTML and CSS. Having Adobe Analytics knowledge to instrument online experience is highly desired.

Showing results 41-60

Mid Backend Developer information

What is a mid backend developer?

Mid Backend Developers are software engineers with intermediate experience who focus on building, maintaining, and optimizing the server-side components of web or mobile applications. They typically work with databases, APIs, server logic, and integration with front-end systems. Mid-level developers have a solid understanding of programming languages such as Java, Python, Node.js, or Ruby and are expected to contribute to code reviews, troubleshoot issues, and implement new features under minimal supervision. Their role bridges the gap between junior developers, who need more guidance, and senior developers, who handle architecture and high-level decisions.

What are some typical challenges a mid backend developer might face when integrating new technologies into existing systems?

As a Mid Backend Developer, one common challenge is ensuring that new technologies or frameworks integrate smoothly with legacy systems without disrupting current operations. This often involves understanding both the old and new codebases, data migration, and dealing with compatibility issues. Collaborating closely with frontend developers, DevOps, and QA teams is essential to address potential bottlenecks and maintain performance. Additionally, thorough testing and documentation are crucial to ensure long-term stability and maintainability.

What are the key skills and qualifications needed to thrive as a mid backend developer, and why are they important?

To excel as a Mid Backend Developer, you need strong programming skills in languages such as Java, Python, or Node.js, along with a solid understanding of databases and API design, typically backed by a bachelor’s degree in computer science or related field. Familiarity with tools and systems like Git, RESTful APIs, Docker, and cloud platforms (e.g., AWS, Azure) is usually required. Problem-solving abilities, effective communication, and teamwork are crucial soft skills that set high performers apart. These competencies ensure efficient development, maintainability, and seamless integration of backend services in dynamic technical environments.

What is the difference between Mid Backend Developer vs Backend Developer?

AspectMid Backend DeveloperBackend Developer
Experience LevelMid-level (2-4 years)Entry to Mid-level (0-3 years)
Skills & CertificationsProficiency in server-side languages, databases, APIs; often familiar with cloud servicesBasic to intermediate backend skills, some familiarity with similar technologies
Work EnvironmentCollaborates on complex projects, often in teams with frontend and DevOpsWorks on foundational backend tasks, may be part of smaller teams or solo projects
Industry UsageCommon in tech companies, startups, and enterprise environmentsWidespread across various industries, including tech, e-commerce, and finance

The Mid Backend Developer typically has more experience and handles more complex backend systems compared to a Backend Developer. While both roles require similar foundational skills, the mid-level position involves greater responsibility, problem-solving, and collaboration on larger projects.

What job categories do people searching Mid Backend Developer jobs in California look for?

The top searched job categories for Mid Backend Developer jobs in California are:

What cities in California are hiring for Mid Backend Developer jobs?

Cities in California with the most Mid Backend Developer job openings:

Infographic showing various Mid Backend Developer job openings in California as of August 2026, with employment types broken down into 78% Full Time, 14% Part Time, 2% Temporary, and 6% Contract. Highlights an 93% Physical, 3% Hybrid, and 4% Remote job distribution.

Software Engineer UI, Cloud & Backend Design Lead

San Francisco, CA • On-site

Other

Medical, Dental, Vision, Retirement

Posted 9 days ago


Job description

PRhobe, Inc.

Software Engineer

Cloud & Backend Design Lead | Orinda, CA | Full-time, W-2 | Mid to senior — we hire and title to fit

ABOUT PRHOBE

PRhobe is rebuilding the economics of logistics tracking. Our patented RIoT device attaches to a pallet, container or trailer, reads RFID tags on the goods around it, and reports item-level location and condition to the cloud — cutting the cost of a tracked item journey from roughly $50 to $0.50. A $1.25M NSF SBIR Phase II award will take RIoT from evaluation hardware to certified, field-deployed product, with further funded scope expected soon. The NSF funding, combined with private financing, is expected to provide sufficient capital to take us beyond commercial product launch.

THE ROLE

Every RIoT in the field reports the passive RFID tags around it. Your job is to turn that stream into a live digital twin of every serial-numbered item moving through global logistics — and then into alerts a supermarket, a car plant or a pharmaceutical distributor will pay for. You own the backend, the data model, the alerting engine, the customer-facing UI and the partner integrations.

WHAT YOU WILL OWN

•  Backend cloud platform. Build and operate ingestion, device management and processing on a managed IoT cloud, then lead the evaluation and, if warranted, migration to a (hybrid) PRhobe-owned platform. Pragmatism first, then durability.

•  Digital twin data model. Maintain per-item state for serial-numbered goods associated to a RIoT at each blink — location, custody, environmental history — across journeys crossing carriers, borders and months.

•  Bandwidth economics. Cellular payload is a direct cost and a direct battery cost. Design the delta representation of tag populations with the Firmware Engineer so we send changes, not inventories.

•  Alerting and value propositions. Build the rules and analytics behind real-time inventory count and accuracy, ETA deviation, route change, partial load separation, shrinkage and spoilage risk, theft last-known-location, hazardous proximity and multi-factor delivery authentication.

•  Customer-facing UI. A clear interface for inventory count, location, environmental state (temperature, humidity, air quality), device health and journey history — supporting real customer pilots at production grade.

•  Traceability and partner integrations. Model events so one structure serves DSCSA serialization in pharma, FSMA 204 tracking events in food, item-level inventory in retail and PPAP-grade evidence in automotive. Build the APIs, ASN/EDI exchanges and audit trails that make RIoT useful to our customers and to the logistics software they already run.

WHERE YOU WILL FLEX

The device and the cloud are one system with a radio in the middle. You will design the on-air payload format jointly with the Firmware Engineer, and we would gladly redeploy a backend engineer who holds their own in embedded C onto device-side work when the schedule calls for it. If your instincts run toward data and UI, there is more than enough of both here.

WHAT YOU BRING

We are open on level — we title to fit. A smart engineer with 5-10 focused years interests us as much as a fifteen-year senior. Title and pay follow the person; the work does not change. We expect experience deploying software continuously into production.

•   AI fluency — mandatory. You use Claude, ChatGPT, Perplexity, Grok or equivalent daily and have multiplied your own throughput, on the order of 10x or more rather than a marginal gain. Be ready to walk us through what you delegate, what you deliberately do not, and how you verify.

•   5+ years building and operating production backend systems, including services you personally kept running.

•   Data engineering instincts for high-volume time-series and event data, and schemas that survive years of change. PostgeSQL, MQTT/COAP.

•   Event-driven or streaming architecture; an alerting engine that is both accurate and cheap to run, supporting observability, logging and metrics.

•   Practical API design and third-party integration, including documentation partners can actually build against. REST, Websockets etc.

•   Sufficient front-end capability to own an operational dashboard end to end supporting security, authentication, authorization, multi-tenancy

•   Time-series and event data at fleet scale, with cost-aware query, retention and rollup, and with event queues.

•   Working knowledge of multi-tenant security and data isolation — our customers compete with one another.

•   BSCS or equivalent practical background.

NICE TO HAVE

•   Managed IoT platform experience (AWS IoT, Azure IoT, Google Cloud IoT or similar) — provisioning, fleet management, telemetry.

•   Logistics, WMS or track-and-trace domain experience in automotive, pharma, retail or food.

•   GS1 EPCIS, SGTIN and EPC Gen2 identifiers; DSCSA or FSMA 204 data models; Flutter or an equivalent front-end framework.

COMPENSATION, BENEFITS AND LOCATION

Full-time W-2. $113,000–$139,000 depending on level and experience, set against the labor rates approved under our federal award. 401(k) with 6% employer match; 90% employer-paid medical, dental and vision. Based in Orinda, CA, at our facility walking distance from BART; remote and hybrid arrangements within California open to discussion.

WHY THIS IS WORTH YOUR TIME

•   Generous equity, and a market that justifies it. Early-stage equity is inherently uncertain. What we can say are the targets: ~$10 trillion global logistics (tracking) and $30 trillion product inventory. Taking tracking from $50 to $0.50 while creating the real-time inventory category is a change we expect to work at a scale with no natural ceiling.

•   Ownership, and it ships. You own your discipline, and your name goes on the patents you earn. Funded, with customers waiting on pilots — your work will be deployed to customer pilots inside a year.

  • PRhobe is an equal opportunity employer and does not discriminate on any protected basis. Applicants must be authorized to work in the United States. This role is federally funded; daily contemporaneous time recording against project charge codes is a condition of employment.