Java Fullstack Engineer

About Quipu Quipu is AI infrastructure for long-term memory, built for enterprises engineering complex systems—automotive, drug development, battery storage, and AI agents. We give every entity a single, audit-grade memory so teams can study cause and effect rather than guess at it. That means vehicles with component-level traceability and failure prediction, accelerated drug development with fewer risky experiments, battery systems with trusted cell-ageing models, and agents with a shared persona that never resets.

Working Model—please read before applying This is an on-site role at T-Hub, Hyderabad, on a 6-day working week for the first 9 months. We're building core infrastructure to a hard timeline, and we'd rather be upfront about the commitment than surprise you later. After the initial 9 months, the schedule moves to a standard 5-day week.

The Role A Java full-stack engineer who thinks in systems, not just code. You'll work on core platform services—building and operating distributed microservices that handle graph storage, streaming ingestion, and semantic retrieval at scale—alongside the tech lead and senior engineers. We're hiring 2 engineers and are open across the experience range:

• 2–3 years: you'll build and ship features across Spring Boot services and the Angular frontend, working within architectures designed alongside senior engineers, and steadily take on more design ownership as you grow.
• 3–5 years: you'll own architecture decisions on core services and be expected to reason about trade-offs and failure modes before writing a line of code.

What You'll Do

• Build and maintain Spring Boot microservices that form the core of a distributed graph memory platform
• Work with event-driven and streaming architectures — Kafka-based pipelines, backpressure-aware stream processing, and actor-model concurrency
• Model and query data across polyglot persistence: graph databases (Neo4j), distributed SQL (YugabyteDB), vector stores, and embedded key-value stores
• Develop UI features and integrate REST APIs in the Angular frontend
• Own features end-to-end: implementation, testing, deployment, and production debugging—with architecture ownership scaling to your level
• Debug issues across the stack using logs, metrics, and traces
• Participate in design reviews and explain your technical decisions with clear reasoning

Must-Have Skills

• 2+ years of professional experience with Java and Spring Boot in production
• Solid grounding in core Java: collections, concurrency, JVM fundamentals
• Working knowledge of REST API design and integration
• Hands-on experience with a frontend framework (Angular preferred; React/Vue acceptable with willingness to work in Angular)
• Strong SQL skills and familiarity with at least one relational database
• Exposure to messaging or event-streaming systems (Kafka, RabbitMQ, or similar)
• Comfort reading logs, metrics, and traces to find root causes in running services
• Strong debugging habits and curiosity about how systems work under the hood
• Available to work on-site in Hyderabad, 6 days a week for the first 9 months

Additionally, for the senior position (3–5 years)

• Solid grasp of distributed systems fundamentals: consistency models, partitioning, idempotency, retries, backpressure, and failure handling
• Hands-on production experience with Kafka or comparable event-streaming platforms
• Experience with at least one NoSQL or graph database
• Ability to reason about a system before coding it — design rationale, not just working code

Strong Plus

• Experience with Akka or Apache Pekko (actors, streams, cluster)
• Graph databases (Neo4j, Cypher) or graph data modeling
• Distributed SQL databases (YugabyteDB, CockroachDB, Spanner-class systems)
• Vector databases and semantic search pipelines (Milvus, pgvector, etc.)
• Python (FastAPI) for building service sidecars
• Exposure to LLM-integrated systems: prompt pipelines, extraction workflows, RAG architectures
• Infrastructure familiarity: Keycloak, Vault, Jenkins, Docker, containerized deployments on Linux

Who You Are

• You ask, "Why is the system shaped this way?" before asking, "What do I build?"
• You're comfortable with ambiguity and small-team ownership—no hand-holding, no rigid specs
• You debug from first principles and write down what you learn
• You communicate trade-offs clearly and can disagree constructively in design discussions

What We Offer

• Direct ownership of core infrastructure on a small team—your work ships and matters immediately
• Deep, unusual technical problems: bitemporal modeling, graph traversal at scale, streaming knowledge extraction
• Close mentorship from technical leadership on architecture and systems design