Xebia Interview experience Java Developer

Ajouté : 2026-05-10

[00:00:00]And about my rules and responsibilities, so I have developed several API in this project and I have written generic test cases as well. That is all about me.

[00:00:08]Thank you.

[00:00:09]>> [snorts] >> Sorry, I missed how many years do you have in the resume? I cannot find it.

[00:00:16]Around 4.5.

[00:00:18]>> 4.5. Yeah, yeah, sure. Okay, okay, fine, good.

[00:00:21]So, are you comfortable in Java concepts? Yes.

[00:00:24]>> For Java, right? Yes.

[00:00:25]Can you please briefly explain me what is encapsulation in Java? Yeah, so encapsulation it means it wraps data and method into a single unit. It is called encapsulation. And we can say like it is a key concept. We can say like key point like encapsulation means data hiding. Class variable are usually usually declared private and access access to variable is provided through public like getter and setter methods and it helps protect data from unauthorized access.

[00:01:00]Okay, okay.

[00:01:01]What is the use of setters and getters?

[00:01:02]Do you write any logic other than returning and setting that data?

[00:01:07]Mhm.

[00:01:08]So, set set Yeah, so in my project like I can say like I use setter for like set data and getter use for getting data.

[00:01:19]Indirectly we can say and with the help of do and we can use at the rate data also we can use for this directly if we want to use.

[00:01:32]What I mean is in the for example in the setter if I want to write some code, can I write in the setter code?

[00:01:38]Before setting the data into class.

[00:01:43]Is it Did you Have you ever written some code other than setting the data into the setter method? Mhm.

[00:01:51]So, yeah, we can write like well validation logic we can write inside it.

[00:01:56]Okay, okay. Okay, fine. So, that's they call it control access.

[00:02:00]To data setting the data we are validating the data. So, that's you are writing in the validation.

[00:02:05]Okay, fine. Do you know what is immutable objects in Java?

[00:02:09]Yeah, so immutable it means we can't change immutable object it means like we can't change state cannot be changed after it is created.

[00:02:20]Mhm. Yeah, so like all classes fields are usually we can say private and final.

[00:02:28]Okay. Yeah, and the class does not provide we can say setter methods also.

[00:02:33]Okay.

[00:02:35]So, all methods are like whatever the getters can we use getters? So, we we use like value set only through my constructor and we use only like setter only we can say.

[00:02:50]Setter or getter?

[00:02:51]Setter only.

[00:02:53]So, it does not provide setter only.

[00:02:55]Sorry.

[00:02:56]Okay, we don't provide the setter getter is allowed. Yeah, getter is allowed.

[00:03:00]Okay, fine. So, I will show you one Java program related to this one. Mhm. Second.

[00:03:10]>> [snorts] [cough] >> Yeah.

[00:03:18]I'm sharing my screen. Mhm, okay.

[00:03:22]Do you see the screen?

[00:03:24]Yes, sir.

[00:03:27]It's visible, right? Yeah. Yeah, visible.

[00:03:30]Yeah, so like you said for example, we'll just Yeah. We have employee class.

[00:03:38]Okay, this has three fields ID, name Department, okay. Like you said that private and final.

[00:03:45]Mhm. I already followed the rules and also you said that constructor constructor is also is there ID, name and this one I'm setting the values in the constructor.

[00:03:53]And here the getters.

[00:03:55]Mhm, okay. I did not write the getter for get ID and get name. So, this is get ID get name.

[00:04:02]Get ID comma get name. I did not write the full implementation here. Mhm. Okay.

[00:04:07]And then get department. Mhm.

[00:04:10]This is my employee class from here to here. Mhm, okay. So, now I have one more class department is a simple POJO class.

[00:04:17]It is not immutable.

[00:04:18]Mhm.

[00:04:19]Constructor setters and getters. This is normal POJO class with department ID and department name. Okay, mhm. Simple POJO class nothing here nothing is there here. Mhm. What I'm doing is I'm creating I want to create employee like immutable object.

[00:04:34]Employee is equal to new employee of one comma Gauss my name and new department one comma PD.

[00:04:40]Mhm, okay. I'm passing the department object to this constructor employee class. Mhm. Okay, now what I'm doing is in the next line I'm asking get department. Mhm. That means in the employee class we have a getter that is called get department. I'm calling this method here.

[00:04:57]And then I'm saying set department because the department has this one.

[00:05:04]Set DEP. Mhm.

[00:05:07]Okay.

[00:05:08]So, here I'm changing the name because here I have the setters and getters of uh department.

[00:05:15]Mhm.

[00:05:17]So, now my employee class is not anymore uh immutable because I can change the content of department. That means this one.

[00:05:27]This content.

[00:05:28]I can modify the value inside this one.

[00:05:31]Mhm. So, by calling the set department is equal to HR. So, I'm changing the value from PD to HR.

[00:05:37]Mhm.

[00:05:39]So, employee class is no because it is not possible to change the content of one comma Gauss because there is no setters in the employee class.

[00:05:49]Mhm. But there is no setter for department also, but there is a getter.

[00:05:54]Right? I'm using this getter get department rather than setter.

[00:05:58]Mhm.

[00:05:59]>> So, using the setter I'm getting the department. I'm setting setting the name. Set DEP is equal to HR. Mhm.

[00:06:05]So, now how to deal with this case so that others cannot change my department name.

[00:06:14]Department name.

[00:06:17]So, for this uh So, in this case we can say like employee class like immutable class, but it is actually not fully immutable.

[00:06:39]Yes. So, department >> Department is Yeah, department is the problem.

[00:06:44]>> Yeah, yeah. So, we can say like a department is mutable object because it has a setter.

[00:06:51]Yes, this is a mutable object. Yes. So, It has setter, yeah. Yeah, so we can say like even like department is final some we can We can say like if we like department final so still it can do like employee.getDepartment We can say like uh um mhm We can say It prevent the it prevent others from modifying the department. We use defensive copying we can say. Instead of returning the original department object we return a new copy of it. We can do it. Okay.

[00:07:39]So, where do I make change? Do you mean in which method I have to make changes?

[00:07:48]So, for this >> Or I can share or I can change share my code in your chat then you can copy paste and you can change the code so that it will work. Yeah.

[00:07:58]Uh Sure.

[00:08:07]Sure.

[00:08:08]>> [snorts] >> I'm stopping sharing my screen. Okay.

[00:08:23]You can share your screen and copy that in the notepad plus plus or notepad.

[00:08:29]Mhm.

[00:08:32]Is it visible for you?

[00:08:34]Uh yes. Okay.

[00:08:36]>> [clears throat] [snorts] [snorts] [snorts] [snorts] >> Shh.