Transcript for transcript_12ivMMurvxYo6Cx1pELWGS1NrN2KgNKbp_1_1634_377b29d3d9f2_7.txt

transcript_12ivMMurvxYo6Cx1pELWGS1NrN2KgNKbp_1_1634_377b29d3d9f2_7.txt

[00:00:12]  I think it's a good thing.
[00:00:31]  I think it's a good thing.
[00:04:54]  Hi, Sai Kumar.
[00:04:56]  Can you switch on your camera?
[00:05:03]  Yeah.
[00:05:03]  Hi, man.
[00:05:04]  Good afternoon, man.
[00:05:05]  Yeah, the panel is just joining in from my team.
[00:05:10]  I'm waiting for him to join.
[00:05:11]  Just wait for two more minutes and they'll be here.
[00:05:14]  Okay, okay.
[00:05:14]  We'll be back on camera till then.
[00:05:16]  Okay.
[00:05:17]  All the best.
[00:05:17]  Thank you.
[00:05:18]  Thank you.
[00:05:32]  You can switch off your camera if you feel like.
[00:05:34]  Okay, okay, man.
[00:05:36]  Yeah.
[00:08:54]  Okay, Sai Kumar, you can switch on your camera.
[00:08:58]  I can take the first part of your interview and then we can move on with my tech team joining in.
[00:09:06]  You can start with your introduction.
[00:09:09]  Okay, okay, man.
[00:09:10]  Thank you for giving me this opportunity, man.
[00:09:13]  Actually, my name is Sai Kumar, man.
[00:09:15]  I'm a 2024 CSE graduate from the Vagishwari College of Engineering.
[00:09:19]  So I had like a one year of experience.
[00:09:23]  Focusing on like a front end from Unicloud technologies.
[00:09:26]  I specialized in building like a production ready applications, web scalable applications.
[00:09:33]  And also I'm passionate about like creating the user interfaces and web applications.
[00:09:38]  And I'm eagerly like, I'm eagerly looking for the opportunities like where I can contribute and grow and achieve my like a long term career goals.
[00:09:51]  Got it.
[00:09:52]  Can you let me know a little bit about your internships or experience that you have mentioned in your CV?
[00:09:59]  And from there,
[00:10:00]  my colleague will connect with you for the rest of the interview okay okay man actually like i had around one year of experience uh from unicloud technologies
[00:10:11]  i was focused to work on the front end part like mostly i was focusing on like a react js javascript html css and also like uh i was like collaborated with my backend team uh also and in one of the project like uh
[00:10:26]  i was done i was worked with the node.js express and sql also
[00:10:31]  So actually, like in my previous company experience, like I was supposed to be a part of the two projects.
[00:10:40]  So mainly like we had done the two projects.
[00:10:43]  Like the first one is like a property management setup, like which is a base application.
[00:10:47]  So mainly that application's aim is to like where the users allow.
[00:10:53]  Like to search or filter or they can delete or they can update about the like apartment facilities like what are the amenities what are the features are there in those particular
[00:11:05]  apartments so the users get supposed to
[00:11:10]  look in that particular application.
[00:11:12]  So we build this by like using the React.js, JavaScript, main or front-end application.
[00:11:18]  And the main like writing, we develop the architectural design by defining like component-based architecture.
[00:11:28]  So instead of like writing the
[00:11:30]  code again and again like by using the react j so we make it as like a reusable components like component based architecture so it makes like a
[00:11:39]  more easy like more faster and like wherever we require like we use those particular components and also like i was responsible to build some like a small components
[00:11:51]  like we are like maintaining a separate unity c component that is related to my own company so that is related
[00:11:58]  a separate unity c component so where like we are developing the different types of components and we are storing it in like unity's component and we are using wherever we want
[00:12:10]  and the next project is like a kenzo management portal so mainly like it is based on like a employee like a check-in check-out uh
[00:12:19]  system so this is our own product that was built for uh my company purposes so like uh
[00:12:26]  this is the like employee and uh hr management portal so where employees can log in they can track the task they can track their time like they can uh check their payroll so they can make check their like hr operations and all those things
[00:12:41]  So like this was the another project and also the main thing the main thing to develop this Kendo management model is and also the
[00:12:52]  we made a like role based access controls means like suppose if the normal employees can log in they can.
[00:13:00]  can able to see the different features like the admin users like who are the like managers or the senior managers team like if they log in like they will see the different features like if the HR logins
[00:13:13]  they will see the different features so for the role based access control we developed like for every
[00:13:20]  user we had different different types of features developed in that mostly like i was supposed to be a part in this project like for the front end and for the good back end
[00:13:34]  Okay, that's great.
[00:13:36]  Pradeep, do you want to move forward with the technical questions now?
[00:13:41]  Yeah, sure.
[00:13:42]  Hi, Saigwa.
[00:13:43]  How are you?
[00:13:44]  Yeah, hi.
[00:13:44]  Hi, sir.
[00:13:46]  I'm good, sir.
[00:13:47]  All right.
[00:13:48]  So you consider yourself to be more of a front-end developer.
[00:13:51]  Are you, you know, do you consider yourself flexible enough to do back-end related work or would you like to stay confined to front-end?
[00:14:00]  Yes, yes.
[00:14:01]  I am fine with doing the backend also.
[00:14:04]  Like in one of the project, I was completely focused on frontend.
[00:14:07]  And one of the project, like I was supposed to be part in the both frontend and the backend.
[00:14:11]  So mostly like I was familiar with the Node.js Express also.
[00:14:16]  Okay.
[00:14:17]  All right.
[00:14:18]  So.
[00:14:20]  React is your go-to framework, I believe.
[00:14:24]  React.
[00:14:25]  React is mostly a front-end library, sir.
[00:14:27]  It's a JavaScript library.
[00:14:28]  Yeah, I'm asking is that something you consider yourself to be comfortable working with or is there some other framework you consider yourself working with?
[00:14:36]  No, no, I'm comfortable with working with both library as well as the frameworks.
[00:14:43]  Okay, no issues.
[00:14:45]  I'm going to send you a code snippet.
[00:14:47]  If you could just quickly have a look and let me know what is a, you know, what is something wrong in there, if at all.
[00:14:57]  Okay, sir.
[00:14:58]  I will tell you.
[00:15:12]  This is a react code.
[00:15:14]  Don't you just go.
[00:15:27]  Yeah, I think everything is fine, but only one thing like here, actually, we are defining asynchronous function, right?
[00:15:34]  The use effect, but we are using the asynchronous function, but we are not defining with the await keyword.
[00:15:41]  Here, like fetch is like promised, like it will either resolve or it is rejected.
[00:15:47]  Like we need to mention like a await keyword.
[00:15:52]  We need to define with await because we are using the asynchronous functions.
[00:15:56]  So meanwhile, like if we use the async keywords, so we need to like.
[00:16:04]  Oh, Jim.
[00:16:10]  Like a...
[00:16:15]  Okay.
[00:16:16]  So if I was not using a sync, would there be any other way I could handle it?
[00:16:22]  Like if you're not using a sync, like we can also write in normal methods like a try catch blocks without using a sync also.
[00:16:32]  You can define it by try catch.
[00:16:35]  What about using dot then?
[00:16:37]  Dot.
[00:16:38]  Okay, dot then also.
[00:16:41]  Dot then also we can use.
[00:16:43]  Dot then like returns the search's callbacks and like a dot catch returns the error callbacks.
[00:16:48]  We can also use dot then also.
[00:16:51]  Any other possible way you could think of?
[00:16:55]  Yeah, mostly like a promise or else we can use with like a promise callback.
[00:17:04]  Okay.
[00:17:05]  Promise callbacks.
[00:17:07]  We can use dot then dot catch.
[00:17:09]  We can use try catch blocks.
[00:17:12]  Okay.
[00:17:12]  All right.
[00:17:15]  So where would you use a SQL database over a NoSQL database or vice versa?
[00:17:23]  SQL database is nothing but like we are defining the data with the rows and columns.
[00:17:30]  Like wherever.
[00:17:31]  we are having the like employee details or user details or login details like we will store uh
[00:17:37]  in the like sequence form like either rows and columns like uh no sql means like uh nothing but
[00:17:44]  the data format is in like a json format so mostly like we will use this no sql uh database for the larger data sets for larger applications
[00:17:55]  And we will use like a SQL for mostly that like the small database, small storing data.
[00:18:04]  Okay.
[00:18:06]  What about relationships between data?
[00:18:11]  Relationships between data.
[00:18:15]  Is that something you would consider when deciding between a SQL or a NoSQL database?
[00:18:21]  No, like actually mostly we will use like both SQL and NoSQL database.
[00:18:29]  But in some cases, we will prefer to use the like a non SQL database because it is used for the larger applications.
[00:18:38]  It makes the like applications faster, like it is very reliable and also it is very scalable, like it is very efficient, more efficient when compared to the SQLs.
[00:18:50]  So we can handle it very efficiently.
[00:18:56]  Okay, that's fine.
[00:19:02]  You have worked with JWTs?
[00:19:06]  Yeah, yes, sir.
[00:19:07]  Mostly, I heard about that and also I have worked with that.
[00:19:15]  Okay so can you tell me what they are uh like
[00:19:22]  jw mostly like these are used for the api authentications like json web tokens like it is a stateless and a lightweight api authentication methods so mostly we will use for the like a
[00:19:36]  login purposes or or so the jw contains like uh three parts like a header payload of signature so this jw
[00:19:46]  contains these three parts so now i'll explain like how how it works uh means like suppose one the user uh like a logins with the email and password so the front end the client sends the request to the server the server verifies
[00:20:01]  the credentials and it generates a token so then we will generate the like a json tokens so and that's
[00:20:10]  that server sends the json tokens to the front end and the front end stores it for the future request like suppose if the user again revisits the same application so it will check whether the
[00:20:22]  user is existing user or a new user so in that case like we will use the json web tokens like this is one of the like
[00:20:30]  most important API authentication methods.
[00:20:34]  Is there any other way you could do authentication apart from JWT?
[00:20:39]  Also, yeah, there are like a basic authentications methods, like showing some alerts or showing some data missing.
[00:20:48]  And also like there is one.
[00:20:52]  Open authorization or the or uh api authentication is also it is there so it is like completely dependent on a third party libraries or or means it is dependent on third party libraries mainly like a on google or a
[00:21:07]  uh like a github or any other platform
[00:21:11]  Have you heard of session-based authentication?
[00:21:14]  Session-based authentication.
[00:21:18]  Yes, I think I have.
[00:21:19]  Session-based authentication means it will store the token for that particular session only.
[00:21:28]  After the session closes or after.
[00:21:30]  After the session terminates, I think the tokens what the server generates, like it may delete from the session storage.
[00:21:41]  So these session tokens, where do they stay?
[00:21:44]  On the server or on the client side?
[00:21:47]  On the server only, session storage.
[00:21:51]  Okay.
[00:21:55]  Okay.
[00:21:55]  No choice.
[00:22:02]  Would you, so you have worked just with Express or have you also worked with Flask or FastAPI?
[00:22:09]  Mostly I worked with Express, Express.js.
[00:22:14]  Will you be, have you worked with Python at all?
[00:22:19]  No, I had like a Python.
[00:22:21]  I know the Python.
[00:22:24]  Like in my previous experience, I didn't work with the Python, but I know the Python, like how to write the APIs and all.
[00:22:32]  Okay.
[00:22:33]  All right.
[00:22:34]  So I just have to ask, so you were working as a full-time developer at Unicload?
[00:22:43]  Yes, sir.
[00:22:44]  So this role, however, is more of an intern related, which obviously it could be translated into full-time.
[00:22:51]  And you're okay with that?
[00:22:54]  Okay, yeah, yes.
[00:22:57]  Any reason why you left Unicloud?
[00:22:59]  Yeah.
[00:23:00]  Actually, like there we had completed the project, sir.
[00:23:04]  So actually the project is running for one, two years.
[00:23:09]  So the project is completed and mostly the work is based on like a net shoot only.
[00:23:15]  So mostly like I was familiar with the front end and the node and all these things.
[00:23:20]  So the project is completed and they're looking for the NetSuite developers.
[00:23:24]  So and also like I want to like grow, I want to grow like for my long term career goals.
[00:23:32]  Like I want to join in a company like where I can.
[00:23:35]  Contribute myself for a long-term career goals and I was looking for like a better opportunities so that's why like I have upskilled myself and I was like looking for the new opportunities
[00:23:48]  All right.
[00:23:51]  So, yeah, I don't really have any other further questions.
[00:23:54]  Do you have anything to ask?
[00:23:57]  Yeah, like I have a few questions, sir.
[00:24:00]  Like first, like I would like to know, like, what is the project like for my role?
[00:24:06]  Like what project I need to?
[00:24:09]  Do for my role.
[00:24:12]  All right.
[00:24:12]  So we have multiple projects working concurrently.
[00:24:17]  So it is possible that you will have to wear multiple hats.
[00:24:21]  Obviously, since it being a startup, we all have to do multiple roles at the same time.
[00:24:25]  We do have a tech team of three so far and you will if you do join you will be the fourth
[00:24:30]  person.
[00:24:32]  Mainly your task would revolve around the front end as well as some bits of the back end, but majorly on the front end.
[00:24:41]  And you would also be helping with creating data sets.
[00:24:45]  Okay.
[00:24:46]  For machine learning applications, I'm not sure if you have had experience working with those.
[00:24:50]  If you do, great.
[00:24:51]  If not, you'll get an opportunity to work with that as well.
[00:24:56]  And what are the technologies you have used most for the front-end and the back-end, sir?
[00:25:03]  So our entire front-end stack is React.js.
[00:25:07]  We are shifting some of it to use TypeScript now.
[00:25:11]  It was previously using just JS.
[00:25:15]  And it's, you know, again, mostly because it's much more readable if you're using TypeScript as opposed to JavaScript.
[00:25:22]  And for the backend, we do have multiple microservices.
[00:25:26]  Some are Express-based, some are Python-based, and some are Spring Boot-based.
[00:25:30]  So there will be some of these that you'll have to work on.
[00:25:34]  But, you know, first, to start off, we will obviously be putting you in just the technologies that you are comfortable with and working with.
[00:25:42]  But eventually, you will be required to learn the others as well.
[00:25:47]  Yes, yes.
[00:25:54]  Anything else?
[00:25:56]  That's it, sir.
[00:25:57]  Mostly I want to know about those things.
[00:25:59]  All right.
[00:26:00]  Thank you.
[00:26:01]  Also, I will locate to Noida because it's an in-office role.
[00:26:08]  Yeah, yes, ma'am.
[00:26:10]  Okay.
[00:26:11]  Okay.
[00:26:12]  Thank you.
[00:26:13]  Okay.
[00:26:14]  Thank you.
[00:26:15]  Ma'am.
[00:26:17]  Yes.
[00:26:18]  When will I get the further updates regarding this?
[00:26:23]  We'll get back to you in a week or so.
[00:26:26]  You can contact me if you have any questions in your head before that.
[00:26:32]  Oh, okay.
[00:26:34]  Okay.
[00:26:35]  Thank you.
[00:26:36]  Okay.
[00:26:36]  Thank you.
[00:26:38]  Okay.
[00:26:38]  Thank you, sir.
[00:26:39]  Thank you.
[00:26:39]  Bye.
[00:26:40]  Okay.
[00:26:41]  Thank you, sir.