About the job
Full details, eligibility and the selection process are available on the company's careers page.
Citi
Java Fullstack Developer
Posted 6 days ago
- Experience
- 0-2 years
- Location
- Chennai, Tamil Nadu, India
- Job type
- Full-time
- Work mode
- Hybrid
Interview prep · Full Stack Developer
How to prepare for this interview
Full stack interviews go broad: you will be asked about the browser, the API and the database in the same conversation. The strongest signal is a project you built end to end and can explain layer by layer, including how you deployed it.
Typical selection process
-
1
Online assessment
DSA problems and MCQs covering JavaScript, SQL and HTTP.
-
2
Frontend round
JavaScript fundamentals and a small UI task in React, Angular or Vue.
-
3
Backend and database round
API design, SQL queries, authentication and schema design.
-
4
Project deep-dive and HR
Architecture of your best project, deployment, then HR discussion.
Rounds vary between companies. Citi may combine or skip some of them.
Skills to brush up on
- JavaScript and TypeScript
- React, Angular or Vue
- Node.js, Laravel, Django or Spring Boot
- SQL (MySQL or PostgreSQL) and MongoDB basics
- REST API design
- Authentication (sessions, JWT, OAuth)
- Git
- Docker and basic cloud deployment
Likely interview questions
Open a question to see what the interviewer is looking for.
01 Explain the full request flow when a user submits a login form in your app.
How to answer:
Form validation in the browser, the HTTPS request, server-side validation, password hash check, session or token creation, the response, and how the frontend stores the auth state.
02 What is CORS and how do you fix a CORS error?
How to answer:
A browser rule that blocks cross-origin requests unless the server allows them. Fix it on the server with the correct Access-Control-Allow-* headers, not in the frontend.
03 SQL or NoSQL: how do you choose?
How to answer:
Use SQL for relational data that needs joins and transactions; document stores suit flexible, nested data with simple access patterns. Most apps are fine with SQL.
04 Where should validation happen, on the client or the server?
How to answer:
Both. Client-side validation is for user experience; server-side validation is for security and must never be skipped.
05 What is server-side rendering and when is it worth it?
How to answer:
HTML is rendered on the server for faster first paint and better SEO. It is worth it for public, content-heavy pages; dashboards behind a login often do not need it.
06 How do you handle file uploads securely?
How to answer:
Validate type and size on the server, store files outside the web root or in object storage with generated names, and serve them through signed URLs if they are private.
07 How do you manage environment-specific configuration and secrets?
How to answer:
Use environment variables, keep
.env files out of Git, and use a secrets manager in production.
01 Build a to-do app with an API and a UI in 90 minutes. What do you build first?
How to answer:
Agree on the data model and API contract, build the thinnest working slice end to end, then add validation, error states and polish.
02 Users report the dashboard is slow. How do you find out if it is the frontend or the backend?
How to answer:
Check the network tab: slow API responses point to the backend; fast responses with slow rendering point to the frontend. Then profile that side.
03 How would you deploy your project so it survives a server restart?
How to answer:
Use a process manager or containers, a managed database, environment-based config, and a CI pipeline that runs tests before deploying.
01 Tell me about yourself.
How to answer:
Keep it under two minutes: who you are, what you have built or studied that fits this role, and why you applied here. Skip personal details unless asked.
02 Why do you want to join our company?
How to answer:
Mention something specific: a product they ship, the tech they use, or the kind of customers they serve. Generic praise ("good brand, good growth") sounds rehearsed.
03 What are your strengths and weaknesses?
How to answer:
Back each strength with a short example. For the weakness, pick a real one that does not block the role and say what you are doing about it.
04 Are you comfortable with the location, shift timings and work mode?
How to answer:
Answer honestly. If you have a constraint, say it now rather than after the offer, and mention any flexibility you do have.
05 Do you have any questions for us?
How to answer:
Always ask one or two: what the first 90 days look like, how the team is structured, or how performance is reviewed. Avoid asking only about leave and salary.
06 Walk me through your final year project.
How to answer:
Explain the problem, your exact contribution, the tech you chose and why, and one thing that went wrong and how you fixed it. Interviewers dig into this, so know every line you claim.
07 You have no work experience. Why should we hire you?
How to answer:
Point to proof of effort: projects, internships, certifications, open source or competitive coding. Show that you learn fast and can take feedback.
08 Are you willing to sign a service agreement or relocate?
How to answer:
Many campus and fresher roles include a bond or training period. Read the terms before the interview so you can answer clearly.
09 Where do you see yourself in three to five years?
How to answer:
Show ambition within the field: owning features, mentoring juniors, going deeper in a technology. Avoid saying you plan to leave for higher studies soon.
Resume tips for this role
- Feature one end-to-end project with a live link, the stack for each layer and how it is deployed.
- Split skills into Frontend, Backend, Database and DevOps so recruiters can scan them quickly.
- Show ownership: "built and deployed" is stronger than "worked on".
- Keep tutorial clones off the resume unless you extended them significantly.
Free resources to study
This guide is written by the JOB_SPOT_360 team from common interview patterns for this kind of role. It is not provided by Citi, and the actual questions may differ.
Frequently asked questions
Can freshers apply for the Java Fullstack Developer role at Citi?
Yes. The role accepts candidates with 0-2 years of experience, so freshers can apply.
What is the salary for this job?
Citi has not disclosed the salary. You can ask about it during the HR round.
Where is the job located? Is it remote?
This is a hybrid role based in Chennai, Tamil Nadu, India, mixing office and work-from-home days.
What skills are required for this job?
The listing mentions Java, HTML5, CSS3 and Spring Framework. Expect interview questions on each of them.
What is the last date to apply?
No deadline is listed. Openings like this can close once enough applications come in, so apply early.
How do I apply?
Select "Apply on company site" on this page. It opens Citi's official careers page, where you submit your application. JOB_SPOT_360 does not collect applications and never charges a fee.