Customize this Outstanding Entry Level Restaurant and Food Service Resume Template

Customize this Outstanding Entry Level Restaurant and Food Service Resume TemplateCustomize this Outstanding Entry Level Restaurant and Food Service Resume TemplateCreate ResumeLenny Lawson100 Main Street, Cityplace, CA, 91019 C (555) 322-7337example-emailexample.comSummaryWaitress experienced in taking food orders, operating cash registers and safely handling food while checking for proper temperatures.Energetic administrative assistance Dedicated and focused on,excels at prioritizing, completing multiple tasks simultaneously and following through to achieve project goals. Seeking a role of increased responsibility and authorityHighlightsCash handlingReliable team workerNeat, clean and professional appearanceComfortable standing for long time periodsMath and language skillsDelivers exceptional customer serviceEngaging personalityExcellent multi-taskerReliable and punctualMicrosoft Office proficiencyProfessional and matureStrong problem solverDedicated team playerStrong interpersona l skillsSelf-starterAccomplishmentsRecognized by peers and management for going above and beyond muster job functions.Increased office organization by developing more efficient filing system and customer database protocols.Coordinated all department functions for team of 10 employees.ExperienceWaitress Jan 2011 to May 2013Jerry BsKenedy , TXUp-sold additional menu items, beverages and desserts to increase restaurant profits.Took necessary steps to meet customer needs and effectively resolve food or service issues.Recorded customer orders and repeated them back in a clear, understandable manner.Correctly received orders, processed payments and responded appropriately to guest concerns.administrate assistant Jan 2008 to Jan 2010All tech ac heating companySan Antonio, TXManaged the receptionist area, including greeting visitors and responding to telephone and in-person requests for information.Handled all media and public relations inquiries.Maintained the front desk and reception ar ea in a neat and organized fashion.Served as central point of contact for all outside vendors needing to gain access to the building.Made copies, sent faxes and handled all incoming and outgoing correspondence.EducationGED, Physical therapy 2007 Dilley High SchoolDilley, TX, united states nbspCustomize ResumeMore Customer Service Resume TemplatesExperienced Restaurant and Food Service Resume TemplatesEntry Level Technical Support Resume Templates

4 Common Coding Interview Mistakes (And How to Avoid Them)

4 Common Coding Interview Mistakes (And How to Avoid Them)4 Common Coding Interview Mistakes (And How to Avoid Them) Ah, the dreaded whiteboard coding bewerbungsgesprch . Where youre thrown in front of a whiteboard, stripped of your usual code editor and hotkeys, and asked to solve a complicated data structures and algorithms question on the spot . Yikes. Its enough to make anyone a little nervous - even the most seasoned engineers.Lucky for you, you stumbled onto this deutsche post dhl about the four most common coding interview mistakes Ive seen hundreds of candidates make. Let their mistakes be your unfair advantageleidhing stops a coding interview dead in its tracks like a candidate saying, I dont really know how big O bedrngnisation works. If you have any weaknesses here, this should be priority number one. Make sure youre 100 percent solid on big O notation . Make a habit of thinking about the big O time and space costs of all the code you write. A nd definitely get comfortable with logarithms - they come up more than you might think, and they take too many candidates completely by surprise.Before your next interview, take some time to read up on all the core computer science data structures . Know the strengths and weaknesses of each one. Focus on knowing when you should use each one.Its a very easy mistake to make. Youre chugging away at a problem, and your interviewer interrupts you to point something out. Okay, I see were doing a post-order traversal of the tree. And you have no idea what that means. But your first instinct is to just hope its not important. Or hope you can get away with pretending to know what that means. Or something. So you just say, Right. At first , it looks like youve gotten away with it. But it comes up again later. So, why did you choose to do a post-order traversal? Uh Youre busted. Not only do you not know what the heck post-order means but now you look dishonest . Because saying I dont know what that means at this point means also saying .I, uh, sort of pretended to know what that meant earlier. Best to nip this kind of problem in the bud before you end up in that situation.When your interviewer says something you dont understand, point it out immediately. Lean right in. Because letting them think you understand is only going to make things messy later. Try to be as specific as possible about what you dont understand. It makes your thinking sound much more organized. Huge difference between Huh? and What does post-order mean in this context?I see this all the time. Youre a few minutes into the interview. Youre talking about the problem with your interviewer , batting around some ideas for how to get started. Suddenly you have this sinking feeling that a lot of time has gone by - and the whiteboard is still blank . You decide its time to get moving . Even though you dont know yet what your code is even going to do, you start writing it a nyway.The functions gotta have a name , right? So you write out a function declaration with a name and some arguments. Thats safe - well definitely need that. Maybe a closing brace at the bottom of the board. And theres going to be a loop in here, right? So lets throw a loop in there. I guess itll loop through that first argument? So you kinda sketch out a loop. Maybe you call a subroutine in there that handles some tricky part youre not sure yet how to handle. Ill write out that function later, you say.And then you realize youre sort of back to the drawing board, because you still have to figure out what your code is actually going to do - but now you have all this half-baked code on the board, which might already have bugs, or might already be pointing you in the wrong direction. That instinct to get moving and start writing code actually ended up hurting you. Because now another 10 minutes has passed, youre no closer to an algorithm, and you have messy, half-baked code scra wled all over the whiteboard.Instead, when that instinct kicks in, just pause. Take a moment. Breathe. Know that worrying about time isnt going to make you move faster. Lean into the moment. You could even say out loud , Im starting to feel like I should start writing code soon, but I know its no use to start writing code before I know what its going to do . Just get back to the problem at hand, and keep batting around ideas for how to solve the problem. Play around with a sample input on the whiteboard. Draw a picture of the data structure. Brainstorm. Trust that youre not supposed to know the answer right away thats what makes it a good coding interview problemAfter 45 long minutes, youve finished writing your code. Whew. You just want to turn your brain off and relax. You look at your interviewer expectantly - youre just waiting for them to say, Perfect Its perfect. But they dont. Instead, they say can you find any bugs in your code? You hope its a trick question, but you begrudgingly look back at your code. You step through each line, but youre not really debugging . Youre just sort of explaining the intention of each line. Youre so hoping that your code is right that youre only seeing what you want to see. Youre not seeing the bugs. So, of course, you miss the bugs. And of course, your interviewer sees them.Heres how you actually debug whiteboard code. Write out a sample input. Something short enough that youll be able to get through the whole thing, but long enough that its not an edge case. Then walk through your code line by line. As it changes the input, actually change it on the board . If it makes new variables, write those on the board as well. Thats right - youre using your brain as the computer processor and the whiteboard as your computer memory. Its tedious, but thats the only way to debug code on the whiteboard. Oh, and once youre done, do the same thing with all the common edge cases. Empty arrays, single-elem ent arrays, negative numbers, disconnected graphs, etc.Those are some of the most common coding interview mistakes. If you can avoid them, youll be bounds ahead of most other candidates. Now go run some practice problemsParker Phinney is the CEO of Interview Cake , which makes free guides and online courses on how to pass coding interviews.

