Java OMS Developer - Order Management System
Commergence · San Ramon, CA
—
Jul 7, 2026
San Ramon, CA
Jul 21, 2026
What this job asks for AI summary
A contract role focused on building and maintaining an Order Management System using Java and Spring Boot microservices. Day-to-day work involves order processing, inventory and fulfillment logic, event-driven architecture with Kafka, and integrating the OMS with eCommerce, payment, shipping, and warehouse systems. Cloud platforms, containerization, and CI/CD experience are preferred.
Senior level · San Francisco-Oakland-Berkeley, CA · Contract
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 500 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 260–660
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The posting is for a 12-month contract engagement in San Ramon, CA. San Ramon falls within the San Francisco-Oakland-Berkeley, CA CBSA (41860).
No compensation figures are stated anywhere in the posting.
AWS and Azure are listed together as a single preferred item ('AWS/Azure'), so they are captured as one preferred skill with the other as an alternative.
OMS integration experience (eCommerce platforms, payment, shipping, warehouse, inventory systems) is stated as required but names no specific platform product; it is captured under the 'OMS' skill rather than inventing separate unnamed-tool entries.
Event-driven architecture is a methodology/pattern, not a named tool, so it is not emitted as a standalone skill — it is reflected in the Kafka requirement.
No overall years-of-experience figure is stated in the posting.
Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.