Senior Full-Stack Engineer (Java / React)

𝗦𝗲𝗻𝗶𝗼𝗿 𝗙𝘂𝗹𝗹-𝗦𝘁𝗮𝗰𝗸 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 (𝗝𝗮𝘃𝗮 / 𝗥𝗲𝗮𝗰𝘁)

Intellitech Solutions, LLC | Remote-friendly | 1099 contract through end of 2026, likely to extend into 2027

𝗥𝗘𝗔𝗗 𝗧𝗛𝗜𝗦 𝗙𝗜𝗥𝗦𝗧

People are watching television right now. To make that work, somebody, somewhere, had to build a schedule of events: every episode, every promotional advertisement, every break, every regional variation, every rerun, even live events and break-ins for urgent news.

We build the systems that do that.

If the schedule is bad, it airs bad, and that means frustration or lost revenue. We're hiring someone to help us keep building out the most advanced scheduling system in the space, one that's rolling out to network after network.

𝗪𝗛𝗢 𝗪𝗘 𝗔𝗥𝗘

Intellitech Solutions is a small, senior consulting firm. We get brought in when a platform is genuinely difficult: high-volume, real-time, rules-heavy, and tangled up in integrations. Teams call us when they need people who can walk into an unfamiliar domain, get fluent fast, and start shipping things that hold up under production load.

A few honest things about working with us:

• 𝗪𝗲'𝗿𝗲 𝘀𝗺𝗮𝗹𝗹 𝗼𝗻 𝗽𝘂𝗿𝗽𝗼𝘀𝗲. You will not be engineer #340. Your commits are visible, your architectural opinions get heard, and there's nowhere to hide. Most good engineers find that freeing rather than frightening.

• 𝗪𝗲 𝗴𝗼 𝗱𝗲𝗲𝗽, 𝗻𝗼𝘁 𝘄𝗶𝗱𝗲. We'd rather own a whole subsystem end to end than rotate people across ten shallow tickets like a body shop.

• 𝗪𝗲 𝘄𝗼𝗿𝗸 𝗱𝗶𝗿𝗲𝗰𝘁𝗹𝘆 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗵𝗼 𝘂𝘀𝗲 𝘄𝗵𝗮𝘁 𝘄𝗲 𝗯𝘂𝗶𝗹𝗱. You'll talk to the operators whose day gets better or worse based on the code you shipped. That's a rare and useful feedback loop.

𝗪𝗛𝗔𝗧 𝗬𝗢𝗨'𝗗 𝗔𝗖𝗧𝗨𝗔𝗟𝗟𝗬 𝗪𝗢𝗥𝗞 𝗢𝗡

A distributed platform of Java microservices, dozens of them, that ingest programming metadata from upstream systems, run it through a configurable rules engine, and emit broadcast-ready schedules to downstream playout and traffic systems. On the front end, a React and TypeScript application that lets operators see, understand, and reshape those schedules.

Concretely, the work looks like:

• 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

𝗪𝗛𝗔𝗧 𝗪𝗘 𝗡𝗘𝗘𝗗 𝗬𝗢𝗨 𝗧𝗢 𝗕𝗥𝗜𝗡𝗚

𝗡𝗼𝗻-𝗻𝗲𝗴𝗼𝘁𝗶𝗮𝗯𝗹𝗲:

• 𝗦𝘁𝗿𝗼𝗻𝗴 𝗺𝗼𝗱𝗲𝗿𝗻 𝗝𝗮𝘃𝗮. We lean functional: records, streams, immutability, and composition over deep inheritance hierarchies.

• 𝗥𝗲𝗮𝗹 𝗮𝘀𝘆𝗻𝗰 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲. 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.

• 𝗥𝗲𝗮𝗰𝘁 𝗮𝗻𝗱 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁. Hooks, component composition, typed state, and the judgment to keep a large front end maintainable rather than letting it sprawl.

• 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝗶𝗻𝘀𝘁𝗶𝗻𝗰𝘁𝘀. Idempotency, eventual consistency, retries, backpressure, and the difference between "it worked in dev" and "it worked at 3x volume."

• 𝗠𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴. RabbitMQ, Kafka, or SQS. The tool matters less than knowing what happens when a consumer dies mid-ack.

• 𝗔 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗶𝗻 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻. MongoDB preferred: schema design, indexing, and knowing where document modeling tends to bite you.

• 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝗮𝘀 𝗮 𝗿𝗲𝗳𝗹𝗲𝘅. Unit and integration. You don't have to be a TDD zealot, but code arriving without tests should feel wrong to you.

• 𝗪𝗿𝗶𝘁𝘁𝗲𝗻 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻. 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

𝗧𝗵𝗶𝗻𝗴𝘀 𝘄𝗲 𝗱𝗼 𝗻𝗼𝘁 𝗰𝗮𝗿𝗲 𝗮𝗯𝗼𝘂𝘁:

• Whether you have a CS degree

• Whether you can whiteboard a red-black tree from memory

• How many buzzwords fit on one page

𝗛𝗢𝗪 𝗪𝗘 𝗛𝗜𝗥𝗘

1. 𝗔 𝗷𝗼𝗶𝗻𝘁 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻. You, our principal, and our CTO, together in one virtual room. It's mutual; you should be interviewing us at least as hard. We'll talk through a real problem from our actual domain. No puzzles, no tricks.

2. 𝗔 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗰𝗹𝗶𝗲𝗻𝘁. We staff this work for a client, and they like to meet the people who'll be building on their platform. A fit check, in both directions.

3. 𝗢𝗳𝗳𝗲𝗿.

No take-home projects, no paid exercises, no lost weekends. We give real feedback at every stage, including when the answer is no. We've been on the receiving end of silent rejections, and we won't do that to you.

𝗧𝗛𝗘 𝗔𝗥𝗥𝗔𝗡𝗚𝗘𝗠𝗘𝗡𝗧, 𝗣𝗟𝗔𝗜𝗡𝗟𝗬

This is a 1099 independent-contractor engagement, not a W-2 role. You invoice us, and you handle your own taxes, benefits, and equipment, including the hardware and development tools you work on. The current contract runs through the end of 2026, with a strong likelihood it extends into 2027. We'd rather say that now than have it be a surprise later.

𝗧𝗢 𝗔𝗣𝗣𝗟𝗬

Send us:

• Whatever represents you best: resume, GitHub, a blog post, a war story

• A few sentences on the most interesting bug you've ever fixed. Not the hardest, the most interesting. It's the first thing we read.

No cover letter. Please. We'd rather have the bug story.

Email: careers@intelli.co