Jobs / United States / gravity9
Lead Java Developer/Solution Architect (6-month contract)
gravity9 · 🇺🇸 Remote job · Remote
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal — ask the recruiter.
- No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- Confirmed live todayWhen a source last listed this job as open.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Why not apply?
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
SponsorApply flags time-wasters so your applications go where they can land. These come from the posting's own wording — read the original listing to confirm. See better-fit alternatives →
Sponsor Radar — gravity9
This employer posted directly and does not match a government sponsor register.
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for gravity9 →
About the role
gravity9 is recruiting Java engineers and architects for a portfolio of engagements across UK central government. These are large-scale, data-intensive modernisation programmes: replacing legacy systems that carry statutory weight, decomposing monoliths that serve millions of users, and building secure data platforms where access control and auditability are first-class architectural concerns rather than late additions. We are hiring across two overlapping profiles — Senior Java Developer and Application / Migration Architect — and expect most people to move between programmes as engagements start and complete. Several of these are hands-on architect roles: you will own design decisions and also write production code The kind of work The following are representative of current and upcoming engagements. Individual roles will draw on some of this, not all of it — we are more interested in engineers who can work confidently at the intersection of Java and data than in a checklist match against any one programme. Secure data catalogue and access-control platform A greenfield metadata catalogue acting as a federated index over data held across independent domains, so that authorised parties can locate and retrieve data the catalogue itself never holds. The work includes designing an attribute-based access control model over attributes such as clearance, nationality, organisational unit and compartment; enforcing those policies inside the database query path rather than filtering results afterwards; application-layer encryption with externally managed keys; hybrid lexical and semantic search with access filtering applied before candidate retrieval rather than after it; and a tamper-evident audit trail that can reconstruct why a given record was returned, redacted or withheld. Real-time decision-support data architecture Replacing point-to-point integration across a multi-vendor estate with a microservices architecture and a common data layer, so that operational data flows in near real time instead of over days. The work includes target-state architecture and decision records, change-data-capture ingest pipelines from upstream data services, ontology and mapping-layer design across suppliers with competing data models, separation of system, reference and insight data classes including time-series, and deployment topologies spanning cloud-hosted services down to constrained edge hardware. Legacy-to-document-model migration at national scale Migrating hundreds of millions of records and tens of terabytes of XML out of a legacy relational platform into a sharded document store, in support of a COBOL-to-Java microservices rewrite. The work includes a configuration-driven XML-to-JSON transformation framework backed by a versioned schema registry — twenty years of history, multiple record types and continual schema and semantic drift; CDC and streaming pipelines, or a checkpointed parallel bulk-extract alternative; a field-level mapping validation and reconciliation framework robust enough to stand up to audit; a replay and failure-diagnostics harness with dead-letter routing and idempotent re-runs; and repeated dress rehearsals toward a single cutover window with no dual running. Monolith decomposition and data-ownership migration Breaking a distributed monolith of well over a hundred Java services sharing a handful of database clusters into domain-owned services — moving from borrowed data to owned data without reintroducing hidden coupling. The work includes bounded-context analysis to establish which domain genuinely owns which collections, in-place data remodelling ahead of any physical move, a data-access facade with feature-flagged per-request routing between old and new stores, dual-write / backfill / reconcile / read-switch cutover