Member of Technical Staff – Java Backend Spring Boot
· Kafka
· Distributed Systems | 4–7 Years ? T-Hub, Hyderabad (In office) ? 4–7 years of professional Java backend experience ? Full-time ?️ 6-day week for the first 9 months, then 5 days ? https://thequipu.com ━━━━━━━━━━━━━━━━━━━━ ABOUT QUIPU Quipu builds AI infrastructure for long-term enterprise memory. Our Knowledge Twin gives every entity in a complex system three things: its live current state, a causal history of what changed and why, and its meaning in a semantic graph. With that, engineering teams and AI agents can study cause and effect instead of guessing at it. Our platform already supports real enterprise work:
• Automotive: component-level traceability and failure prediction
• Pharma: drug development with fewer high-risk experiments
• Energy & storage: cell-ageing models that teams can trust
• AI agents: a shared, persistent memory that never resets THE PROBLEM WE'RE SOLVING
* Enterprise data is scattered across warehouses, event streams, documents and tools, with no single view of any one entity
* Most systems store the current state but lose the history
* Without that causal history, teams guess at root causes, repeat costly experiments and can't audit decisions
* AI agents have the same gap: no long-term memory, so thee trusted with high-stakes work Quipu fixes this by giving every entity one audit-grade meaning full causal history and its meaning, all queryable by people and AI. ━━━━━━━━━━━━━━━━━━━━ WHAT WE'VE ACHIEVED ? Commercial pilots with 2 Fortune 500 enterprises (pharma, US
· automotive, EU) ? Winner, Renault Open Innovation Challenge ? Winner, Maruti Suzuki Innovation Program (NSRCEL, IIM Bangalore) ? Selected for NetApp Excellerator, Cohort 15 ?? Selected for the IndiaAI Startups Global Acceleration Program (MeitY, Govt. of India), STATION F Paris. September 2026. ?? Alumni, Maria 01 Northern Light Accelerator, Helsinki. September 2025. ━━━━━━━━━━━━━━━━━━━━ ⚠️ PLEASE READ BEFORE APPLYING
• On-site only, at T-Hub, Hyderabad




• 6-day week for the first 9 months, then a standard 5-day week
• You need at least 4 years of professional Java experience. We won't consider applications below that. We're building core infrastructure on a tight timeline, so we'd rather tell you this now than surprise you later. ━━━━━━━━━━━━━━━━━━━━ THE ROLE We want a backend engineer who thinks in systems, not just code. Our platform runs on an in-house, event-sourced, bitemporal graph database with its own Cypher query engine, built with Java, Spring Boot, Pekko and Kafka. You'll own architecture decisions for the core services behind it: graph storage, streaming ingestion, ETL pipelines and semantic retrieval at scale. We expect you to think through trade-offs and failure modes before you write any code. ━━━━━━━━━━━━━━━━━━━━

WHAT YOU'LL DO
• Design, build and evolve the Spring Boot microservices at the heart of the platform
• Own architecture: service boundaries, data flow, failure handling and scaling strategy
• Build security in from the start: authN/authZ, multi-tenant data isolation and secrets management
• Build event-driven Kafka pipelines with stream processing that handles backpressure
• Build and run ingestion and ETL workflows across many kinds of data sources
• Model and query data across graph (Neo4j), distributed SQL (YugabyteDB), vector and key-value stores
• Own features end to end, from design through production, and debug them with logs, metrics and traces
• Lead and take part in design reviews, and explain your decisions clearly ━━━━━━━━━━━━━━━━━━━━ MUST-HAVE ✅ 4–7 years of production experience with Java and Spring Boot ✅ Strong core Java: collections,



concurrency and JVM internals ✅ Proven ownership of systems and service boundaries, not just single features ✅ Application security: OAuth2/OIDC, JWT, RBAC/ABAC and secure API design ✅ Production experience with Kafka or a similar event-streaming platform ✅ Hands-on experience building or running ETL and data pipelines ✅ Distributed systems fundamentals: consistency, partitioning, idempotency, retries, backpressure and failure recovery ✅ Robust SQL, plus experience with at least one NoSQL or graph database ━━━━━━━━━━━━━━━━━━━━ STRONG PLUS ⭐ Keycloak, HashiCorp Vault or production IAM integrations ⭐ Akka or Apache Pekko (actors, streams, cluster) ⭐ Neo4j, Cypher or graph data modelling ⭐ Distributed SQL such as YugabyteDB, CockroachDB or Spanner-class systems ⭐ Vector databases and semantic search, such as Milvus or pgvector ⭐ Python (FastAPI) for service sidecars ⭐ LLM-integrated systems: prompt pipelines, extraction workflows and RAG ⭐ Jenkins, Docker and containerised deployments on Linux ━━━━━━━━━━━━━━━━━━━━ WHO YOU ARE
• You ask "Why is the system shaped this way?" before "What should I build?"
• You do well with ambiguity and ownership in a small team. You don't need rigid specs or hand-holding.
• You debug from first principles and write down what you learn
• You explain trade-offs clearly and disagree constructively ━━━━━━━━━━━━━━━━━━━━

WHAT WE OFFER
? Title: Member of Technical Staff ? Real ownership of core infrastructure: what you build ships and matters right away ? Hard, uncommon problems: bitemporal data modelling, graph traversal at scale and streaming knowledge extraction ? Close mentorship from technical leadership on architecture and systems design ? A small, high-ownership team building for Fortune 500 clients ? Apply here, or email your resume to [email protected] #hiring #java #springboot #kafka #backendengineer #distributedsystems #hyderabadjobs #thub #startupjobs #AIinfrastructure

📌 Member of Technical Staff (Hyderabad)
🏢 QUIPU
📍 Hyderabad