Senior Full-Stack Engineer (React/Clojure for Analytics Platform)

We are looking for a Senior Full-Stack Engineer to join a high-impact internal analytics platform initiative at a mobile-first financial platform. This team is building and evolving internal products that give product, analytics, operations, and experimentation teams deep visibility into customer behavior, product funnels, event flows, and cross-platform interactions across a large-scale mobile ecosystem. This role sits at the intersection of modern web product development, analytics infrastructure, and internal platform engineering. The work combines rich analyst-facing and back-office web experiences with contract-driven service integration over real-time and high-volume analytical data systems. The ideal candidate is comfortable owning complex frontend surfaces while also working effectively across backend services, query layers, and data-facing product workflows. This is a true full-stack role with a strong product and platform component. On the frontend side, you should be able to build polished, high-density React applications with strong usability, performance, and maintainability. On the backend integration side, you should be comfortable working with service-oriented architectures, typed contracts, query services, and backend systems built in Clojure or similar functional / JVM environments. As a Senior Engineer, you will help evolve internal analytics and experimentation workflows related to event exploration, product funnels, operational visibility, rollout controls, and instrumentation quality. You are expected to bring 5+ years of overall software engineering experience, including strong production experience building web applications with React and meaningful experience integrating with backend services in Clojure or adjacent ecosystems. The ideal candidate combines strong product judgment with engineering depth in environments where frontend delivery, service integration, and analytical data all need to work together reliably. React + TypeScript / JavaScript Strong hands-on experience building production web applications with modern React, including component architecture, hooks, reusable abstractions, and maintainable UI systems for complex internal products. Clojure or Strong Adjacent Backend Experience Production experience working on or deeply integrating with backend systems built in Clojure, or strong experience in adjacent JVM / functional ecosystems such as Scala, Kotlin, or Java with clear readiness to ramp into Clojure quickly. Full-Stack Product Ownership Ability to work across frontend application layers and backend-facing integration concerns, contributing meaningfully to both user-facing product delivery and service-level technical design. Modern Web Platform Experience Experience working across more than one React application model, including modern framework-based applications and mature SPA/back-office architectures. The team operates in a mixed environment rather than a single greenfield stack. Frontend-Inclined Strengths Ability to build high-quality internal web products with strong UX for dense, data-heavy, read-intensive workflows such as tables, filters, charts, path analysis, funnel analysis, and analyst-facing operational screens. Backend-Inclined Strengths Ability to work effectively with service-oriented architectures, HTTP APIs, typed contracts, auth-aware flows, backend-for-frontend patterns, query services, and large analytical payloads. Analytics and Data-Heavy Product Experience Experience building products where event analytics, product usage data, operational insights, experimentation data, or other analytical workflows are central to the user experience. State Management Ability to model local, shared, and remote state clearly using practical patterns such as React Query, Context, Redux, lightweight state stores, or equivalent approaches without unnecessary complexity. Schema-Driven Integration Experience consuming contract-first APIs, generated clients, typed schemas, or strongly structured service interfaces, with emphasis on correctness and safe evolution between frontend and backend systems. Component Libraries and Design Systems Experience building polished interfaces with mature component systems such as Ant Design, Material UI, Chakra, or similar libraries commonly used in internal operational platforms. Experimentation and Feature Flags Practical experience with experimentation platforms, rollout controls, or feature-flag systems where gradual release, measurement, and operational safety matter. Instrumentation and Product Analytics Strong understanding of event instrumentation, event schemas, funnel-oriented product analysis, and the practical realities of building software around behavioral data. Performance Optimization Track record of diagnosing and improving bottlenecks across React rendering, browser performance, network behavior, and query-driven UI flows in data-heavy applications. Observability and Error Monitoring Practical ability to instrument applications, investigate runtime issues, and work with logs, metrics, traces, and monitoring tools such as Sentry or equivalent platforms. Testing Commitment to quality through unit, integration, and end-to-end testing using tools such as Jest, React Testing Library, Playwright, Cypress, or equivalent. Existing System Ownership Ability to join mature products, understand constraints quickly, and improve them incrementally without destabilizing business-critical systems. English C1 Ability to communicate technical trade-offs clearly, participate in design discussions, and collaborate effectively in a remote, multicultural environment. EXTRAS (Nice to have) Real-Time OLAP Experience Previous work with Apache Pinot, Druid, ClickHouse, BigQuery real-time, or similar analytical systems that power operational or analyst-facing products. Analyst-Facing Product Experience Experience building products for support, fraud, analytics, or business operations teams where large datasets and workflow efficiency are central to the user experience. Clojure Service Familiarity Exposure to integrating with Clojure-based backend services or comfort ramping into teams where key backend domains are implemented in Clojure. Internationalization Experience with runtime localization systems or externalized translation workflows beyond simple build-time string handling. Product Analytics and Funnel UX Familiarity with event analytics, funnel exploration, segmentation workflows, or experimentation-oriented product interfaces. Functional or JVM Background Background in Scala, Kotlin, Java, or functional design approaches can be valuable when paired with strong frontend and product-platform delivery skills. Quick Skills Reference Languages TypeScript, JavaScript, SQL, Clojure or adjacent JVM / functional language Frontend React, Next.js, SPA Architecture, HTML5, CSS3, Accessibility, Data-Heavy UI Backend Integration Clojure Services, HTTP APIs, Contract-First Clients, Auth-Aware Flows, Query Services, Service Integration State & UI React Query, Redux or equivalent state patterns, Component Libraries, Design Systems Product Platforms Internal Tools, Experimentation, Feature Flags, Operational Workflows Analytics Product Analytics, Event Instrumentation, Funnel Analysis, Virtualized Tables, Charts, Real-Time Analytics Data / Infra Context OLAP Systems, Analytical Query Services, Event Pipelines, Observability Quality / Tooling Jest, React Testing Library, Playwright, Cypress, Sentry, CI/CD Apply To This Job

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...