Senior Full-Stack Engineer (Java / React)Sales Representative - AI Strategy & Custom Software Consultancy (Remote, 1099, Part-Time)

Intellitech Solutions is a small, senior consulting firm specializing in complex software solutions. They are seeking a Senior Full-Stack Engineer to work on a distributed platform of Java microservices and a React front end, focusing on building advanced scheduling systems for broadcasting.

Responsibilities:

• Designing async, non-blocking services that stay responsive while doing heavy I/O against databases, queues, and third-party APIs
• Modeling difficult domain logic (recurrence, rights windows, regional variants, live vs. re-air behavior) so it stays understandable six months later
• Building and evolving a rules engine that non-engineers configure to change scheduling behavior without a deploy
• Handling event-driven messaging across services: ordering, idempotency, retries, poison messages, and distributed locking
• Owning data modeling and migrations on collections that grow fast and can't afford downtime
• Building the React and TypeScript front end operators live in all day: data-dense grids, canvas-rendered schedule views, and forms that have to get complicated input exactly right
• Integrating with external systems whose specs don't always match reality, and building the validation that keeps their problems from becoming ours
• Writing the tests that let all of this change with confidence

Requirements:

• Strong modern Java. We lean functional: records, streams, immutability, and composition over deep inheritance hierarchies
• Real async experience. Vert.x is ideal, but Reactor, RxJava, Mutiny, Netty, or Kotlin coroutines all translate. What matters is that you understand why you never block an event loop, and can spot it when someone has
• React and TypeScript. Hooks, component composition, typed state, and the judgment to keep a large front end maintainable rather than letting it sprawl
• Distributed systems instincts. Idempotency, eventual consistency, retries, backpressure, and the difference between 'it worked in dev' and 'it worked at 3x volume.'
• Messaging. RabbitMQ, Kafka, or SQS. The tool matters less than knowing what happens when a consumer dies mid-ack
• A document database in production. MongoDB preferred: schema design, indexing, and knowing where document modeling tends to bite you
• Testing as a reflex. Unit and integration. You don't have to be a TDD zealot, but code arriving without tests should feel wrong to you
• Written communication. Half of senior engineering is a clear paragraph at the right moment
• Redis for caching, distributed locking, or coordination
• MUI and MUI X, Apollo GraphQL, or canvas-based visualization (Konva) experience on data-heavy front ends
• A background in broadcast, media, streaming, OTT, or scheduling, or any domain where time zones and calendars have personally wronged you
• Gradle multi-module builds and the discipline to keep them clean
• Docker, CI/CD, and comfort with the operational half of 'you build it, you run it'
• Comfort joining an existing codebase, team, and set of practices, and improving them from the inside rather than rewriting everything