Can I Sign Oklahoma Banking Word

Can i industry sign banking oklahoma word free

hey guys so let me get started by telling you a little bit about me I've been in web development for a little bit over 15 years I ran a design development agency building on the lamp stack for about 10 years right now I'm a software engineer with B stock and I've been there for about three and a half years and I'm on a team of about 25 engineers we primarily use the land lamp stack they're my specialty is probably the front end although recently I've been building a back-end microservice with nodejs I am a self-taught programmer when I'm not coding stuff I like to do photography travel creative writing hiking dancing philosophy metaphysics astronomy astrophysics long walks on the beach so the agenda for today I'll talk about the interview process in the tech space and I'll give you guys some general interview tips I'll talk a little bit about some red flags that I see when I'm interviewing and we'll talk a little bit about soft skills and what we're looking for as a tech company at my company I have a little section for free code campers and self-taught programmers I thought that would be relevant for you guys I'll talk a little bit about my interview process and that includes both the phone screen and the on-site interview so the interview process in the tech space what does this look like usually at my company and this is pretty much across the board you will have a phone screen with maybe a technical recruiter usually a phone screen lasts about an hour after that with my company you will have a second phone screen with an engineer now this is not all companies but it's possible that you will have a phone screen with an engineer once you pass those two phone screens you'll be invited into an on-site interview and this is a full-day interview the way that we do it at my company and this is going to vary from company to company is we you will have an interview with two engineers at a time usually they're senior members of the team you'll have after those interviews are over you have an interview with the director and then you will have an interview with our VP or CTO so some general interview tips these may be not specific to the tech industry but these are things that I wanted to mention today first of all understand the role that you're applying for before you get on that phone screen or walk into the on-site interview really understand the job description and what the company is looking for before you walk in do some research on the company you know get on Google and look up the company website read about what they do what they're about what their philosophy is it's good to have this understanding of who you're interviewing with before you actually speak to somebody at the company dress well so there are varying opinions on this topic in Silicon Valley which my company is based in it's not uncommon for people to walk into an interview in t-shirt and jeans personally I would like to see someone well dressed when they walk into an interview that means throw on a suit maybe put on a tie put on your shoes women closed-toe shoes it may not hurt you if you dress down for your interview but it's definitely not gonna hurt you if you dress up what it tells me when you walk in well-dressed is that you care about this position this interview that you have respect for the company that it's very important to you so you're trying to put your best foot forward eat before and not during your interview so we we usually we have breaks in between the on-site interviews and we will let people you know use the restroom and get a drink grab some snacks or something so one day I had an interview and this girl took us up on the offer to get something to eat in between the interviews and she spotted a box of cherry tomatoes in our fridge which is fine but throughout the entire hour of our interview girlfriend was popping these cherry tomatoes and I couldn't concentrate because I kept thinking what if she squirts at me you know like it was like really awkward so if you're gonna get something to eat at your interview do it you know get something light get a granola bar eat some something small try and eat well before your interview I know this is silly but it really is relevant and ask thoughtful questions so if you google you know everybody knows you should ask questions at an interview right when they say do you have any questions for me you should ask something but if you look it up on Google you'll see the same questions over and over when I'm interviewing engineers I'm hearing that very same question you know 10 15 20 times that tells me that you googled it that doesn't tell me that you actually have a question for me about me or about my company or about the role so try and find something relevant you know an actual question that you have to ask about the company or the team or the job that you'll be doing be prepared to demonstrate on just get understanding of skills listed in your resume sometimes I will see people come in and they list themselves as a senior engineer but then they have no idea what they're doing it's fine to be a junior it's fine to be entry-level but come in with that presentation of yourself this is who I am and this is where I'm at that's fine practice coding challenges and study algorithms it's 99 percent guarantee that you will be asked to do a coding challenge or solve an algorithm algorithmic problem at an interview so study these ahead of time there's nothing that you can do on the spot if you're not familiar with a coding challenge so it's really important to spend some time before you start interviewing just kind of looking at the more popular ones solving them on your own practicing them and after the interview think the interview is for the time send a follow-up thank you email that afternoon of the next day this is kind of old school we used to be taught this at school when I was back in the dinosaur ages when I was in school but I think that those people who take the time to thank me for breaking up my day to meet with them for this interview or that send a note through email you know later that day saying you know thanks for your time I appreciate you taking time I take it makes me feel like they recognize that the interview process for me actually took some time out of my day because you know when you got your head in code but you have to stop for an interview it's kind of distracting so I just appreciate when somebody reaches out like that and again it may not help you but it's definitely not going to hurt you next up some red flags and these are things that I have seen first up is please don't be asked me if I ask you a question and you don't know the answer to it don't try and sound like you do just tell me you know what I'm not really sure if I was faced with this in a real life situation this is what I would do to find the answer perfect that is a perfect answer for that question I don't expect anyone walking into an interview to know every answer to every question I have but I do expect you to be able to find the answer no one admit what you don't know explain what you do to find the answer second please at least attempt to answer my question even if you don't know the answer so this shows me that you're trying to work through the problem in your head right you you maybe you don't know the answer and again that's fine but don't say oh you know that's not really showing me that you're trying so try to answer the question please don't be arrogant and condescending this one is a little bit tricky because when you walk into an interview you want to be confident right you want to look like you're confident in what you know at the same time you don't want to send a message that I know more than you you know I had an interview once with someone who was a senior JavaScript person and I introduced myself at the beginning of our interview so people know what my proficiency is and I did mention JavaScript he proceeded to explain to me what strings and variables were that didn't make me feel like you know really warm and fuzzy so try to communicate what you know know who you're interviewing with know what their proficiency is so that you're not kind of talking down to them soft skills so we all hear about soft skills so what are they soft skills thanks to Google personal attributes that enable someone to interact effectively and harmoniously with other people so these are the kinds of things that cover soft skills what qualities are important for your job or your team to have these are asking you about your personality what you're looking for what are your strengths and weaknesses this is something that you should think about before you walk into an interview and be prepared behavioral questions tell me about a time when I might ask you tell me about a time when you were working with someone and you had a really difficult time working together how did you resolve that situation so one of the the methodologies that you can use to answer this question is called a star methodology and it's just an acraman acronym to help you remember the steps right first you describe the situation that you were in you talk about the task that you were given the action that you actually took and the results of that action so this will help you to like really be thorough in answering these questions about tell me about a time one okay next up what we're looking for as a tech company so when we're interviewing we're looking for do you have proficiency in whatever language it is to the level of the position that you're looking for right this is a no-brainer this is pretty much basic stuff are you a good culture fit and I know that this is really important that my company a lot of the engineers that I've talked to it other companies here in Oklahoma are very much the same this is a big deal for a lot of tech companies or tech teams now this isn't something you can prepare for it's not something you can study for you either are or aren't going to be a good tech good culture fit with the team but know that it is something that's really important and it should be really important to you too we want to know can you explain your thought process so working on a team of engineers you're going to work with people a lot you're gonna have to communicate a lot whether that's verbal right explaining what you're thinking of doing explaining what you're working on or maybe through the form of comments when you comment your code which I hope everyone does you want to be able to communicate what your thought process was while you were writing that code so as we're interviewing we're looking to see are you able to communicate your thoughts are you a good culture fit put this in a second time because this is really important to our company and I really wanted to emphasize this do you seem willing to learn from and share knowledge with internal and external partners so when you work on a tech team chances are you're not going to be working alone you're going to be working with other engineers but you're also going to be working with other teams right you're gonna be working with maybe marketing maybe the UX team maybe you're gonna be working with product so are you able to talk to other people about what it is you're doing can you share your knowledge with them are you a good culture fit surprised will you be able to work well in a cross-functional team again because you'll be working with other team members in other departments we want to know that you'll be able to communicate with people who aren't necessarily tech oriented may not know the lingo that you can still explain yourself and be able to work with them are you a good culture fit so I'm really emphasizing the culture fit because this is something that's really important to us and to a lot of companies so this is my section for free code campers and self-taught programmers how many of you do not have a CS degree okay that's most of you actually alright so I grabbed this from Stack Overflow this is a 2019 survey and if you see at the bottom worldwide about 3/4 of professional developer respondents have the equivalent of a bachelor's degree or higher consistent with what we found in previous use however it is not that rare to find accomplished professional developers who have not completed a degree so guys we fall up here hell yeah this is something to be proud of and that said I wanted to talk for a minute about imposter syndrome imposter syndrome is real whether you're self-taught or not this is a screenshot from a slack conversation that I had with one of my seniors last week Laith I think I'm just gonna take a basket-weaving what I think I asked dumb questions in the note channel it hits everyone you are never gonna know everything about the technology that you're in you will always be learning and there will always be someone that knows less than you do so actually I find impostor syndrome to be a good thing it means that we're not comfortable at our level of knowledge right it makes us it kind of drives us to keep learning it makes us feel like there's more for me to know I kind of know more so look at it as a positive thing on the other hand you may be judged from being self-taught when you're in an interview somebody may look at you and they say oh this guy doesn't have a degree from MIT Stanford in that case nothing you can do about it right that's kind of a dumb thing and not a you thing okay there's nothing you can do about that don't even worry about it you probably don't want to work at a company like that anyway so I wanted to also mention confidence and humility so this is a topic when you walk it into an interview you want to have both confidence and humility in the West we kind of look at confidence as more is better the more confidence you have the better you are right but and this is personal opinion people may have argument with me on this confidence does not equal proficiency what confidence does equal is I am competent enough to teach whatever it is that I know humility on the other hand does not equal inadequacy humility means I am still a student so while confidence says I know stuff humility says can you help me learn this stuff I don't know courage says I know stuff and I will show you there's also this other stuff I could know better might you help me learn so there's kind of a marriage of confidence and humility so when you walk into this interview I'd like you to walk in with courage I think that courage is a better word to summarize both of these aspects than confidence or humility and that is my Yoda slide for the presentation does anybody know who this is Susan Boyle who said it what did Susan Boyle do she's saying so so let me give you a little for those that don't know who Susan Boyle is you can see she's kind of frumpy she kind of looks a little dumpy right she was this British woman who was on Britain's Got Talent it was maybe ten years ago or so she walked out kind of stout you know she was a little awkward looking she introduced herself and she and they asked her the judges asked you know what are you doing here today and she says I want to sing and people kind of laughed at her you know she was all awkward and weird never liked whatever and they said like who do you want to sing like and she mentioned I don't know some famous singer I don't you know then I don't know who that was but it was some famous singer and everybody just bust out laughing at this woman because they're like really well let me tell you what girlfriend opened her mouth and started singing and I have chills right now remembering the sound of her voice okay she was so impressive she had such a beautiful voice coming out of this really awkward woman so so how does this what does it houses relevant to you guys I'm telling you channel Susan Boyle when you walk into your interview you were walking in without a degree from Stanford or MIT you're self-taught programmers Channel Susan Boyle CS degrees set a level of expectation I know when somebody walks in with a degree what they have a proficiency in I know what their level of expectation was to be able to graduate but if you're self-taught tell me that and then wow me because you can write my level of expectation of somebody who's self-taught is probably not going to be as high somebody who's got a CS degree so you have this opportunity to be like alright you know judge me but now look this is who I am so this is my interview process the phone screen and I don't spend too much time on this because this is pretty brief it's about an hour what I usually do is I'll introduce myself I'll talk about my current role in my areas of proficiency again I do this so that you know who are you talking to and how you know what what vocabulary you can use with me right if you're say a Python engineer and you're talking to somebody who's front-end they may not be as familiar with the syntax of Python so you know it kind of gives you an idea of who it is you're talking to if you interview on the person doesn't tell you who they are what their role is ask them just ask because this this is going to be relevant for how you're speaking about what it is that you do then I will move to tell me about yourself tell me about your current position tell me about your programming languages of choice after we get through this conversational part of the phone screen then I move on to technical questions in an online coding challenge technical questions I actually brought with me today and if we have time at the end I will throw out a couple of the questions that I usually ask just so you get an idea of some of the different things that you might be asked on an interview so the on-site interview if you pass the phone screens and then you get to the on-site stage this is usually what it will look like now this is how I do it but it's pretty common throughout the industry it's pretty much standard I'll introduce myself again if the interviewer doesn't introduce themselves ask them about their role in the company so that you understand who they are introduce yourself this is commonly where the interviewers will start right who are you what are you doing now what is your current role as a developer I'll get back to this in a minute how many of you are currently not developers alright I got some stuff for you guys I will talk about I'll ask about your soft skills tell me about a time one right I want to know what you're doing to improve your skill set you guys are free code campers you've already got something for that right I want to know why you're here interviewing this is a common question that you might be asked so what is it about the company that you liked what appealed to you about the position why are you here then the whiteboarding encoding challenge right this is something that I'll also talk about later and then it usually ends with questions for me questions for the interviewer so Who I am this is pretty much the spiel I gave you guys at the beginning of this talk you know I'll talk about my experience my previous experience what I'm doing at my company then when I talk about who are you and I asked tell me about your current position as a developer okay so there are two paths we can go here right I'm currently a developer some of you guys are or I'm currently not a developer so I'm gonna talk about both of those and how to handle that question so first I'll go with the easy path right tell me about your current position as a developer when when I asked this question of trying to gauge several things I want to know you what your level of knowledge is and your personality are you a culture fit right is your role at your current position reflective of what you've told me in your resume does your skill level meet the requirements of the positions we're looking for hiring for them do you work well within your current team structure and is it comparable or different to ours maybe you work in a small team environment you're in a team of five and our team that's twenty five plus you know what is your situation how do you feel about working in a bigger team how well can you explain what it is you do again communication are you going to be able to explain your code are you going to be able to explain your thought process so tell me about your current position as a developer now this is the other path which most of you fall into I'm self-taught and I have no work experience as a developer yet okay so Alex thank you for this I on slack said I think transitioning can sometimes scene with suspicions with which I think comes from unfounded bias people change their minds they find new interests it doesn't mean they're flaky or have short attention spans I could not agree with this more and that is because I'm self-taught and I come from a very different background so if someone said to me you know I'm not working as a developer right now my next question would be cool so why did you decide decide to switch to a career in tech if you're not asked this question volunteer the answer anyway work it in okay this is important things you don't want to say I want to make lots of money you know my job pretty much sucked that seems like the place to be right now oh okay these are things you don't want to say so what are the things that you do want to say I have a serious passion for technology I've always enjoyed coding I started coding as a hobby and I got super excited about it I love problem-solving I'm looking for someone who's with fire fire is what's gonna sell you your knowledge and your fire remember Susan Boyle so when I when I ask or if you're not asked this is something else that you want to work into your interview how do you think your previous experience can make you a better coder so you're thinking you're experienced you know might not be relevant but when you're asked about your current role if this is not a follow up question take the opportunity to explain how your experience will benefit you and the team if you join okay so I'm gonna use my own personal example for this um just to give you an idea of how I would work it into an interview so first out of high school I worked in the wire transfer Department for an International Bank seems so irrelevant right but that industry was very time sensitive and it was a high risk high pressure environment this is something that's gonna be beneficial when I'm a developer on your team I was also an assistant manager of Kinkos which is now fedex kinko's i guess and that taught me how to work with difficult clients right it helped me to develop empathy in order to understand our users so you're just really spinning it you're spinning what'd you do to make it relevant to what you're trying to do and then I taught high school social studies so how is this relevant to engineering right so it prepared me for working with juniors as a senior or a team lead right it gave me the tools that I needed to learn how to work with people who needed to learn stuff so find a way to and you need to think about this before your interview if you're not a developer now you want to think about what what it is that you're doing now that will bring value to your new position all right guys whiteboarding so whiteboarding petrifies me petrifies me and i'm not sure that there's anyone in this room that it doesn't intimidate just a little bit right the idea of getting up in front of your colleagues your peers or people that you hope to be your colleagues and solving a coding challenge so the I just want to make a brief statement about I refuse to whiteboard I have heard this I hear it I've heard it over the years there are people who will say I refuse to whiteboard I'm not doing an interview where they asked me to whiteboard just not doing it when you start out don't do this don't refuse the whiteboard because if a company wants to see you code and you want that job you need to whiteboard if you're in the industry 10 15 20 years and you want to refuse to whiteboard by all means go for it but in the beginning be prepared to whiteboard and when you do get into that whiteboard part of the interview know that the interviewer probably wants you to succeed when I'm watching somebody into whiteboard I'm usually sitting there like cheering for them in my head come on you know how to do that you know I see what they're writing and I'm hearing their thought process and I'm cheering for them in my head so don't walk in feeling like they're setting you up they want to see you struggle they want to see you fail most of the time they do want you to succeed follow the interviewers lead if you start coding something and they kind of diverge you and want you to go in a different direction don't be hell-bent on continuing what you were doing let them tell you the direction in which they want you to go and follow their lead maybe they want you to write something in a different way follow their lead as best you can show what you know don't code to impress so if you are interviewing for a say a JavaScript position and you are not familiar with fat arrow function functions now is not the time to start using them code what you know code the way you're comfortable it's not the time for you to try to be like you know the showstopper or the superstar just get it done this is like brute force time okay and I'm freezing up and oh my god I know how to do this so these are two kind of opposite ends of the spectrum here and I'll help you out with this in a sec this is how you would should deal with either I don't know what to do or yeah yeah I got this you want to use the reactive method and I grabbed this from full-stack Academy this is again another acronym to help you remember the steps while you're white boarding so I would suggest before you even start this process you just take a minute take a deep breath because you're like you feel like you're on stage right now and this is the moment of truth right now is when you have to perform so it's kind of intimidating take a moment take a breath take some notes write it down on paper write it in your IDE write it on the whiteboard wherever you have to just make some mental notes for yourself as you think through the problem okay just in case you feel like even if you know what you're gonna do you might freeze up halfway there and you're like oh my god I can't remember where I was going with this so kind of hash it out right away so the reactive method is the first thing you want to do once you're given the challenge is repeat the question ask for clarification if you don't get what they're asking you ask make sure that you understand what it is that they want you to do then give some examples these are the types of inputs that the program will take and this is what they expected outputs will be at the end when the program runs then talk about possible approaches so I could to it in this way or I could do it in this way you know this is what I'm thinking talk about it then sorry you then yeah so then you're gonna write your actual code okay sometimes pseudocode is okay I've had people ask you know do you want me to pseudocode this or do you want me to actually write the code depending on how complex the challenge is you may not have room on a whiteboard to write the whole program so just ask you know the important part of whiteboarding is that you know how to think through the process and you're gonna get it done it's not necessarily that you have to syntax down or that you have beautiful form it's more about getting the problem solved and getting the program functioning after that you want to run through some tests so in TDD style think of some tests that you would run your program through talk about it right you're not gonna actually write the test but you're gonna talk about it this is the input that I'm you know expecting here and then the program is doing this and by the end this is the the output that I expected or maybe you run through your program and you realize that you don't get the expected output fine just say that oh I just realized this isn't gonna work this is what I have to do to change it so it just at the whiteboarding part of the interview they just want to see your process right they just want to see you write code figure out problems as you run into them and see how you're gonna solve them because nobody writes a program perfectly the first time believe you me have yet to do it if you have time at the end of the whiteboarding challenge you might want to do some optimization you want to make it dry dry for anyone that doesn't know don't repeat yourself and at this point you might try and do something to improve the time space complexity normally when we give whiteboarding challenges we don't get to this point we usually run out of time before the person has time to do this again follow the interviewers lead sometimes they don't want you to spend time on this sometimes they do so just talk it talk it through so an example of a whiteboarding challenge you might be given and there's been a lot of chat about this on slack lately fizzbuzz is a very common coding challenge and what phys bus is is write a program that prints the numbers from 1 to 100 for multiples of 3 print fizz instead of the number for multiples of 5 print buzz for numbers which are multiples of both 3 and 5 print fizzbuzz and I added there's a book that you might want to check out cracking the coding interview is a great book with coding challenges if you want to practice so let's say this is you and you're in your coding challenge and this and you're given fizzbuzz so hmm fizzbuzz okay I know I could solve this by writing a for loop but I could also write a function that takes arguments so that it's more flexible so you're thinking this to yourself right so this is your interviewer while you're thinking okay what I'm gonna suggest is you be this guy you say it out loud so this is what I'm thinking I could write this by writing a for loop but I could write a function takes arguments that way it's more flexible do you have a preference whoo this is me I'm excited because not only did you talk it out you asked me if I had a preference which way you went of course I should also add if you don't know how to do both don't offer it so questions for the interviewer so after you've gotten through your whiteboarding section of the interview this is pretty much near the end questions for me and some examples of those are can you tell me about the dev team structure and process this tells me that you're interested in our team you want to know if we're gonna be a culture fit for you so not only is it important for me to know you're gonna be a culture fit with us it's nice to know that you care if our team is going to be a good fit for you so this is a great question to ask what would a typical day look like for me in this role right you want to know what your day-to-day operations is going to look like can you tell me about your team culture again going back to the culture question what do you like most about working here people love to talk about themselves just ask me when you ask somebody what they love about their job you know it kind of it does give you insight into what the company is like what their day-to-day is like and you may learn something about the company that makes you go oh I don't really want to work there or it might be something that gets you excited about becoming part of the team so it's kind of like when you move into a new neighborhood and you ask the neighbors hey what do you like about this neighborhood you know it gives you some insight into what's going on there what kinds of challenges rates are your team facing right now everybody likes to talk about their challenges oh this this would probably give you insight into some of the things that you'll be working on and it'll give you insight into what the struggles are of the team what they're working on right now you know what what obstacles they're running up against are there opportunities for professional development I love this question I love to hear this question because that tells me you want to go to conferences you want to learn stuff you got the fire right that tells me that you're interested and you want to continue to develop yourself that you're not like yeah I know how to code some stuff I'm done right I want to know that you're interested in growing what are your expectations around my accomplishments in the first X months in this role I like this question too because it tells me that you're thinking about what are the kinds of things that you see me wor ing on where should I be in a few months from now and it tells me that you it's important to you what your team members are thinking and what their expectations are of you this is also a great question to ask anybody who's in a more senior role like your director or the CTO if you interview with them so recap that was quick so we talked about doing research research the company that you're interviewing with be conscientious with your address with your thanks for people's time with your meaning meaningful questions be ready to demonstrate your skills practice common coding challenges and algorithms know what you know know what you don't and know your resources this is a big one self-taught versus formal education so bring the fire right channel oil relate your previous experience with the dev role this is something you got to think about beforehand so prepare this behavioral questions are going to use the star method whiteboarding you're going to use the reactive method and wrapping up the interview ask thoughtful questions that show your interest and desire to grow and all throughout be courageous right my Yoda slide be create courageous so that's all I've got I am happy to take any Q&A we have some time left I do also have some sample interview questions that I can share if there's time testing oscar's before you got this role did you have a person like interviews with other companies and have there you go and part of reason I'm asking visit I had a personal interview this is five years ago where it was very small syrup so what stood 20 people and it were true business casual so not a jacket but all that and I got this interview in a different matter I just met somebody people so I didn't go through the initial on scooting and because I knew them a little more personally they actually did say they they were kind of questioning my dresses too much you were too dressed yeah I have heard that before I think this goes back to know the company that you're interviewing for in in smaller startups and when I started with B stock I actually started with them as a contractor about ten years ago and when I started with them they were very small the team was about 10 people I think the engineering team was me and two Russian guys so yeah if I had shown up to an interview with them in a suit it might have looked a little weird especially because it was Silicon Valley I think that in Oklahoma it's a lot more conservative than Silicon Valley so I would tend to be more dressed here than there but again it goes really goes back to the company that you're applying for trying to get a sense of what their culture is and what their values are and again I think if you're overdressed I think that that's going to hurt you less than if you're underdressed you know what I mean erring on the side of caution I think it's better to be a little bit overdressed than underdressed great question anyone else yeah you can just ask it I'll repeat it yeah I had a question on the part on the coding challenge whiteboard especially or even uncle hmm okay yeah so the question was if you're interviewing and you get a coding challenge that is not really relevant to the job that you're applying for and what's my position on that I think that there are some companies where you'll walk in and you will get a coding challenge that is an extremely difficult algorithm something where they're looking for people to show their what's the word I'm looking for prowess but more than prowess it's it's a little bit more of a I don't really have a PG way of explaining what I want to say it's sorry quits BA not so much foot spa but more like you're bragging about you know or you look how good I am you know they kind of put you in a position to maybe it's sort of condescending right I I personally feel that coding challenges like that are not appropriate there are companies that do it though and I guess that's the point at which you should decide if the I mean obviously you're gonna try to do the whiteboarding challenge right whatever the question is you're gonna try to work through it but the sense around that question if it's not relevant to the position you're applying for and you feel like they're just kind of trying to make you dance that's an uncomfortable situation right they're not actually testing you on what you know for the job you're going for the testing you want how well you can dance and that kind of I don't like that so I guess to answer your question you do want to do the challenge but I think it tells you a little bit about the company culture if you're getting a challenge that's not relevant to what you're applying for is that kind of answer question that's a great question so the question was when I'm interviewing someone how do I not someone is a culture fit is there something that I look at as a measurement so I guess personally for me because I've been with the company for so long I do I am really intimately familiar with the culture of my team but beyond that we do have company values and philosophy so and this is also why I suggest you do some research on the company that you're applying for because if it's been outlined in a company philosophy chances are that's the culture you're trying to fit into so that is something less subjective that I can use to kind of gauge whether or not someone is a culture fit that's a great question not not that I'm suggesting that you pretend to be someone you're not obviously where you going into into an interview but you know before you even get to the interview maybe you read the company values and you're like dude this place is not for me you know I mean the research part before you get to your interview is going to be invaluable to knowing whether or not you want to work there it's not just about oh can I get this job it's about do I want this job then can I get this job a great question anyone else okay so what I can do now if if you guys are interested is I can run through some of the questions that I'm asking let's see how can i how many of you guys our front end okay whose back end and JavaScript PHP alright well some questions so these are some of the questions that I'm asking they may or may not be relevant to you what I try to do is I will try and engage what role it is that you're applying for and even if you're applying for a role that I'm not necessarily proficient in I will be on the interview because again I you know programming in general I actually got some general programming questions that I can ask you programming in general is it's language agnostic right it doesn't matter what language you write there are some basic concepts that you should know so let's see I've got some junior dev we don't want to ask those so general programming so here's one of my class now if you guys interview with me I'm gonna have to change my question so why would you use triple equals instead of double equals so you want to want to try and answer that or should I just run through these yeah go for it okay you want to make sure that the values are exactly the same so you would use the triple equals right let's see then I will ask questions like have you worked with vagrant or docker and in what ways have you worked with them what did you like and dislike about them so this is more of a conversational question if you haven't worked with them okay if you have you know white why do you use it why did you use it what did you like about it just to kind of gauge your experience with it what can you tell me about object-oriented programming what is it all right I don't wanna put you guys on the spot I would say explain the concept of loose coupling in programming y'all got some homework to do okay so what are the main features of object-oriented programming clearly I'm using object-oriented I write a lot of PHP and we do use object-oriented programming our main product is built on a monolith which is an MVC structure and it is using olp so a lot of my questions are relating to object-oriented programming let's see what else I will ask so I do have some questions about MVC okay here's some more generic questions what is the difference between QA and software testing right so with this question I'm kind of looking for somebody to explain to me that QA is something that somebody else probably does and software testing is something that I as a developer probably do then I'll ask why did you choose PHP as your primary program programming language or whatever it is Python node whatever okay why why do you like it what do you not like about it what is continuous integration alright have you worked with it why is it important I've got some JavaScript questions PHP questions so again this is mine this is like my master list of questions and I will ask them depending on what your experience is and what the role is that you're applying for right so I'm not gonna ask you all these questions if you're like a Python guy I'm not gonna ask a question about WordPress right but if you're coming in as a WordPress guy I'm gonna ask you WordPress questions what is the sequel injection right I would hope that everybody kind of has some understanding of what a sequel injection is whether your front-end or back-end whatever database you're using it's kind of a very general question right and even if you can sort of answer it and you don't sound like you have a lot of proficiency with sequel that's fine one of the questions that I like to ask mostly to back-end people or do you prefer to work with relational or no sequel databases and why this is really telling of someone's familiarity of the different types of database structures and so I like to get people's opinions on these I will give if someone is proficient in applying for PHP slash sequel I'll give some examples here's a select statement tell me what's wrong with it tell me why this why this code is vulnerable how you would fix it right what's the difference between unit testing and integration testing this is one of my recent favorites because I had been integration testing and not unit testing so I have to take a little lesson on that myself have you done regression testing and can you tell me what it is what so if you're more senior than I start to ask a little bit more senior questions like what are the first things you do when reviewing someone else's code what do you do - or what tools do you use to test code quality and I'll ask you some of my or I'll I'll share with you some of my less or these are my what I call culture fit slash soft skills questions sometimes because I know people are nervous I like to start out with tabs or spaces everybody's got an opinion I just you know I just want to lighten it up if this is not a real like I'm not gonna not hire you if you're using spaces I still love you you've just been put in charge of a legacy code project with maintainability problems what kinds of things would you look to improve to get the project on a stable footing so this is relevant to our product how would you describe nodejs to a child whatever your language is I'll ask you explain that to a child what is something substantive that you've done to improve as a developer in your career I go to free code camp meetups what kind of projects or work do you really dislike and why what is your perfect job I think this is a common question this this is one of my favorites describe the color green to someone who is blind see the reason yeah confusion right why is she asking this question what does this have to do with web development I want to know how well you can think I want to ask you and it just out of the park question and just give you the opportunity you have not prepared for that question right there is no way you've guessed that I'm gonna ask you that question and I want to gauge your personality I want to see how well you can think on your feet because you will be given problems in real life that are like this explain the color green right yeah sorry alright sound frequency to explain the color green awesome yeah I love that sweet yeah so I am looking for creative thinking and in with this question what if this is a question that you'll probably maybe hear what is the one what is one thing you like most about your current manager and what is one thing you'd like to change and that could be what is one thing you like about your current job what do you would like to change something about your you can't answer that question there's someone here that works for me so we don't want her to if you woke up and you had 2000 unread emails and could only answer 300 of them how would you choose which ones to answer these are all subjective questions right there's no right or wrong but I'm looking to see how you think let's see teach me something I don't know in the next five minutes now I actually grabbed that one off Google because I thought that was a pretty cool question just just anything you know any random thing so interviews with me maybe are not as stiff formal I like to inject some informality and so there are different styles of interviewers right you you're gonna interview probably with somebody who is very cordial and formal and that you may not get cool questions like these but I like to put people yeah I'm I'm not saying I'm cool I'm just I guess I guess what I'm saying is that because it's important to me to get gauge your personality I do inject these kinds of questions and I also like to make people feel comfortable because I know everybody's nervous at an interview this is another favorite of mine that you'll never get asked on an interview but I'm gonna share it anyway cuz I love it a lot if I had an airplane full of jelly beans and I wanted to get them all out but in a very sanitary way so I could still eat them what would you do you have 24 hours to do this but you have unlimited funds so I guess these are more like brain teasers right and and their ways of yeah and I've gotten some really interesting answers to that one that's really fun I also ask questions about leading leading others because I'm trying to gauge whether even if you're not in a position right now like you don't have enough proficiency right now to be a team lead or a senior I want to know you know what your potential is so you've been given two projects they both have to get done both super high priority how do you deal with that let's say oh and I do have some actual have some whiteboarding challenges but I don't really have a way to show you so I'm gonna skip that yeah so I don't want to give you away all my secrets just in case one of you guys end up interviewing with me but there's some of them and if there are no other questions I guess that'll do it for me oh I should mention I put up my contact info um feel free to reach out I'm on tech aloneness lack as mere legion and there is a space in there that's weird but there's a space my gmail my website which is kind of Cody kind of personal sort of weird and my LinkedIn so feel free to reach out any questions or anything I can do to help hopefully some of this has helped you guys out today thank you