First, if you have graduated and you have no job, then getting a job is your job. You should be devoting 8 hours a day to it.
This can include researching companies, polishing your interview skills, networking, filling out applications, polishing your resume or CV, actually interviewing, and, for IT people, getting more experience by spending some time on personal projects that you can show off at an interview. Do not however spend less than 4 hours a day on the actual mechanics of applying for jobs (in other words, don't get seduced by the fun of your personal projects) and looking for new places to apply to. Expect to try several hundred places before success, so don't get discouraged becasue the first ten didn't work out. Don't limit yourself to big international names. Smaller companies often have less competition.
Spend some time practicing common coding tasks that are given in interviews like FIZZ BUZZ (search the Internet for things to practice). Read big thick books on programming in your chosen stack and general programming things like debugging techniques, design pattenrs that are not technology specific. You are prepraing to be able to answer interview questions.
You need to think what you can offer that other entry level people do not. If you don't have anything you see as special, neither will potential employers. So if you didn't do an internship, you need a good solid set of personal projects that are business oriented to point to. An interviewer is going to be more impressed with the guy who built a web site with a database backend than with the guy who just did class exercises. Consider if there is a charity that you could build something for while you look. (But if you do this, you will have to commit to finishing it in your off hours after you start to work. Don't volunteer to help out a charity and then dump them with no product.)
Personal projects should be in an area where you would like to work. If you are looking for business programming, then make sure you do a project that is heavy on database use and reporting and sales. If you want to work in embedded systems, then do an embedded systems project. If you want to work in mobile app dev, then do a mobile app. If you want to work in game programming (and you have a lot of MAth background), then you need sameple games to show. And so forth. Just make sure it is something that will be interesting to the people who will be interviewing you, not just interesting to college students. Use the technologies you want to get hired to use.
After each interview, write down the questions that you can remember that they asked and then go look up the answers. This way your answers will get better over time.