
Mercedes-Benz Research and Development India (MBRDI) — the automaker’s largest R&D center outside Germany — is hiring for a Junior Backend Developer role under its Change Management department in Bangalore. The listing is officially titled “ACM Developer” internally, but the actual work is straightforward backend engineering, which is worth knowing before you apply so you’re not thrown off by the internal naming.
What MBRDI actually is
If you haven’t come across MBRDI before: it’s not a separate company but Mercedes-Benz Group’s dedicated R&D arm in India, headquartered in Bangalore with a satellite office in Pune, employing thousands of engineers and IT specialists on work that feeds directly into Mercedes-Benz’s global product line — not a back-office support function.
What this role actually involves
This is an entry-level backend engineering position, not a testing or support role despite the internal job title. You’d be building and maintaining backend services using Java and Spring Boot, working on RESTful APIs and microservices, and collaborating directly with frontend and QA teams on live projects — a genuinely hands-on coding role rather than a rotational trainee program.
Role snapshot
- Department: Change Management
- Location: Bangalore
- Start date: August 1, 2026
- Employment type: Full-time
- Level: Junior/entry-level
Skills required
- Solid grasp of core Java programming concepts
- Working knowledge of the Spring Boot framework
- Basic understanding of REST APIs and microservices architecture
- Familiarity with SQL-based databases
- Willingness to work through code reviews and iterate on feedback — this is called out specifically as part of the day-to-day, so candidates uncomfortable with critique on their code may find the environment demanding early on
What the hiring process typically looks like
MBRDI’s standard recruitment process for engineering roles generally runs through an initial resume/candidate screening, followed by technical assessment and interview rounds evaluating core CS fundamentals and role-specific skills, before a final HR discussion and offer stage. Exact rounds can vary by role and hiring cycle, so treat this as a general guide rather than a confirmed process for this specific posting.
How to apply
Applications go through Mercedes-Benz’s official Taleo-powered career portal. Make sure your resume clearly demonstrates hands-on Java/Spring Boot exposure — even personal or academic projects count — since this listing screens specifically for practical coding ability over just theoretical knowledge.
FAQs
1. Is this a fresher-friendly role or does it require prior experience? It’s listed as a Junior Backend Developer position aimed at candidates early in their career — the listing emphasizes willingness to learn over extensive prior experience, though basic Java/Spring Boot knowledge is expected.
2. What does “ACM Developer” mean in the job title? It reflects MBRDI’s internal department naming (Change Management), not the actual nature of the work — the role itself is standard backend development using Java and Spring Boot.
3. Is this role based in Germany or India? This specific posting is based in Bangalore, India, at Mercedes-Benz Research and Development India — MBRDI’s largest R&D center outside Germany, not a Germany-based role.
4. What is the expected start date for this role? The listing specifies a start date of August 1, 2026, so candidates should factor this into their notice period or availability planning.
About Mercedes-Benz
Mercedes-Benz Group AG is a German multinational automotive company headquartered in Stuttgart, one of the world's leading luxury vehicle manufacturers and a pioneer in automotive engineering since the invention of the automobile in 1886. Known for brands like Mercedes-Benz and Mercedes-AMG, the company designs, produces, and sells premium passenger cars and vans globally. For tech roles, Mercedes-Benz has increasingly positioned...
View Company Profile →Top Interview Questions
Prepare with commonly asked questions for this role
The four pillars are encapsulation, inheritance, polymorphism, and abstraction. For example, in a project I might use inheritance to share common fields across related classes, and polymorphism to let a single method behave differently depending on the object calling it — this keeps code modular and easier to extend later.
Spring Boot removes a lot of manual configuration through auto-configuration and starter dependencies, so you can get an API running with minimal boilerplate. Annotations like @RestController and @RequestMapping handle routing directly, and embedded servers mean you don't need separate deployment setup just to test locally.
A monolith runs the entire application as a single deployable unit, while microservices split functionality into independently deployable services that communicate over APIs. Microservices offer more flexibility to scale or update individual parts independently, but add complexity around service communication and data consistency.
@RestController
@RequestMapping("/api/items")
public class ItemController {
@GetMapping
public List getItems() {
return List.of("Item1", "Item2", "Item3");
}
}
Note for candidates: answer this with a real example — describe the feedback, how you responded, and what changed as a result. This role specifically values comfort with code review, so a generic answer here won't land as well as a real one.
