Oh lol I told my boss and he bitched them out for trying to poach after only 6 months.

That was probably the worst option of all. It doesn't really benefit you at all, and it damages your reputation with the recruiter (and maybe any recruiter friends they have?)

Yeah...

Unless you're feeling extremely happy and loyal in your current company, don't talk about recruiters like that with your boss. The only exception is when mocking bad recruiters that both you and your company will never use.

Yea I feel a little unprepared for calc 2 as well. Going to grind through khan academy during the break to prepare.

Recruiting company is terrible and I have no problem never talking to them again, when I'm ready to make a change I will go through one of the other 50 companies that all have the same positions. I worked "for them" for 3 months and they were just terrible in every regard other than paying me on time.

I am guessing paragraphs in employment offers about NDAs, intellectual property rights, etc are all standard?

+1

You can negotiate that stuff out when you are more senior, but in your spot and them being IBM the reality is you just sign all of it without even reading it.

I'm actually down with it.

This recruiter is engaging in some lowlife business behavior. The recruiter's guarantee was probably 90 days but sometimes it is 180 days. Seems like the recruiter waited out the guarantee period plus a bit of time and then went after him again under the false assumption he might be an easy sale again.

Temp-to-hire is also a pretty bad business deal that good recruiters avoid. I would say the chances this recruiter sucks is 99.9 if not 99.99%. If he does have recruiter friends that are willing to listen to his war stories and commit them to memory, then you are doing yourself a favor by avoiding them as well.

The recruiter probably just has overly aggressive sales goals and has pressure to find a way to close business anyway possible.

It is good to let his boss know that this company is likely unfit to appropriately represent them in a very competitive job market, and could even be giving them a bad rep to potential candidates.

It's unlikely to help him in any meaningful way. And there's the small chance this comes back to hurt him in the future due to wanting a job/reference from this recruiter or in contacting someone that this recruiter knows about.

It's just one of those, "don't burn bridges" kind of thing to me.

The only thing I've ever worried about too much is the ability to work on code for non-work purposes. I have no idea what IBM is like these days, but some companies put in clauses that try to own everything you ever code while working for them. I would attempt to get that removed if it exists.

Congrats, let us know which offer you accept.

I actually ended up not taking the IBM offer, and accepted an offer from the other company. Much younger work force, and I will get to work on new technology instead of supporting old stuff that my be near end of life.

I actually talked to one of my professors that worked at IBM for a long time and even she advised me to take the other offer that was available to me, which made the decision a little easier. That and 10% more money, sooner start date, and better benefits.

Although I wasn't thinking and accepted the other offer before declining IBM's offer, and the manager wanted to negotiate when I told him. Oops, lesson learned. I doubt that we would have ended up much higher overall anyways.

I didn't want to say anything, but I've heard a lot of IBM horror stories. It's never seemed a very appealing place to work to me. Glad it worked out for you!

I actually didn't even apply at the other company. I had interviewed there for a co-op in the spring, but then they had a hiring freeze after acquiring another company. The manager said he had kept my resume because I made a really good impression on him, and he contacted me as soon as a position was open. That made me feel really good, and that it will likely be a great place to work.

I too have hear IBM horror stories, but also lots of good stories (although mostly from people that worked there back in the "good old days"). I think it probably would have been a great job and was a wonderful opportunity, but I just didn't want to be worried in the back of my mind about layoffs and other terrible things all the time.

Binked a 91 on my c++ midterm, no idea how that happened

Nice job! I am going to have to work on C++ diligently for the next couple of months. My job will be mostly C++ and we are a Java school.

My god, i miss java

My Python professor ussd to work for IBM. She can't stop talking about her time there. Also did I mention she is a terrible professor? Yea IBM sucks.

But anyways congrats on getting a job!

Good job! I got mine tomorrow. Not going to study at all so I am hoping at least to get a B.

I have a midterm for calc on Friday that I have to focus on.

It was really easy tbh, some of the "easy" looking questions are sorta tricky, some are really simple. The if statement questions were all pretty tricky.

He had a few like -

x = 20
y = x++

What are the values or x and y ? Which i think is kind of tricky at first glance, but maybe it isn't.


Oh and the order of operations questions were a nightmare.

One was literally:

x = 1.5 + 4 * -1.5 - (4 + 2.5) * -1.5

Which i worked out like 8 times and still couldn't get an answer.

A: X = 21, Y = 20

B: 1.5 -6 + 9.75 = 5.25 ?

Thats exactly how i did it, but the answer wasn't on the mult choice. Who'd write a stupid expression like that anyway.

Yea obviously IBM would have sucked massively, but when you are just starting out I feel like amateur excitement can make any job seem decent for the first 1-2 years and then bouncing would have been a mortal lock.

Output: 5.25

Your teacher better learn maths better. I thought I was right, I was the state champion in the orders of operation speed math even in 5th grade, lol.