Key Responsibilities

WHAT YOU WILL BE WORKING ON

- Designing and building backend services in Java and Spring Boot APIs, integrations, data pipelines.
- Modelling data in MongoDB. On Project, we want to get the schema right from the start: thinking about access patterns, evolution over time, and what happens at scale.
- Defining REST API contracts before implementation begins — spec first, code second. That means agreeing on the shape of requests and responses, documenting the contract, and only then building to it. If the spec changes, the conversation happens upfront, not after both sides have built against different assumptions.
- Contributing to frontend work in React and Next.js when features require it. You do not need to be a CSS perfectionist, but you should be able to deliver a working, coherent UI.
- Setting up and monitoring dashboards in Grafana and Graphite. If something looks wrong in production, you are the kind of person who investigates.
- Thinking seriously about system design on Project Swifty: service boundaries, scalability trade-offs, where we denormalise and where we do not.
- Writing tests that travel with the code — unit tests for business logic, integration tests across service boundaries, and contract tests where services talk to each other. We do not have a separate QA function, so the person who builds it is the person who ensures it works.
- Writing code that other engineers can maintain. Good tests,



clear documentation, and pull requests that explain the why, not just the what.

MUST HAVE

- 5+ years of software engineering experience, with most of it on the backend.
- Deep Java and Spring Boot experience. You have built and shipped production services, debugged them under pressure, and improved them over time.
- Strong understanding of data modelling — particularly in NoSQL. You think about how schemas evolve, not just how they look on day one.
- REST API design experience and the instinct to think about the consumer of an API, not just the producer.
- Enough React and JavaScript to work across the stack without slowing the team down.
- System design fundamentals: you can discuss trade-offs around consistency, scalability, and service boundaries without needing to be prompted.
- You treat edge cases as part of the design, not an afterthought. You think about what happens when the data is malformed, the third-party service is slow, or the user does something unexpected.
- You are direct about problems. If the design is wrong, you say so early rather than building it anyway and hoping for the best.

GOOD TO HAVE

- TypeScript, TanStack Query, or Next.js experience.
- You have been involved in the architecture of a recent system from scratch — not just inheriting an existing one.
- Experience with event-driven architectures or message queues.

📌 Senior Software Engineer I (Fullstack) (Tamil Nadu)
🏢 TALENTSHIP
📍 Tamil Nadu