Pushing past the pain How to know when youre overdoing it

Pushing past the pain How to know when youre overdoing itPushing past the pain How to know when youre overdoing itWhen Lawson Craddocks bicycle hit a plastic bottle during the first stage of this years Tour de France, the American cyclist hit the ground, finding himself with a laceration above his eye and a scapula fracture in his left shoulder.Craddock, the road and track cyclist whos been racing professionally since 2008, remained in the race after receiving medical clearance telling reporters he welches raised Texas tough. Craddocks ambitious spirit welches celebrated, but after months of training to maintain a resting heart rate of about 38 beats per minute, the cyclist noticed a spike to 50 bpm during the rest of the Tour.In addition to affecting his heart rate, the crash affected Craddocks sleep and overall ability to recover. While he once slept over ten hours, Craddock was struggling to sleep through eight. Facing dramatic recovery deficit and physical pain, the exhaustion o f the sport began to take a significant toll. The few days running into this, I had absolutely awful recovery, Craddocktold reporters. That wasnt necessarily something I was quite worried about yet. I think it was really interesting to see the stress around the Tour de France.Craddock also used this years Tour as a way to raise money for Hurricane Harvey relief efforts in Houston. The racecourse where he got his start in the sport the Alkek Velodrome was heavily affected by the hurricane last year, and Craddock pledged to donate $100 for every stage he completed on the Tour. Most people will do more when theyre asked to do it for someone else, explained team chiropractor and physical therapistMatt Rabin. That definitely has been the case with him.While Craddock fought past the pain to complete the competition for his own sake, and for the sake of so many others, the reality of his health-threatening overtraining could not be ignored. Thats something that people would never know ot herwise, the strain that we put on ourselves day in and day out for 21 days, Craddocksaid.We jump to celebrateathleteswho push past the pain for the sake of the sport, but at what point is the physical andmental stressdefeating rather than invigorating? While Craddock took pride in dusting himself off and getting back in the race, the concern for his lack ofrest and recoverybegs the concern aboutoverdoing it. And although hes not performing as well as he had hoped, Craddocks plans to stay in the race have not wavered. Just still being in the race is really encouraging, Craddock told thepress. Its hard for me to complain, getting to do what I love.This articlefirst appeared on Thrive Global.