Backend Engineering Internship

Nada is India's first social network for arranged marriages. Matches come through the people a family already knows: relatives, friends and the community matchmaker, a role the app calls Community Member. The app syncs a user's phone contacts, builds a who-knows-whom graph, and shows how two profiles connect. It has been live on the Play Store and the App Store since August 2026, and the full launch is on 11 October 2026. Nada Network Private Limited is a DPIIT-recognised deep tech startup working from Noida.

The founder, Harsh Titoria, built the backend and runs product and engineering end to end. He was a backend engineer at Dell Technologies before Nada, after a BTech and MTech from IIIT Gwalior. You would be the second person writing code for the platform.

• Java 25 on Vert.x 5, asynchronous and non-blocking, with Guice for dependency injection and Gradle to build.
• Neo4j 5 as the primary database. The who-knows-whom graph, the connection chains and the feeds are Cypher queries.
• Redis 7 for caching, presence and real-time messaging over WebSockets.
• Firebase phone authentication with JWTs for users, and a separate admin login.
• JUnit 5 with Vert.x JUnit 5 and Mockito for unit tests, Testcontainers for integration tests against a real Neo4j, Docker Compose for local services, AWS Mumbai in production.
• An OpenAPI spec and a Postman collection for every endpoint, and a written test plan.

Backend engineering on a live product, with the founder reviewing every pull request.

• Build features. There is a written backlog for the next app update, across signup, profiles, the who-knows-whom graph, discovery and chat. You take a feature from its spec to a merged pull request: the route, the handler, the service, the Neo4j queries, the tests and the API contract.
• Fix bugs. Issues from the live app and the store review queue, each fixed with a test so it cannot come back.
• Take on new requirements. The launch brings users, and the requirements change weekly. You scope them with the founder and build them.
• Keep the codebase healthy. Tests and coverage for existing endpoints, test data for local development, and the cleanups you find along the way. Part of the work, not the whole of it.

The code that decides what one user may see of another stays with the founder until you have earned it, because a mistake there leaks personal data. Every pull request is reviewed by the founder, over screen-share for the first month, and an automated security review runs on each one as well.

Nada pays for an AI coding assistant for you, Claude Pro or similar, on a company account. Use it for the work. Three rules: you can explain every line it wrote before you open a pull request, nothing from production and no user data ever goes into a prompt, and the account is closed on your last day.

• You write Java, and your GitHub shows projects you built or contributed to, with tests in them.
• You know your way around Git and pull requests, and you read the documentation before asking.
• You can reason about asynchronous code, or you want to learn to and can show it.
• SQL or Cypher: you can write a query with a join or a path in it and explain the result.
• You are comfortable with graphs from your DSA course: adjacency lists, breadth-first search and shortest paths. The backend is a graph of who knows whom, and the task uses one.
• You have 24 hours a week, Monday to Saturday, about four hours a day, for three months, and a laptop that runs Docker.
• You are a student or a recent graduate.

Good to have. Neo4j or any graph database. Vert.x, Netty or any reactive framework. Redis. Testcontainers. Firebase. A Linux shell.

• ₹7,000 a month, an internship letter, and a certificate and a reference at the end.
• A paid AI coding assistant on a company account.
• Code review on every pull request from the founder, who built the platform.
• Your work in an app that is live on both stores.

1. Apply with the form and your GitHub profile. We look at your projects first.
2. Shortlisted candidates get a task by email: a small HTTP API in core Java from a spec we send, Vert.x optional, with tests for the main case. You have two days from the email to send it back as a GitHub repository link with a README that says how to run it. We run it and read the code.
3. If the task is selected, an interview with a member of the team about how we work.
4. A final interview with the founder, starting from your task.

Remote, with the camera on for calls. A short written check-in every working day and a short team call on working days. Company accounts for every tool.

Nada hires across gender, religion, community and background.