Full Stack React Software Engineer (AI Infrastructure) Role in St. Petersburg, FL

Job Description

Duties:

\n

\n
• Build features end to end across the Nash platform — from the React/TypeScript front end through the Java/Spring Boot services to the Oracle schema behind them.

\n

• Extend the asynchronous LLM execution pipeline. Work on the message-driven services that accept requests, queue them by priority, call the model provider, and return results — including retry, failover and error handling semantics.

\n

• Integrate and maintain model provider connections across Azure OpenAI and AWS Bedrock: new model onboarding, routing, provider SDK upgrades, and the differences in how each provider reports usage and errors.

\n

• Design and implement throughput controls — token- and request-per-minute rate limiting, backpressure, and circuit breaking — so the platform scales toward its 1M+ requests/day target without exhausting provider quota.

\n

• Own usage, cost and token accounting. Extend the data model and reporting that tracks input, output and reasoning tokens per request, and surface it in the admin UI.

\n

• Deliver the self-service authoring experience that lets business teams create and tune AI use cases without hands-on engineering support.

\n

• Work the full change lifecycle in a regulated environment — design, code review, governance and compliance gates, and controlled promotion across environments.

\n

• Build and maintain observability — structured logging, service metrics, and dashboards in Splunk, Datadog and Dynatrace; diagnose production issues across a distributed, queue-based system.

\n

• Harden the platform — service authentication and authorisation, secrets handling, and dependency currency.

\n

\n

Collaborate with DBAs, platform, networking and compliance teams, whose sign-off the work depends on.

\n

Skills:

\n

**Required**

\n

- 5+ years building and running production web applications end to end

\n

- **React 18 + TypeScript** — hooks, modern state management (Redux Toolkit / RTK Query), and experience with a high-volume data grid (ag-grid or equivalent)

\n

- **Java 17 + Spring Boot** — REST APIs, Spring Data JPA, dependency injection, configuration management

\n

- Strong **relational database and SQL** skills — schema design, query tuning, and working with DBA-applied migrations rather than ORM-generated DDL

\n

- Solid grasp of **asynchronous and concurrent programming** — thread pools, executors, and the failure modes that come with them

\n

- Git-based workflow with peer review; CI/CD pipelines

\n

- Able to work within formal change control, and to write for an audience that includes non-engineers

\n

\n

**Strongly preferred**

\n

- **Project Reactor / reactive Spring** (`Mono`, `Flux`, WebFlux) — core to the execution services

\n

- **Message-oriented middleware** — IBM MQ, JMS, ActiveMQ or Kafka; consumer concurrency, redelivery, dead-letter handling

\n

- **LLM API integration experience** — Azure OpenAI, Bedrock or OpenAI directly; prompt handling, token accounting, rate limits, and 429/backoff semantics

\n

- **Kubernetes and Docker** in an enterprise setting

\n

- **Micro-frontend architecture** — Webpack Module Federation or similar

\n

- Oracle specifically, including PL/SQL

\n

- Observability tooling: Splunk, Datadog, Dynatrace, Prometheus/Micrometer

\n

\n

**Nice to have**

\n

- Azure API Management, or API gateway policy work generally

\n

- Financial services or another regulated industry

\n

- Performance and load testing at scale

\n

- Maven and private artifact repositories (Artifactory)