Full Stack Engineer

Direct message the job poster from Nexus Leap

The Full Stack Engineer at Nexus Leap designs and builds the web applications powered by our data products, working closely with data engineering, product, and research teammates.

At Nexus Leap, we design and build data products that enable organizations to make better decisions. Our work spans analytics, data engineering, and applied AI—always grounded in real business needs, not hype.

We take a practical, building‑block approach: starting with clear, usable tools, strengthening the data systems behind them, and only then layering in more advanced capabilities. This ensures our work compounds over time and earns trust with the people who rely on it.

We operate as a collaborative, curious team that values clarity, ownership, and steady progress.

Here’s what one of our enterprise clients with over $8B in revenue said about us:

We’re looking for a Full Stack Engineer to help design, build, and evolve the systems that power Nexus Leap’s internal platforms and client‑facing products. This role is hands‑on and spans frontend, backend, and system‑level thinking.

You’ll work closely with data engineering, product, and research teammates to turn ambiguous problems into working solutions. The environment is iterative and fast‑moving, and we value engineers who can help bring structure and momentum without over‑engineering.

This is not a narrowly scoped role. We’re looking for someone comfortable working across the stack, making thoughtful trade‑offs, and improving systems incrementally as requirements evolve.

To get a feel for our dynamic, check out what our team hates about working at Nexus Leap:

We’re aiming for a simple, scalable foundation and expect this role to help refine details over time. Current direction (not exhaustive):

• Backend:
  Python
• Frontend:
  Type Script + React, HTML/CSS
• Data:
  Postgres, Graph
  
  QL, Redis, REST APIs
• Infrastructure: AWS, Docker, Terraform/IaC, CI/CD

We expect candidates to bring a strong foundation in software development and an interest in working across frontend and backend systems. Depth in specific technologies, years of experience, and exact tooling will vary by candidate and project.

If you’ve built real systems, learned from them, and can explain your decisions, we’re interested in talking.

More specifically:

• Production experience building and operating backend services (
  Python
  , Node.js
  , or similar)
• Production experience shipping web UIs in Type Script + React
• Strong SQL fundamentals
• Experience deploying and operating services in the cloud (
  AWS preferred
  ):
  Docker + CI/CD
• Comfortable with production basics:
  authentication/authorization
  , secrets management, logging/metrics, error handling
• Experience with data ingestion workflows and data‑heavy product UIs
• Experience creating UI components (React/HTML/CSS) in conjunction with backend
• Ability to modify open source libraries (Streamlit/Apache) based on custom requirements
• Ability to implement multi‑tenant B2B patterns (tenant isolation, RBAC, audit logs)
• Ability to own features end‑to‑end: clarify requirements → implement → deploy → iterate
• Familiarity with event‑driven systems (queues, retries, idempotency, dead‑letter handling)
• Deep IaC experience (Terraform modules, environment separation)
• Experience implementing observability with structured logging + metrics

• Web applications that support data ingestion, exploration, and analysis
• Backend services and APIs connecting data systems, dashboards, and AI/ML components
• Frontend interfaces focused on clarity, usability, and real user workflows
• Early‑stage prototypes and POCs that may evolve into production systems
• Incremental improvements to reliability, performance, and developer experience
• Help establish and improve our engineering patterns (repo structure, environments, CI/CD, testing standards)
• Make pragmatic architectural tradeoffs that prioritize maintainability, security, and iteration speed
• Document decisions so systems are easy for additional engineers to understand and extend

In the first…