During the final year of college we have many job fairs (also called as campus placements) that take place throughout the year. During this many different companies come to our college. I don't want to apply for a job until I find out what kind of work I would be doing.

What can I do to find out which of these companies are hiring and also, what sort of job positions they are hiring for?


4 Answers 4


From my experience - even when you are a fairly seasoned professional, it can be pretty hard to figure out if you will like the job you are interviewing for. Probably because, at any point in your career, you're looking to make a change and make some aspect of your job new, different and hopefully better. Any job is such a complex mix of people, organizational culture, rules, technology and business domain mechanics, that it's nearly impossible to get a full picture.

Thinking back to my college days... I'd recommend the following... this is somewhat US biased, as that's my career base, but I have trouble seeing these tricks failing in any technical field.

Use your school's job hunting mechanisms extensively

Organizations that have taken the time, money and energy to recruit at your school, post on job boards and otherwise be on your campus have a vested interest in hiring you. Most companies don't go to this effort if they haven't had a good experience with graduates from your school. It's quite likely that they have experience with graduates from your program of study and they already like what they see.

Which means your chances of being getting a job and being happy at it increase greatly.

It also means they have people on their staff who have some experience trying to answer college grad questions in helpful ways. I scoff at companies who don't send a technical person somewhat related to recruiting areas to the job fairs or interview sessions on campus as there should be someone there who actively manages college grads who can speak to the entry level onboarding process and general career options from a hands on perspective.

Job fairs are a great way to have light weight contact that goes beyond a company's website, where you can clarify the kinds of things you might do starting off. Many companies I've recruited for (as a technical hiring manager) will not commit to a certain position's availablity - our needs are too vast, and the projects are too ever-changing for us to be ready to commit without interviewing. But I am well versed in what most teams are like, the current range of likely projects, and what it'll be like to work for us, regardless of the specific project. You're not likely to get this sort of information from a corporate website, as this is ever changing, complex, hard to communicate stuff that doesn't lend itself well to static content.

Browsing a job fair lets you get a baseline. Searching websites may help you refine that baseline...

The wider world

The range of companies is pretty much infinite. For the most part, a good bet is to have a sense of a few basic company qualities that may fit your basic desires:

  • Big vs. Small - most big companies have well structured employee intake processes, offer a fairly well-defined job and can give you exposure to more mentoring. Small companies, OTOH, can give you a more broad experience as you do more diverse work when there are fewer people there to do the work... they can also be more chaotic, and less stable with less clear expectations.

  • Business domain - different areas of the economy tend to have different corporate cultures. In essence, it's a likely conjecture that government defense contractors in any country are more like govt. defense contractors anywhere in the world than they are like small venture capital funded startups anywhere in the world. For the most part, companies compete with each other in a business area, as they often want the same type of people - and it's not necessarily just your degree, it's also your personal style and how you work within a team.

  • Interal Vs. External - for the most part, there are different demands between roles that face a company's customers vs. roles that come in contact with people only within the company. This can be a lot of different jobs - for example a software developer may develop code for an internal company app used only by the accounting department, or he may be a consultant developing code for a customer who pays the company money. Same job, but vastly different experiences, support structures, and expecatations.

  • Particular work/life benefits - different businesses but also different corporations will have different benefits in this area. I don't mean the easy to compare paper benefits - like health care, insurance, time off, etc. I mean the quality of life benefits - like private offices vs. cubicles, capability to work from home, investment in tools and technology, the definition of "appropriate personal use" of this equipment, etc. You'll see over time that these offering center around a business domain to some extent, but can still vary markedly. Knowing and thinking seriously about what will work for you is important, and to get this information, you'll likely have to go on an interview.

The name of the game

IMO, the name of the game is to maximize the useful job offers while minimizing the time you spend acquiring them. That means figuring out a collection of places to apply, and then scneduling interview options based on what you feel are the most likely good fits for you. A trick is to balance the hours you spend researching companies with hours spent actually talking to people through either job fairs or the interview process so that you can start to gain insights into the areas that sound most interesting to you.

I tend to treat this as a phased process. I research a collection of jobs, I send out a batch of resumes and coverletters, I wait for follow up. As time goes by, I track the follow up to see what was most interesting to me, and what seemed most likely to yeild a good job offer. Then I repeat targeting those areas that seemed to be the likeliest matches and finding competitors or similar businesses to widen my scope again.

  • If you are just starting out and unless you are an intern at a company you should go on every possible interview possible. Once you get a job offer that is when you will decide "did this company give me a good impression" don't make a decision before that job offer Facebook was once small don't forget.
    – Donald
    Jun 20, 2012 at 17:21
  • I agree that you need to go on interviews to learn more - but I'd say regardless of your experience range, you have to find the sweet spot between interviewing, looking for interview opportunities, and getting other things done. Jun 21, 2012 at 20:21
  • At this stage in your career, you need interviewing practice, so while this is great advice, don't filter out companies too soon.
    – HLGEM
    Jun 21, 2012 at 20:24

As a new graduate I suggest you look for a larger company, institution, college or healthcare environment.

This will give you the ability to:

  • Learn from other seasoned professionals
  • Have time to get proficient in the actual tools you code in (if you code).
  • Learn more about the professional software environment and the softer people skills you need.
  • Get up to speed on a code base, a skill that often takes years to mature (again if you code).
  • Start you career in a more relaxed academic-type environment before doing main line consulting.

I would avoid small companies and startups for now as they need you to produce very quickly, but you haven't usually learned how to apply best practices to make a good enough code base.

  • On the other hand, small companies are great for getting exposure to lots of different areas to figure out what you really want to be doing long-term. In larger companies you may specialize too soon because of the team structure (e.g. you're on the database team so you never do UI work but maybe you'd be particularly good at it if you ever tried). Jun 20, 2012 at 14:57
  • @MonicaCellio yes, I am also concerned that I might not get to do one kind of work if I always do some other kind of work
    – nischayn22
    Jun 20, 2012 at 15:25

I would research to see which companies have a technology, ideology or culture that wants to become a part of that company. Never accept work for work unless you do not have a choice. If you are working for a paycheck then you are motivated to work just hard enough to prevent yourself from being fired.

However if you find a company that inspires you to be the best then the next step is to research the company, use social media to find contacts in that company and politely ask them for a few minutes of their time to ask them what inspires them to work for that company.

Also find out what their hiring process is like, is the interview more technical in nature or more culture in nature (most of the time its both). Finally look at the jobs in that company and apply for the ones you qualify for (personally any job that I have 80% of the qualifications I apply for).

  • Doing research on the company before hand should always be done.
    – Donald
    Jun 20, 2012 at 17:21

My experience is that interviewing is like acting - you can read books, but in the end you need to get up on stage and interact with an audience.

I would make a list of companies about which you are 'meh', and apply to those. Get some lower-stress interviews under your belt. After that, you can better handle interviews when you really want the job.

  • 1
    Why did you bump a ten-year old question, especially without any useful insight? Sep 10, 2021 at 3:59
  • @MichaelMcFarlane, the useful insight is to schedule interviews in reverse order of desirability. I learned this by accident in 1998, when I was graduating. I botched the first few interviews, and got much better. What the OP seemed to be doing was to hold off until he/she could get an interview with the companies at which they wanted to work. That would mean that their high-desire interviews would end up being their 'shake-down' interviews. Sep 11, 2021 at 14:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .