good afternoon friends Sergey kromchenko here from Los Angeles California the founder of cremify online boot camp where you can find us is couldn't find.com anyways today we're having an interview with the two awesome guys actually it's going to be a discussion of the interview questions so I can ask some interview questions they will answer we're going to discuss them they'll ask me questions I'll answer them we're going to discuss it afterwards and find out what are the best answers and what do we need to improve in order to have a much higher chance of getting a job this is my favorite interview literally I I don't think we have something as valuable as this one because you guys going to be able to learn what questions do they ask during interview process number one and the most important how to give the best answer ever to get the job and you will hear things that we've heard during our our interviews you will hear our responses and you were here you will hear if we got the job or if we did not get a job after such an answer anyways before you start don't forget to give big fat thumb up subscribe to our Channel below join our Instagram and telegram communities in the links in the description right underneath of this video enjoy it [Music] Let's go Team good to see you guys good to see you sorry all righty um welcome on board everyone we're good at Georgie and Anton right here uh some of you guys have already seen Anton uh let's start with Georgie you want to go ahead and introduce yourself because these two people are uh are wolf pack or what do you call them the first group that we've ever had at condemnify official group we had one guy before them but this is the first two students that we have ever had officially that yeah that's that was exciting time uh yeah hey everyone my name is Georgie um I'm originally from Ukraine but I'm based in La now I moved to us in 2016. um and I'm working as a senior care automation engineer at the moment thanks to Sergio yeah and to his academify course that's a brief overview if you want to ask me questions yeah feel free to throw introduce yourself as well just in case we have people who have not seen our video yet which we should appreciate which we're gonna attach right there or maybe right there somewhere in those spots but yeah basically my name is Anton I'm also from Ukraine um actually right now I'm living in Vegas before I was living in L.A so I'm currently working as a QA engineer my you know stuff is split between like 50 automation fifty percent manual but yeah that's kind of pretty much it awesome alrighty and so Georgia is in La Agora Hills and uh Anton is in Vegas Vegas right now right that's right that's right all right yeah it's it's good thing you can work like from anywhere else right you can work from Ukraine as well yeah I mean if we're interested in we're good yeah you want to take a trip right now one way yeah do you like double work help out like other that's true that's true alrighty well uh let's get started with the interview so what you're going to do is we're just gonna go through questionnaire that everyone usually goes during the interview and one of us will pick it up and answer it and three of us are going to discuss that afterwards to see what we could improve was good or what's not and usually interviews start with a question tell me about yourself uh so if any one of you guys want to pick up the question and give an answer to it maybe you can bounce off of my um so basically I'll give you the answer first and then I'll kind of give you the reasons why I structured it in a particular way so say hey guys thank you for giving me the opportunity uh to talk to you and uh possibly get in this position uh as of myself I've been a QA engineer for past five years for the past two years I've spent at company X for the last three years I spent the company why current company basically specializes in you know X Y and Z and I would I would kind of explain what it is and um you know some of the tools that I'm working with include let's say uh web driver IO uh together with mocha and chai libraries I would use gr for bug tracking and I would use test rail for test case management I would use Jenkins for CCI CD um and and I think that's kind of pretty much it gives you kind of surface love understanding about my about myself if you have any more follow-up questions I would love to answer those awesome can can we actually give the full answer with the company you're working for right now so people would hear the actual answer that you okay yeah I just anyone I didn't know if you wanted to kind of disclose certain things or not but yeah I can definitely uh give the full answer right now okay so thank you guys for giving me the opportunity my name is Anton and I'm currently working uh for for the past four years I've been working as a QA engineer for five years um and I'm currently working for the company called Fortress Technologies uh the company specializes in Property Management uh we provide the software to uh quality buildings and commercial real estate to be able to manage your properties more efficiently um and uh some of the tools that I have used in the past that I'm currently using include Jeff for bug tracking web driver IO together with mocha and chai libraries for UI automation Postman for API testing um some testing for uoi tests so it's basically like an online tool where you can do it everything without coding Jenkins for CI CD and um yeah that's kind of pretty much it if you have any more questions I would love to answer those perfect sounds good uh yes usually that's how and people answer this question and in my opinion there was pretty much excellent because you gave the basics of the company what they do right can you explain you explain that and then you've told what tools do you use this company at this company and usually recruiters for key managers whoever is the interviewer would ask follow-up questions based on his speech and what I think was it wasn't bad but what I think was missing I mean it was possibly the space left by Anton for them to ask questions about is his role what is exactly he do at his role so as the QA manager whoever is the interviewer I will ask hey could you please tell me a little bit more about your uh your job duties what do you do on a daily basis and what what are your responsibilities for the current job yeah that's that's exactly right that's why I structured this answer even right now when we're preparing sharing for interviews I say you need to say kind of almost the bare minimum but uh still be able to answer the follow-up questions because you don't want to go into a really really long spiel you know where you're sitting and talking and talking you're branching off things left and right and you might say things that they didn't even ask you and you might even have the possibility of messing up so like you said you know hey you know can you describe to me like what do you do like a little bit more about yourself and say yeah sure definitely like you know I'm responsible for all QA related processes right it's you know test case management it's where they're like documenting writing test cases automating test cases uh doing some exploratory testing which is manual testing um you know and you know automating stuff so when I'm able to kind of give that answer um as a follow-up as a to a follow-up question I think you know it's a we play game almost like question answer question answer and it's not necessarily a question and let me cover everything about me in one answer because then it just kind of becomes really messy and not very specific so exactly that's one of the biggest mistakes that our students do they talk too much this you know when people ask them hey can you tell me about a release process and the person starts talking about a release for the two words and then the person starts talking about agile and I'm like why are you talking about age I was just talking about a release clearly nothing else so that was that was an excellent answer um all right and then yeah uh can I can I add something to that um yeah like I would answer the same way as Anton I agree like too uh tell less uh and like follow answer follow-up question would be great I also like uh always kind of like try to build a connection between interview and interview interview guide so I usually tell like more details about my personal life about my hobbies you know and kind of like set the vibe uh for the interview so it's probably also a good idea you know what's actually interesting uh one of the uh job positions that I was interviewing for uh the first call that I had with the guy actually within the company uh after my initial call with the interview with the with the recruiter the guy tells me hey I don't want to hear anything about your professional career just tell me about you like who you are as an individual well I was like he's like I'll try to understand whether you're the right culture fit for a company and then we can move on to the next things so so it could be either or you know sometimes they want to you know have like a more technical stuff they want to sometimes have a combination of things like You're yeah like you're saying Georgie or you know like that guy asked me he's like I don't want to hear about nothing just tell me who you are as a person so as well yeah that's a good point like I from my experience like I've never had an interview where uh we haven't talked about anything unrelated to you like to the jobs you know so we're like we're usually oh okay what do you do like when you're not working what's your hobby you know it's like it feels like a relationship before they even hire you so it's like it's really good to mention exactly that makes sense that's awesome that's awesome I usually I usually tell all the students that you know whenever you are getting the answer tell them about yourself you only talk about your job duties about your past experience and then if they want they will ask you a question about a personal life that sounds like Georgia does give him a little bit a little bit of a hint of what he does in a spiritual time which actually is also a good point because you you're building connection with them uh and that's awesome yeah I think I'm gonna add that up to our course and tell everyone that after you give them a speech about spiel about your professional duties then you tell them and also during and also during my spiritual time I like to play soccer or do gymnastics yeah that's awesome all right let's move on that was a good one all right so yeah those are usually it's the first question telling by themselves and afterwards uh sometimes uh well usually they ask follow-up questions based on your answer and then the sometimes ask about the company itself like hey can you tell me a little bit more about the company can you tell me what what does exactly come what does what does your product look like and what what are they building does any one of you guys want to talk about that um I can try it oh go ahead okay yeah it's very specific though uh so yeah I would I would say that um I'll I basically can talk about my current company right is that what we want okay yeah so I would say yeah that um our company is called audit board uh and we're providing a software for uh risking compliance management system so and we have kind of nine products that we split up between like teams and I'm part of upside team and um that my duty is doing it like within this team is basically creating all the uh stories and tickets that are coming like my way before the release automating everything and uh keep up with the maintenance and like new tools observing like what what we're gonna go next awesome awesome yeah it sounds like something very specific to audit which most people will not know but from the interviewer perspective I will hear okay this guy knows what's up because he knows that he's talking about the different products he's talking about the team that he is he's in he's even started talking he's even started the conversation about his responsibilities which will be which will bring on the next uh conversation that we're going to have yeah definitely there's actually like I think about it in um you know in kind of two different ways how you could answer that question um if sometimes I would like to go maybe like that short and sweet saying hey you know here's my company like let's say Fortress Technologies and we specialize in providing uh management software you know for commercial and residential properties um so I think even answering just that kind of answers that initial question but you know you can always have that uh like a follow-up statement saying hey if you like to hear any additional details I would love to answer that because what I've actually noticed in one interviewing the students of codemified sometimes they tell them hey you know tell me about the company and then they start going into like micromanaging all the processes and listing all the things that they do and yeah it branches out again into you know two different things whereas could have been just like you know question answer really quickly so yeah yeah exactly that usually happens because people are nervous they and if if the interviewer is quiet if you give an answer and the person is just looking at you you're like okay I must have said something else and you start talking more and more and you're going into the rabbit hole as they say you ask here uh which makes sense so you pretty much have to become what do you answer you have to be confident uh with your answer and finish it on on a good word and possibly tell them okay and let me know if you have any follow-up questions or something like that yeah awesome all right uh well do you guys want to give us before I start with list of my questions that I've gathered from all the students we had so far do you want to throw any of the questions that you have recently had during your interviews um is it manual or automation what are we focusing on either or let's start with the manual because I think most of the people will be interested in the mail but we also can go into automation uh later on I see so I think like yeah okay okay I'll go so um I think there's a lot of like startups coming up and I think it is important to know that sometimes when you're being interviewed for a position you might be that first person who's interviewing who's been interviewed for that query position so I I haven't been asked that question myself but I have heard about people who have been asked this question and the question is like you know as a first QA what would you do right and you know I've heard some ridiculous answers like hey you know I'm gonna message everybody and say hi and like I'm listening and it's a very personal answer versus you can um you know tell them say hey I'm gonna learn the application I'm gonna go through the logic I'm gonna see you know what kind of documentation you guys have in place I'm gonna see if you have any test cases and you know I'm gonna go ahead and connect like with developers to prepare for for future regression and stuff like that so be able to kind of speak the language of how I'm gonna directly benefit um as a an employee towards like you know releasing the product and from the QA standpoint rather than having some um interpersonal skills uh answer you know soft skill stuff so I think that's kind of one of the questions that you should definitely pay attention to yeah yeah that makes sense and I can take this one I can answer it because I've done I've done it multiple times I've been working as the first kid in a company so that and also when I when I was working as the QA manager uh for the last couple of companies I also I can answer it from the perspective from the expectations of the management what do they what do they actually expect so first of all whenever you guys joining the company you will always you will always go through onboarding process if it exists in some startups it will not exist but I'm gonna tell you okay here's our application learn it or here's the documentation learn it so whenever you join it there's no boarding process at all you're the first one and for example one of my first companies had only four Engineers that was fifth one I believe I was like okay awesome I'll learn it myself not a problem at all first question what requirements do you have give me all the documentation give me all of the design tablets give me everything that you have so I could learn it based on that if and we'll we'll go from there if they say we have no documentation there are only tickets in Europe I'm going to fully dive into your number one and number two I'm going to have while I'm doing this I'm also going to have meetings with every single person from the team from the engineering team so I would learn things about the product from their perspective uh what was built what was built lady what was built lately what is getting built right now and how do they like the process because there might be something missed in the process so learn application that's number one you can learn in multiple ways that I've just described thing number two is start supporting the most critical part which is most cases release if it's a startup when I joined my first one it was so messy during that time so I've started helping the number one with the actual release I took it as the one of my responsibilities I was checking the code and pushing it to production but before that I have standardized it through through adding a list of number one test scenarios because we did not have a time for test cases so simply I would say uh test the login with this this that's the login of a positive test case you can log in test login but you cannot log into incorrect password pretty much use the titles for the test cases uh just to remember just to have a list of the test scenarios and then later on when I had time I did fill them out but first of all I had a huge list of things that we had to check uh that was number one and then number two is within within one week I've understood okay this is not very scalable we have to start automating this so the most critical list of the test cases had to be automated and they were automated by that time it wasn't very professional but it was done somehow it was runnable it will it helped me so much to get rid of them uh an hour of work every single day for the release process uh and after that uh documenting test cases and improving uh improving after about a month of watching what is happening within a company within a release process starting to uh negotiating with the team improvements because everyone will have a different video but you can all come to to collaborative decision of what needs to be improved and usually you ask the new person when you join a company you will have the best uh what do you call it the best Hive you will because everyone already got used to the fact that okay we are releasing in such a way and that's okay even if it's even if it's a shared list process you still get used to it like okay that's probably all right but a new person will always tell you that doesn't look right we could possibly improve that yeah that definitely makes sense what she said it's a lot more kind of elaborate than what I have mentioned um but I yeah I think that kind of if you give that answer specifically I think it would make make you look like you definitely know your stuff uh because you basically broke down uh you know various steps that you would take uh in in various parts whether it's um uh you know testing uh the application itself or learning the application so I think it's definitely a solid answer already yeah and and you've mentioned automation I think like uh Anton like is covering like manual part but if you're applying for automation like position they usually can ask you a question if you need to start automation from script from scratch what would you be your steps and processes so you wanna answer for this one also Sergey sure unless you guys or I I can try to yeah what what was my answers previously uh it's like pretty short answer like always kind of like for my understanding so basically the first answer would be it's like how many resources do we have like to uh start like building automation so we need to come up with kind of like uh solution okay whether we need to use this tool how much money we have for for example for awes paying for AWS or like any other CI tools secondly it's like time and wise uh like how short term it should be automated then we'll kind of and decide what's the quickest framework we can use right to automate such a tests and third I guess is just like diving into the requirement and like understand what we have already automated maybe it's like some other like Frameworks already been used and we need to migrate them and Etc so that's my kind of like short answer yeah yeah that's a good answer and based on that answer I could ask follow-up questions such as and actually I was asked the question during my second job of for interview I mean before I got my second job offer there was the question that I get asked uh if our if our stack that we use I mean if the language that we use for the website is for example python can you use can you does it matter which language do you use in writing your automation framework uh I think like the the easiest languages would be JavaScript to automate a front-end so if they don't mind like to use like different language I would like proceed with the JavaScript and the most familiar one that you know instead of like once again it's a timing question so they probably hiring you to start automating from day one and uh yeah you need to go with the tools that you're already aware of and you know yeah yeah yeah yeah definitely that's right that's right uh way to do that but the question would be uh does it matter which language we use does it have to be the same as it's used for the website or can we can it be different uh no it can be different I would say like I went through the same way and I got a job seven years ago yeah some people some people will say that it should preferably be the same language as developers use because they will be able to help you or they will be able to also write automation tests but usually that's not the case usually developers never write your automation tests so it is qa's responsibility with your right which language to use to write your tests on that's totally true in the case of uh because I'm actually not sure about this one uh in the case of when you have a website that's built on python uh do they actually write unit tests in python as well yep yeah yeah so if you want to if you want your integration test or end-to-end test to use the same language as unit tests for the reason that developers write it maybe developers one day will switch to this which happens it doesn't happen in 99.99 of the cases then you could possibly offer that but as Georgia said usually you they hire you they want you to start writing tasks quickly and if you are very familiar with the JavaScript you start using JavaScript if you're if you prefer to do it in a python YouTube python so in I agree with Georgie my opinion it does really make any difference and I got my second job when I answered it this way but it's it's I would say it's a personal preference if you want to do uses that language or the other language yeah all right let's move on to your next question I think Georgia had this one uh Anton you want to go the next one or should I pull one for my license uh yeah I I there's another question that I was asked um at the previous company that I was getting interviewed that which was age of learning and the question was like how good are you at automation so where basically I was joining the company or I was joining the department um where I would be the only QA because it's a big 600 company and they had a separate manual team um I think of like 50 people or so and I would be like the only automation engineer in this particular uh part of the application so I got asked that question and um I think this question definitely startled me but I think it could start everybody because like how good are you at something like am I gonna totally like boast about myself where I'm gonna downplay it so I I think my my answer was something like hey you know I was able to build before a like a simple framework from scratch you know writing some UI test case a UI animation test cases using you know Webdriver IO together with mocha and China libraries and you know I utilize like let's say page objects and stuff like that so I didn't give him saying okay I am good or I'm really good or I'm like terrible but rather I show you like what I've done and I'll let him judge based on that because my perspective of being good might be totally different would be your surgery perspective or your perspective of what is good like you know to some people saying oh I've used page object model it would be like you know and some people would be like yeah I just couldn't have a model you know so you never like I feel like you should never say like oh I'm good or I'm bad but rather State what you have done and let them be the judge whether you're good or bad so yeah yeah definitely and whenever this they ask this question they they actually we want to hear a couple of things number one they want to see your character they want to number two they want to see how humble you are um and then number three they do want to know what do you really consider um being good or not and if you if you would answer them that way that you did that you know what can the word how the word good can have a different meaning for everyone so let me tell you what I really think uh what I've done and you will judge if it's good or it's not good in your opinion yeah that's a really good answer but I would always just make fun of it I would say I'm as good as a two hours old Pizza I can get something like that just so everyone would laugh and then it would start a conversation afterwards yeah plastic surgery sensor yeah so Anton like answer is like very conservative and professional but this is tricky question and usually like if you joke out of it that's like good yeah I think like I asked this I've been asked this question once and I said oh I'm very good that you've never met this person before so and they were laughing at it yeah and also when you answer it this way you kind of show them your once again you show them what they want to see you show them your character you show them your personality and the fact that you're a good team player you will make fun of the things that uh that in most cases will be considerable fun yeah all righty let's move on to your next one Georgie you want to take the next one or shall I um yeah go ahead uh all right let's see so uh this is an animation question but this is a very basic automation uh key automation engineer asked that question what automation stack do you use so the word stack might not sound familiar to some of the people who came out from the boot camps uh because it's just something specific so they could also ask hey can you tell me about what automation tools do you use uh but they or what uh what I would call it Frameworks and languages do you guys here for automation they could ask that way but they actually ask what's tag you use by that they mean every single tool that is here for the Automation and also if they ask what stack do you use they could also mean what type of the database what is the what is used for the backend what Frameworks where languages what Frameworks and languages are used for the front end and then also for automation so when they ask you what stack do you use I just double check with them hey are you talking about automation testing or you're talking about if uh false the actual stack of the website that or application we're working with um are you can I think break it down also if we're just saying are you talking about like um stack for UI automation or API automation because those are different too it will definitely depend on the position that you're applying to but it never hurts to kind of clarify because I A lot of times they go based off of what you have in your resume so you know that they'll look and say okay this guy's been using Webdriver IO to get it with mocha and chai yeah but is there anything additional to that right yeah so yeah it never hurts to clarify it yeah yeah so uh first thing you clarify then you share them and in let's say in my case that would be so for the UI automation I for example for example I use Webdriver IO Maca and chai libraries as well for the API automation I use access which is node.js based as well as web driver i o is and for the application if you want to learn about that for the database we use postgres for the back end we use express.js for the front end we use react and that'll be pretty much it and also we're using AWS to host our server on but this is kind of the very technical details that most of the people on the junior level or mid-level will not likely know especially about where is the website hosted is there a digital Ocean or AWS or anything like that that's not necessary answer but the more you know the the more deeper knowledge you show them you show them how experienced you are but don't be afraid to answer in a way that you know because they don't ask you for anything else yeah very strong alrighty um Georgie you want to go in the next one um yeah it's not the technical one and this question you will hear like during every interview I believe and the question is what are the challenges you faced in in the last company uh do yeah Anton do you agree with me I feel like this question is pretty common yeah definitely even uh during my last round of interview uh it was phrased a little bit different um basically when I was interviewing in front of the panel I was asked hey um have you ever had any conflict with some people with people that you're working with or conflict in the workplace so I think that also kind of can be put in a similar bucket as like challenges right um and um to that question I answer I say well honestly to be like I'm a very personable person I typically get a get along with everybody um you know we I did have certain disagreements with you know so and so but we were able to kind of work through those out and maybe that disagreement was you know which assertion Library are we going to use right or which test Runner we're going to use and why is like axios less uh well less good than I don't think that's proper language but why is axios not as good as super tests or something like that so maybe you can give them a not necessarily a big conflict that you had or a huge challenge but at least you can kind of give them something that you can easily explain and it's easily understood because I feel like if you were to go too deep into the the some challenge where you're trying to solve they might not even understand what you're talking about so I think it's always easier to go simpler way and yeah going back to the same point always be straightforward don't give them do not volunteer too much uh do not volunteer any information as my lawyer told me before the interview I'm sorry yeah I just want to like kind of um answer this question uh the challenges related to my last company I always like ask them the following question uh what are the challenges are you talking about exactly is it technical challenges is it like uh maybe challenges with the release or a DLC process or something like that so they usually pick one one of those three and then you can answer like this question yeah it will be much easier yeah for sure that's what I was going to say that was my second point that you can okay yeah yeah same thing that uh I would double check you're talking about the technical challenges so we're talking about the uh conflicts at the workplace uh before answer it yeah but otherwise I would answer the same way right right and then like yeah I don't know you can come up with any any kind of like Technical Solutions right you say okay our I don't know like I have usually like blockers with I don't know pushing to GitHub because we have like a bunch of conflicts right or something like that uh throughout the course you will probably like uh come up with some ideas but that's usually a good idea just to talk to the interviewer and like ask follow-up questions don't be kind of shy and yeah yeah exactly and during the course usually uh we teach we teach different things every group gets different things but one of the things that right a previous group group learn is how to integrate how to automate OTP uh which pretty much your phone number log log in with the phone number how do you uh how do you automate that so people have learned how to do that and during the interview they were able to explain oh yeah the most challenging thing was OTP uh automation uh because because of this this and that and I've used this this and those tools in order to get that automated it took me a couple of days but I enjoyed it a lot and then pretty much you tell people that I had a challenges I've sold them and I'm looking for more I like that and that's the best standard you can answer you can give unless you're going for uh for a great environment company that doesn't want you to grow which will not uh which you will not meet very likely and very often yeah all right let's go through some quick questions because we're already past half an hour and I feel like people are getting bored so let me I think Georgie had a question we had some solid information for them nobody's gonna get bored of having somebody yeah yeah yeah wow all right let's keep going until you guys give me hard stuff because you both have meetings I do not have any today all right so the most often often asked question for the automation position when you're talking about it node.js or JavaScript is what is the difference between VAR let and const I literally asked my students during every lesson uh doing every webinar the question because I want every single person to know the difference uh because if you're if you're talking about a language that you've learned you should know the basics and these are actual Basics that you should remember by heart Mexico I can go I mean uh if you if when you if you have somebody asking that question I'd be like well okay so let's say bar right it can be really clear reassigned you know like could be uh re-eclared uh and cannot be reassigned and um you know cons cannot be reassigned or redeclared and then you know I typically never get any sort of follow-up after that yeah yeah they just know that you know the difference between these three yeah they leave it at that they're like okay you know it's it's I don't think ever anybody asked me about like but is it Muto is const mutable or stuff like that I think horoscope yeah yeah I think it's it's like really not I mean not a high level but I think just nobody even cares about that yeah yeah yeah definitely that's that's the good Basics as you can say a high level that in most cases it will be way enough for you to say hey I'm filming with the basics of of jazz and here they are definitely yeah awesome all right let's move on to the next one you guys want to take it um yeah I mean if we if we want to like talk about something uh let's say uh manual stuff you know some people get confused about um test cases and let's say bug reports I don't know why like I think even myself at some point I got confused about like what's this case and the bug report but that was like very very early on you know in the process when I was initially applying to companies and interviewing uh but sometimes you do get asked the question like what is a uh you know difference between a good test case and a bad test case right um and you can say well the good test case has you know easily reproducible steps right uh where you know you have essentially um a an action and a reaction in the sense that you know here's the action that you take and here's where you're supposed to expect right a bad test case is something that not easily followed right if I was to give it to a random person can this person if this person cannot reproduce all the steps 100 that means that the test case is poorly written and I think where the confusion between the bug group or it and and the test case comes is in the steps to reproduce right so and I I think it's important to differentiate that the bug report just focuses on reproducing the steps for a bug versus test case reproduces the steps you know for testing particular functionality and you know how that works um and just to kind of balance into like the good or bad bug report right it's kind of also similar so they would say Hey you know can you tell me how you would write a bug report right and I say well typically typically I would I write the title that's very descriptive but yeah concise you know say you know I'll describe what happened where it happened and under which circumstance it happened right so let's say you know the you know like a some particular menu button doesn't work on on the home screen right that's you know that's pretty descriptive but yet super short you you give them saying hey this button doesn't work on this screen when it's clicked right or something like that so and then in in in the short description if it's necessary if it's not understood by the title then you can write this short you know sweet description add the steps to reproduce um the bug as well as maybe attaching some visual sometimes I actually attach gifs um that are like six seven seconds long um sometimes I attach like screenshot with some arrows pointing to different places sometimes if it's a it has like a variety of steps that you know that needs to be recorded on video that's what I do I just attach a small clip that's you know 15-20 seconds so I think though that's kind of like really valuable especially if you're going for positions that are manual and even 50 and 50 you know 50 manual 50 automation so that's true that's true yeah and I think that's a good one yeah I think uh We've we've gave quite a few questions throughout the different levels and different topics so let's see how do people digest it and whenever you guys watch this video please leave a comment below and tell us uh what what do you mostly want to hear about manual automation senior level junior level mid-level uh so we would so we would see how how you guys liked it and what if should we record next because I feel like we can go forever with you guys we can literally keep discussing this for like two three hours but I don't think people will uh will be watching for that long at least that's what I think but you guys let me know how do you like it you can you can you can break it down into like introduce here yes and and uh it could be you know a question from the audience if they're going to leave any questions and under the video below and then you know either myself you know us three or somebody else can jump ahead and address those questions so I I think yeah making a short sweet videos is better um than making one really long one because yeah it kind of consumes you I feel like with a lot more information especially if you if it's so new to you yeah that's true that's true all right well we're gonna live on this good note thank you guys for joining uh I feel like it was amazing if you're probably one of the best videos that we have had on the channel so far because they will get people get the most information about actual interview products it's not about stories and motivation should you go if you do not How does it go how does it work does it work out for everyone or not when you take the course but how do you actually pass an interview what would be the best answers to give and what kind of questions can you hear mm-hmm definitely already and I shall see you next time if people like that alrighty gentlemen good luck guys awesome guys once again it was the most amazing and helpful video that I have recorded so far I can see that you've learned a lot please don't forget to leave a comment below and tell me what did you enjoy the most and what would you like to see the most because I feel like we gave you too many details over different things but we could possibly concentrate on API topic only or automation topic only or manual only this is most likely what we're gonna record next but I want to hear your thoughts and once again big fat thumbs up subscribe to our Channel below and join our Instagram and telegram communities in the description underneath of this video thanks again you have a good one foreign [Music]