-
NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.
Recently laid off - bored and frustrated
- Thread starter Elodan
- Start date
LightPhoenix
First Post
Elodan said:
I "left" my job (Clinical Lab Tech at a hospital) in June or so, with a severance package as well. Though my case is a little different (I had a choice), and unlike you (it seems) I was really miserable with my job.
Anyway, I can relate to most people thinking I do nothing now. I worked my butt off trying (successfully) to get into graduate school, I've been making contacts and studying for interviews. Even when I'm not doing things that are "productive", I still try to get out every day.
Also, one thing that seems to baffle people is that I didn't go out an get a job right away. Besides the truly awful experience at my old job, I didn't want to get a long-term position and then find out I'd be leaving after six months to go to school. I guess it's a sense of professionalism that seems to be generally lacking among some (not all) people. If I had failed to get into grad school, then I would have looked for a job, but not before.
Anyway, best of luck to you! Job-hunting is a pain in the butt, but you'll come through in the end. Just don't get too down in the meanwhile.
Elodan
Adventurer
I had an interview this past Monday which turned out to be a mini disaster (it felt that way to me). The internal recruiter was supposed to send me the official job description and some additional information before the interview. I had called and left a message reminding her that she was supposed to send me that information. She never did.
Monday morning I put on the suit (with the new shirt and tie my wife bought me. I really hate dressing up; it's not me) and go to the company. I'm supposed to meet with the recruiter and two gentlemen who run parts of the department I could be working in. I meet with the recruiter and ask her about the company culture and benefits. She tells me I'm not supposed to ask about benefits at the first interview, although she tells me this may be the only interview they may do before they hire me. O-kay. She is very nice and seems to be overwhelmed. The company is planning on doubling it's size in the next few years. Based on her description of the culture, I'm getting the feeling that this is not the place for me (I tend to make those types of decisions fairly quickly based on what my gut tells me). The recruiter then goes to get the gentlemen.
Both guys come into the room and I get the tag team interview. Neither one is a database person. They give me a brief run down of the department and then start asking questions to test my DB knowledge. It was pretty funny as some of these questions were exactly the ones I used when interviewing DB candidates at my old job. Then they start throwing out some questions about database administration (not my strong point and not what I want to do). A little aside here, it's very easy to specialize in various aspect of database development and administration. Some people just do design, some do development and some do administration. I want to do design and development. I'm getting the feeling that this job is not what I want to do nor is it what I was told it was by the recruiter.
I then get to ask questions about the job itself. I find out that the job is mostly checking the code that others write and doing database administration (something I told the recruiter I was not interested in doing when she first called). There is already have an architect on staff and it sounds like the people pretty much are stuck in their silos. The company is a little too corporate for my tastes. Also, one of the big draws to this company is that they used SQL Server and Oracle, but they're doing away with Oracle (I want more Oracle experience). By this point the gentlemen are pushing me to ask more questions but I've sort of realized that we're now wasting each others time and really have nothing else to ask. Again, nice people.
On my way home I stop at a local Walmart that's supposed to have Sugar Free Kool-Aid. Can't find any on the shelves. For some reason it's become increasingly difficult to find in eastern MA. Just a little annoyance after the frustration of the interview. I get home and send them a thank you letter emphasizing my strong points. No acknowledgment to date. That afternoon, I pull out my learn VB.NET book and start reading.
Stan and Kyle I learned something today speech:
I took this as a learning experience. I realized that I always want to have a very clear understanding of the position description before I agree to an interview. Another plus is that I had some interview practice.
I'm not one to post much on message boards but I've found posting these things somewhat therapeutic (I can see why bloggers do what they do), so I'll probably update this post when something interesting happens.
Monday morning I put on the suit (with the new shirt and tie my wife bought me. I really hate dressing up; it's not me) and go to the company. I'm supposed to meet with the recruiter and two gentlemen who run parts of the department I could be working in. I meet with the recruiter and ask her about the company culture and benefits. She tells me I'm not supposed to ask about benefits at the first interview, although she tells me this may be the only interview they may do before they hire me. O-kay. She is very nice and seems to be overwhelmed. The company is planning on doubling it's size in the next few years. Based on her description of the culture, I'm getting the feeling that this is not the place for me (I tend to make those types of decisions fairly quickly based on what my gut tells me). The recruiter then goes to get the gentlemen.
Both guys come into the room and I get the tag team interview. Neither one is a database person. They give me a brief run down of the department and then start asking questions to test my DB knowledge. It was pretty funny as some of these questions were exactly the ones I used when interviewing DB candidates at my old job. Then they start throwing out some questions about database administration (not my strong point and not what I want to do). A little aside here, it's very easy to specialize in various aspect of database development and administration. Some people just do design, some do development and some do administration. I want to do design and development. I'm getting the feeling that this job is not what I want to do nor is it what I was told it was by the recruiter.
I then get to ask questions about the job itself. I find out that the job is mostly checking the code that others write and doing database administration (something I told the recruiter I was not interested in doing when she first called). There is already have an architect on staff and it sounds like the people pretty much are stuck in their silos. The company is a little too corporate for my tastes. Also, one of the big draws to this company is that they used SQL Server and Oracle, but they're doing away with Oracle (I want more Oracle experience). By this point the gentlemen are pushing me to ask more questions but I've sort of realized that we're now wasting each others time and really have nothing else to ask. Again, nice people.
On my way home I stop at a local Walmart that's supposed to have Sugar Free Kool-Aid. Can't find any on the shelves. For some reason it's become increasingly difficult to find in eastern MA. Just a little annoyance after the frustration of the interview. I get home and send them a thank you letter emphasizing my strong points. No acknowledgment to date. That afternoon, I pull out my learn VB.NET book and start reading.
Stan and Kyle I learned something today speech:
I took this as a learning experience. I realized that I always want to have a very clear understanding of the position description before I agree to an interview. Another plus is that I had some interview practice.
I'm not one to post much on message boards but I've found posting these things somewhat therapeutic (I can see why bloggers do what they do), so I'll probably update this post when something interesting happens.
LightPhoenix
First Post
I've always been amazed about how interviewing really does take practice. I've never gotten that.
That benefits thing was a little iffy. If they're not willing to talk about it, chances are they probably weren't that great. Also, IMO you were well within your rights to ask about benefits - you can't in good conscience make a decision about a job without knowing what you're getting from it.
That benefits thing was a little iffy. If they're not willing to talk about it, chances are they probably weren't that great. Also, IMO you were well within your rights to ask about benefits - you can't in good conscience make a decision about a job without knowing what you're getting from it.
Land Outcast
Explorer
Well, one of the "modern" interview methods (that is of the last five years) is about the interviewer showing the cards at first (benefits). If the postulant is interested the interview goes on, if he/she isn't convinced the interview carries on for some 5 minutes with questions from the postulant before ending or proceeding normally.
Always assuming the postulant has had contact with the official job description. :\
-
Keep on with the information gathering Tom!
Always assuming the postulant has had contact with the official job description. :\
-
Keep on with the information gathering Tom!
Rodrigo Istalindir
Explorer
I used to go on interviews for jobs I knew I didn't want just for the practice. Plus, it can be fun to jerk them around if they're obnoxious, since I didn't have anything to lose 
Another lesson to learn is that recruiters lie through their teeth. They will tell you whatever you want to hear about what the job entails, and they will tell the prospective employer what they want to hear in terms of your qualifications.
Another lesson to learn is that recruiters lie through their teeth. They will tell you whatever you want to hear about what the job entails, and they will tell the prospective employer what they want to hear in terms of your qualifications.
I can also sympathize, like some of the others here. I've been out of work for over a year now. I was laid off from a job I'd held for over 6 years, but in my case, it's been a decent thing to happen. I hate not having the steady income, but the chance this had afforded me is something I would not have been able to pursue otherwise.
I've taken the time to go back to school full time to get my BS in Computer Science. I hope to graduate in May and then try to re-enter the work force. I'm not entirely certain what I will want to do when the degree is complete, but I hope I'm able to choose from a wider variety of jobs than I was able to do in the past when I only had a high school diploma.
Good luck to you in your search. If you plan to stay in the same area, I hope the opportunities open themselves up to you.
I've taken the time to go back to school full time to get my BS in Computer Science. I hope to graduate in May and then try to re-enter the work force. I'm not entirely certain what I will want to do when the degree is complete, but I hope I'm able to choose from a wider variety of jobs than I was able to do in the past when I only had a high school diploma.
Good luck to you in your search. If you plan to stay in the same area, I hope the opportunities open themselves up to you.
Similar Threads
