Great environment for freshers, but tough interviews
Pros: Superb work environment for freshers
Cons: But tough interview process selection
View on Glassdoor
Money Forward India headquartered in Tokyo, Japan has 1 active tech role on Feedback AI with AI match scores, optional skill assessments, and company insights when Glassdoor enrichment exists. Candidates browse open listings on this profile; signed-in users see ranked fit and skill gaps per role. Employers post jobs and review match-ranked applicants on the same platform.
1
Open roles tracked
0
Posted last 7 days
1
Posted last 30 days
Open roles at this company sorted by AI match score — skills, experience, and company fit when you are signed in. Guests browse the same roles on the public job board.
Want match scores and deeper insight? Create a free candidate profile
What employees say
+ Good team mates and nice office atmosphere
− Absence of clear vision Frequent changes in process and team
Recent Glassdoor reviews · 94 total
Pros: Superb work environment for freshers
Cons: But tough interview process selection
View on GlassdoorPros: Perfect WLB. Highly international environment.
Cons: Both compensation and career trajectory are quite limited. The salary is uncompetitive, and growth is stagnant. For instance, the salary for a two-year tenure can be significantly lower than that of new grads, even after multiple promotions.
View on GlassdoorPros: Good culture, Good tech to learn
Cons: Not great salary, Less services that actually have many users
View on GlassdoorPros: good culture , teamwork, work life balance
Cons: underpaid as a researcher, lab follows sterotype style of conservative research pathways
View on GlassdoorPros: 1. HR and management are very helpful. They reflect on the feedback very quickly. 2. So many interesting projects are going on. 3. Management care about the employees.
Cons: 1. Still, most people use Japanese as the main language. 2. They provide translation, which is insufficient.
View on GlassdoorCompany review data sourced from Glassdoor.
Glassdoor salary estimates for top hiring roles
| Role | Location | Median | Range (LPA) | Reports |
|---|---|---|---|---|
| Engineering | India | — | — – — | — |
Salary benchmarks are estimates from Glassdoor and may differ from individual job listings.
India-scoped Glassdoor interview reports · 21 total · avg difficulty 3.0/5 · 17 questions indexed
It was quite a medium to hard side interview....with dsa question in both the technical rounds. After technical there was a hr round which was mostly on behaviour questions after these i was given the offer letter.
Sample questions
The interview focused on backend architecture, scalability, database consistency, SQL/NoSQL concepts, and database querying. You explained frontend-to-backend communication, bottleneck mitigation, scaling approaches, and Django ORM usage. The interviewer identified gaps in practical experience with live applications, CAP theorem, replication, and NoSQL, and suggested studying real-world systems such as Instagram. Questions How does a frontend service communicate with a backend, and what layers are involved? How would you handle a backend bottleneck caused by thousands or hundreds of thousands of requests? How do horizontal and vertical scaling work? Which scaling approach would you choose for approximately 10,000 requests? What problems can arise with horizontal scaling? How do real-world horizontally scaled applications handle data inconsistency? Is using a central database a good idea in a horizontally scaled system? How is database replication managed, and can users read stale data from replicas? What is the difference between SQL and NoSQL databases? How did you query the database and handle transactions?
Sample questions
Was pretty much hard for the package they provide. Focused on DSA, Projects, Communication and knowledge on core CS. Three rounds totally and some got good panel members and some got bad panel members.
Sample questions
I had an interview conducted by the Intervue team where I was asked questions on CI/CD, Docker, Rails, and SQL. While I was able to answer most of the questions, I struggled specifically with a question related to CI/CD in the context of refactoring. I’m trying to understand whether that gap was the primary reason for the decision, as I would like to improve in the right areas. Any specific feedback would be helpful. Overall, the interview experience felt a bit abrupt, and I would appreciate more detailed feedback for future improvement.
The interview was scheduled via a direct HR phone call. The interviewer changed the question abruptly mid-discussion and appeared disengaged, frequently typing in the background, resulting in a rushed and unstructured interview experience.
Questions reported by interview candidates on Glassdoor; edited for clarity. Not guaranteed to match your exact interview.
Top hiring roles: Engineering
Last updated 18 September 2026
Want match scores and deeper company insight? Create a free candidate profile.
Browse all jobs · Companies hiring · Career insights · AI job matching · Naukri vs match scores