[Hybrid NYC] Staff Software Engineer – Event-Driven Architecture

<p>Intellibus designs and engineers platforms trusted by some of the most established FinTech and financial trading firms in the world. Our engineering teams build systems that power high-volume trading, real-time financial data, and mission-critical infrastructure.</p><p><br></p><p>We expect our engineers to operate at a level where technical depth, sound judgment, and clear communication all carry weight — the problems are complex, the systems are production-critical, and the people you work with will hold you to a high standard.</p><p><br></p><p><strong>The Staff Engineer Role</strong></p><p>We are hiring a Staff Engineer to design, build, and own full-stack systems powering financial platforms — from frontend architecture to backend services to distributed event-driven infrastructure.</p><p><br></p><p>This is not a role where you pick up tickets and ship features. You will be expected to think end-to-end: to understand the business problem, design the system, make the trade-offs, and deliver production-grade software that performs reliably under heavy load.</p><p><br></p><p>You will work directly with senior stakeholders across technical and non-technical functions, often navigating competing priorities, ambiguity, and high-pressure timelines.</p><p><br></p><p>The ability to communicate clearly, manage complexity across people and systems, and maintain a high quality bar when things get difficult is essential.</p><p><br></p><p>If you have built and shipped systems that mattered — at a startup, at a large company, or somewhere in between — and you are looking for a role where you will be challenged technically while also growing your ability to operate in complex, high-stakes environments, we want to hear from you.</p><p><br></p><p><strong>What You Will Do</strong></p><p><strong>Frontend Architecture</strong></p><ul><li>Build scalable frontend platforms using React, Next.js, and TypeScript.</li><li>Design modern UI architectures: server-side rendering, component-driven design, performance optimization, and state management patterns.</li><li>Develop reusable component systems and scalable frontend frameworks.</li></ul><p><br></p><p><strong>Backend Engineering</strong></p><ul><li>Build backend services using Node.js and NestJS.</li><li>Design and implement REST APIs, microservices, asynchronous workflows, and high-performance data processing systems.</li><li>Work with SQL and NoSQL databases using TypeORM, and optimize for throughput and reliability.</li></ul><p><br></p><p><strong>Event-Driven & Distributed Systems</strong></p><ul><li>Design distributed systems built on event-driven architecture using Kafka, Azure Service Bus, Azure Event Grid, and messaging/queue systems.</li><li>Build services that process high-volume financial events and real-time trading data.</li></ul><p><br></p><p><strong>Cloud & Infrastructure</strong></p><ul><li>Deploy and operate systems on Microsoft Azure, including Azure App Services, Azure Data Fabric, messaging platforms, Docker, CI/CD pipelines, and Linux environments.</li><li>Design infrastructure that supports resilient, scalable distributed systems.</li></ul><p><br></p><p><strong>What Sets You Apart</strong></p><p>We are looking for engineers who demonstrate several of the following:</p><p><br></p><ul><li>You have designed and operated event-driven distributed systems that process high-volume real-time data.</li><li>You have a deep understanding of algorithms, data structures, and time complexity — and you apply that understanding to build systems, not just pass interviews.</li><li>You have built full-stack platforms using React/Next.js and Node.js/NestJS that run reliably in production.</li><li>You have hands-on experience with message queues, streaming platforms, and asynchronous workflows — Kafka, Azure Service Bus, BullMQ, or similar.</li><li>You reason clearly about system trade-offs: latency vs. throughput, consistency vs. availability, speed vs. reliability.</li><li>You have operated systems in cloud environments like Microsoft Azure, including debugging production incidents and improving performance under pressure.</li><li>You design systems end-to-end and take ownership of architecture and production outcomes — not just the code you wrote.</li><li>You have mentored other engineers and contributed to architecture reviews, engineering standards, and technical decision-making.</li><li>You communicate well under pressure. You can hold your ground in a room full of stakeholders, explain a technical decision to a non-technical audience, and navigate situations where the right path forward is not obvious.</li></ul><p><br></p><p><strong>Technology Ecosystem</strong></p><p><strong>Frontend:</strong> React, Next.js, TypeScript, JavaScript, TailwindCSS, HTML5, CSS3.</p><p><strong>Backend:</strong> Node.js, NestJS, REST APIs, Microservices, BullMQ, TypeORM.</p><p><strong>Event-Driven:</strong> Kafka, Azure Service Bus, Azure Event Grid.</p><p><strong>Infrastructure:</strong> Microsoft Azure, Azure Data Fabric, Docker, CI/CD, Infrastructure-as-Code, Linux.</p><p><strong>Data:</strong> SQL, NoSQL, Azure Data Fabric.</p><p><br></p><p><strong>Compensation $75 - $85 / Hour</strong></p><p><br></p><p><strong>Our Process</strong></p><ol><li>15-minute video call with someone from our team.</li><li>4 Proctored GQ Tests (under 2 hours).</li><li>30–45 minute final video interview.</li><li>Job offer.</li></ol><p><br></p><p>If this sounds like the kind of work you want to be doing, apply now. Our team will be in touch within the hour.</p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...