Slashdot Mirror


Helping Your Ex-Employer?

ali_bubba asks: "A funny thing happened to me today, I have beeb unemployed for over 5 months, and all of a sudden my ex-Boss calls me and demands (well, it sounded like a demand) that I help her out, because her entire corporate LAN was down. Naturally, she knows that I'm kind person, but boy what attitude, so I did help her save the day. She did not even bother calling me back to thank me, (like if you get slapped, turn the other cheek, as Jesus once said) Has anyone else had this happen to them before? What actions did you take?" While I can understand that some people in this situation may harbor some ill will if place in this situation, it may behoove you to see this as an opportunity, and at the very least, an opportunity to make a little money off of your old company. It doesn't pay to burn bridges, especially if they need something that you can provide. For those who have been in this situation, how did you handle it? For others, if you were offered work from your old job, would you do it, and under what conditions would your perform said work?

23 of 721 comments (clear)

  1. Did she pay you? by essell · · Score: 4, Interesting

    You only mentioned that she did not call to thank you.. Did she at least pay you for your time?

    --
    i swear my userid used to be lower.
  2. Be Polite by BurritoWarrior · · Score: 4, Interesting

    A polite, "I'm sorry, but my current schedule precludes me from being able to help" works for me.

    Of course, if you want/need the work, then just go do it at whatever rate you think is fair. Just bite your lip and don't comment one way or the other, it only leads to problems.

  3. I've been (close to) there... by coene · · Score: 4, Interesting

    Make sure you get paid! Is she your close friend? If so, you could be nice. If not, bill them! I would suggest billing for the time you spent there to fix this incident as well, it will send a clear signal. IT support is NOT free.

    1. Re:I've been (close to) there... by sprzepiora · · Score: 3, Interesting

      i wanted to moderate this one up, however I feel I need to comment on it.
      You see I'm am on the opposite end of this situation.
      We recently layed off quite a number of our staff lately and I am left with one other employee in my department.
      Before the others left, as they were filling me in on where they left off
      I had asked if I could contact them via email to ask questions. Everyone of them said yes, and I wouldn't have been angry if they said no either.
      I will note that I have asked questions from email or AIM and gotten answers and nobody was angry about it either.

  4. Send a consultant greeting card - big fat bill by tuoppi · · Score: 5, Interesting

    Basic case handling fee: $500,00
    Case study: $280
    Rapid deployment fee: $843,00
    8 workhours: 8 * $184,00 = $1472
    Non-office hours: 4 * $380,00 = $1520
    Travel expenses: 43 miles * $2/mile = $86,00
    TOTAL: $4701

    TO BE PAID: $4701 + taxes
    DUE: TODAY

    Your previous boss didn't ask for price. That means, he is prepared to pay anything.

  5. Nortel Networks by Cheese+Cracker · · Score: 4, Interesting

    I was laid off on a Thursday, and the HR person at Nortel told me that I wasn't required to do any more work. Despite this, my manager called me the next day and told me to help them out with one of their online tools. Just like you, I'm sometimes a little bit too kind and helped her out anyway, because I felt that I needed the reference from them in order to get another job. Looking back, I regret helping her... after all, she was the one to put me on the hit list. Anyway, she got laid off three months after me, and I'm running my own business now.

  6. Well... no. by RyanFenton · · Score: 5, Interesting

    Well, seeing as the last place I was able to find work, I was only offered $5/hour... no. The guy actually had to talk to his accountant to discover the minimum wage. I'm an experienced professional C++/assembly programmer on DSPs. I was doing advertising design, web design, new product design, and planning for future PDA programming for this company too.

    His other developer and his family had to live in a trailer - and the boss "gave" him a car and phone, only to hold them over his head. When he was sick for a few days, the boss had that phone disconnected.

    The boss even proclaimed to be an experienced Europian developer, and he did fluently speak several languages... so I'm amazed he could treat people that way... and much worse than that on many occasions too. But his company was the only place that would even allow a computer person with less than 3 years experience find a job. He even made quitting a huge hassle - I had to research and quote many specific laws before he dismissed me with "it's not worth my time" to get paid for my two weeks there, even at minimum wage.

    Now I'm still looking for a job... any job. And I can't. I haven't for months. I've called half the numbers in the yellow pages and looked at all the leads in all towns within three hours drive. I have to say, looking for work as a programmer in central Florida REALLY sucks.

    Ryan Fenton

  7. Don't burn bridges... by CDS · · Score: 5, Interesting

    I had a similar situation -- I was laid off the 1st of the year. In the following months, my previous firm contacted me regularly, mostly asking how I was doing, letting me know they wanted me back & were looking for ways to accomplish that, etc.

    Then one day I got a call from them. They had a customer who wanted some work done, but it was such a small job that just drafting the agreement would be more expensive than the job was worth. They contacted me and told me if I wanted to freelance the job, they'd put me in touch with the customer. I accepted it (of course). it turned out that it was too small for even a freelance charge, but I answered the guys question and it generated positive advertising for my previous firm.

    A month later, I got another call from them -- another freelance job - this one was for the wife of the head of my old firm. I again accepted it and his wife was happy with my results.

    Then my old manager called. He didn't have a freelance offer this time -- he wanted some advice on how to collect unemployment! (yeah, business got so bad the managers were being let go...) So I was very helpful & supportive of him too -- told him where to go to sign up, what the process was, etc.

    Then I got one last call -- now I'm working full-time for my old firm again. They were so happy with my attitude and willingness to help them out even after letting me go that they found a spot for me & I'm gainfully employed again -- with my full benefits just like I never left (3 weeks vacation, I'm vested, etc). Admittedly, it WAS a paycut from my old salary, but in this market, I'm not complaining :)

    Sorry about all the rambling. I guess what I'm trying to say in a nutshell is: Don't burn your bridges. Having a positive attitude and being willing to help them out can never hurt - it can only help. Even if they don't have any openings, they may hear of other firms that need people & could suggest you -- or give you a positive review when a future employer starts checking references. You never know when someone may be talking to them and your name may come up...

  8. Got my money & some small revenge by Anonymous Coward · · Score: 3, Interesting
    I worked for a place where a new Sr. person came in who had "issues" with gay folks. Within a few months she was drumming everyone non-straight out of the place: Sudden job-performance problems, lousy schedules, not getting relevant information, etc. At the time the US State we were in had no protections against such and so one by one folks got pushed out, me being one of the last.

    To add insult to injury I didn't get paid much of my accumulated vacation time. I'd been foregoing taking my time as we were in such a crunch, got promised it would carry over, etc. Due to poor record-keeping on my part (and being young and stupid) I didn't pursue the issue much but wrote it all off as lesson-learned.

    Anyway a few moths later I got a call from a friendly former coworker asking me, in a very stilted way, about some security systems I had written, what was the password, etc. I picked up pretty fast that this wasn't actually a social call, that my friendly co-worker wasn't alone in the room, that they wanted me aware of such, and they were being pressured to make this call.

    So, I told them no, I didn't recall the exact passwords but I was sure I could break into what I'd secured and would be happy to do so under contract. I then quoted them an outrageous hourly rate, said as I was unhappy with my former employer I' double that, and no assurance of how long it would take me. My friendly former co-worker politely thanked me and said they'd "pass it on".

    Sure enough an hour later I got a call asking me to come in ASAP. So I did. I got them to confirm the rate in writing, refused to give an estimate, and sat down. And played games, very visibly, for two days, until the sum I felt I was owed in vacation time was met. About 10 minutes after that point, just as I was finishing up my report, the finance guy came in with a pre-written check (they knew perfectly well what was going on) and asked me for the password.

    I handed him my report, told him I'd call from the bank with the password as soon as I'd cashed the check. He balked at that but I pointed out that many of my payroll checks had "bounced" but had been covered by the bank, I wanted to be sure there'd by no awkward problems with this one. He threatened to void the check if I didn't give them the passwords, I said fine I'd be no worse off then before, and if he didn't get out of my way I'd call the police for imprisonment. He gave way and I left.

    So, 30 minutes later from the bank I called, told him the password used on everything, and then took some friends out for drinks, including the friendly former co-worker who had slipped out early. By the way the friendly coworker resigned the next day, the nasty Sr, person lasted another few months, the whole place went under a few years later.

    Oh, and a few times later I was in situations where Sr. folks from that place were applying for jobs and I was in the decision process, each time I knifed 'em.

  9. Intro to negotiating for younger contractors by watanabe · · Score: 5, Interesting
    This is a classic problem for people who are just starting to contract out. As someone who use to contract out, and someone who now frequently hires young contractors, I can give you a few thoughts from both sides of the fence:

    1. Every employer worth working for will expect to pay you something for your time. A helpful employer working with a young contractor will bring up the topic of compensation for you. Don't expect that to happen.

      Here's how to bring up the topic of compensation if you're not talking to a particularly helpful one:

      • Say "I'd be happy to help, and I think I have a good mix of skills to do that. My going rate is $x an hour, with a minimum of $y."
      • Agree on a price with yourself before you sit down to the negotiation. Until you've done this for a while, you're going to talk yourself down in the meeting. So, you'll intend to say the above, but instead you'll say "My going rate is $x an hour. [1 second pause, in which you think "Oh my God, that's too high. They're going to be angry."] But, for you, $x/3." I have done this, and seen it happen so many times, I can't even count them. Younger types sometimes have their hands shake when they say their price. That's a sure tip-off to an employer that they can lowball an offer.
      • When you're starting out, it's almost IMPOSSIBLE that you are going to ask for a price higher than you're worth. I know it won't feel like it, but believe me, it's true. Use the following calculation to get at a price you SHOULD NOT go lower than in your offer: Take your fair Annual Salary, divide by $2,000. This is what you would get in salary per hour as a full time employee of a company. Now, multiple by 1+ (50% for taxes and expenses + at least 50% to account for sales time, time you're not working, time you spend pitching and doing project spec and evaluation + 50-80% to account for the employers lower costs hiring a contractor, [no social security, medicare, can fire you when they want, etc.] ) = multiply by 2.8 as a BASELINE. It's not worth going below this number, trust me. You are losing money, net. So, if you made 60k as a programmer, that = $30 an hour * 2.8 = $94/hr as a baseline.
      • If you want to get to your baseline number, you can't start there with an offer. Start higher. That way IF you are talked down, you have some room before you have to say "no, sorry."
      • Don't be afraid to say "Sorry, sounds like it won't work. Call me if you change your mind." If you're never turned down at a certain price, you are too cheap!.
      • NEVER work with an employer who asks for free work, etc. You should prove your value to them, but not by doing free work. Just say "Actually, I don't work in situations like that because I've found that usually people who want a situation like that aren't prepared to pay for my real value." If they ask again, just say goodbye. TRUST ME, the money that you finally get out of them WILL NOT BE WORTH IT.
    2. Sadly, I'm late, and have to go before I finish, but for a simple book on how to negotiate, I'd recommend Gary Karrass' book, Negotiate to Close. Good luck!
    1. Re:Intro to negotiating for younger contractors by tunesmith · · Score: 3, Interesting
      You have got to be kidding. salary/2000 * 2.8??? If base = salary/2000, I've heard recommendations from between base*1.4 to base*2.0, but 2.8 is making an awfully big assumption that someone with your skillset isn't charging less.

      Some of it depends on what you're doing. If you're an internal administrator, then it is more relevant to set a static rate and stick to it, even advertise it. However, if you're a programmer bidding for projects that are about revenue, this whole rate calculation thing is pretty much irrelevant aside from a very general baseline. It's dependent on the budget available for the project, how fast/good you are.

      People forget that the whole reason freelancing works is because it is a more direct correlation to how good your skills are - it's not dependent on spreadsheets showing cost of living and other people's salaries and all that malarkey. It's just negotiation, and that's all it is. The name of the game is to find win-win scenarios where they feel like they're getting their money's worth, and where you feel like you are getting your time's worth. It's about managing expectations, and it's about intangibles.

      My first freelance gig was for my previous (laid off) base * 0.5. Horrible rate, but the client was cool, the technology was cooler, it meant new skills, it was for me to get my feet wet and try out business instincts with an extremely laid back client, and it meant some very good referrals. I don't regret it in the slightest - it was worth my time, no question.

      I recently gave a quote for base * 2.0 for an hourly rate. He reacted, "Well, here's our budget - if you think you can deliver the objective at your rate and not go over the budget, that's fine. Or if you think the budget is insane, tell us." The rate isn't even relevant to the client in these cases.

      If you're just starting out and going off of base * 2.8 just because someone told you to do so on slashdot, good luck. In the Portland market, I'd only be able to justify that if I'd be able to guarantee the objective in about 30% less time than someone else with my skillset using a market-average. And I can't do that yet, although I'm working really hard on developing my own library of pre-rolled code to make this possible. And for the freelancers that prefer fixed-cost bids and deadlines, this whole subject is irrelevant from the client's perspective, anyway.

      Curt

      --
      skkkoooonnnggggkkk ptui
  10. I've had worse by geek · · Score: 4, Interesting

    My ex boss was on the phone with the FBI telling them I hacked the network and took down the webserver (nationwide ISP with ONE webserver).

    One of the othe employees called me and told me (good friend) and advised that I call him. So I did, and within 30 seconds the server was up and all was dandy. I didn't get a thankyou, just a "If you do it again I'm going through with the FBI complaint".

    The dumb ass he replaced me with switched out the BSD kernel for the GENERIC one which couldn't handle the apache requests without running out of file handles. Of course it's all my fault.

    So consider yourself lucky she called for help. It could have been much worse.

  11. my story, or how I didn't get sued on my birthday by LuxFX · · Score: 5, Interesting

    Several years ago, I had a small contract to do flash design for the website for a small indie film. The pay structure was divided 25%, 25%, and 50% for the final. The first two were fine, and the project was going smoothly. After finishing the project though, I kept getting the run around about my final payment.

    Eventually they had the premiere of the movie, and I was invited. At this premiere I was told that, sorry, they had no more money, and couldn't pay me. They had overestimated the $$ in their bank, and it turns out the last of their money was spent on the refreshments for their premiere party. Sucks to be me, but I didn't counter them legally, it was less than $1000 and I just wrote it off as a loss and broke all connections.

    About a year later, the same people thought that they were finally getting a bite on their movie, and decided they desperately needed to update their website. They contacted me and asked why they had never received the source code for their movie, as per the contract--they needed it so that so-and-so's cousin, who 'knew flash' could update the website. I told them, because I had never gotten paid, also per the contract. When they didn't pay me, I said, the contract was broken.

    At this point they got really upset and brought in so-and-so's uncle the lawyer and told me that what I had made was a piece of crap and the money they already paid more than covered the value of the project. And that if I continued to resist, they would sue me.

    This was on my birthday. I've never had a bad birthday since. No matter what happens, I will always remember how this one was worse.

    Eventually, after spending half my birthday on the phone, I knew what I had to do. Like I said, the original amount just wasn't enough to call a lawyer about, and I decided this wasn't either. Also, I had no money and even if I won this case it would be on the other side of the country which was just more money out of my pocket. So I told them, ok, I'll give you the source code exactly as it is right now, and you'll leave me alone for good and neither one of us ever talks to the other one. Ok, they said.

    What was my trick? My code (and my flash movies are highly dependant on actionscript) was completely uncommented. It would have been a beast for me to figure out, and more so for somebody else that knew flash as well as I did. And much more so for so-and-so's cousin that 'knew flash'.

    In the end, they got off my back, I wasn't sued on my birthday, and I came out feeling like I had won anyway. Because they were never able to figure out my source, and were never able to update their website. (and incidentally, never sold their movie)

    --
    Punctanym: alternate spelling of words using punctuation or numerals in place of some or all of its letters; see 'leet'
  12. Re:Simple solution... by emag · · Score: 5, Interesting

    I actually have a friend who was a contract employee, doing all sorts of security infrastructure for some a company working for some rather large clients. He's not really bothered finding a new job in several months, but recently got a call early one morning from his old boss, who was frantic because everything was down. Unfortunately, he lowballed himself, but got a couple days of work out of the call to fix what the folks left behind had royally screwed up.

    I think he was most pleased with not realizing that, while on a conference call with the people who broke everything, the clients AND a lot of upper management were listening in, and based on what he'd said (ripping these guys a couple new assholes), the buffoons ended up being fired for a) making unannounced upgrades to a production system, b) completely failing to read release notes in the service packs they'd installed which detailed that *exactly* what happened would happen if they were installed on the version of software running.

    The "$200 an hour, minimum 8 hours" was the result of several of us doing a post-mortem on the lowballing. In truth, due to the situation, he could have likely commanded at least twice that (which illustrates just how critical these systems were to the people with Big Bucks).

    --
    "The urge to save humanity is almost always a false front for the urge to rule." --H.L. Mencken
  13. Wrong way by Ektanoor · · Score: 5, Interesting

    Many people think that IT personell are some kind of running clerks at a cafe. These ones have absolutely no respect for your brains, your experience and your sweet. More, they tend to hide their incompetence, ignorance and stupidity behind a mask of arrogance and superiority. If your ex-boss called you demanding something, the first thing you should have done was to say "Cool but that will cost you US$XXXX...". If he comes up with threats and dubious statements about your past work, you better send him fast to Hell and tell him to forget your name and your phone.

    Beware that you open-hearthed behaviour could have caused more damage rather than help to yourself. There are times when old bosses start to talk too much about their ex-employees as "smarties that left hacks and bombs to spoil our work". And when you come back and do something in half-second, they may try to use it to make a serious accusation that you tried to crook them. While I have never seen such stories getting to courts, there are pretty real examples how ex-bosses tried to extort cheap work out of their ex-employees by playing such scenarios. Personally, many years ago, I was in such situation and things nearly ended in a violent fight inside a "respectable" commercial bank.

  14. Re:whos bitch are you? by Wavicle · · Score: 5, Interesting

    When we're all dead, people will remember us for the kind deeds we did while we were walking the streets and talking the talk. The little league team you coached

    Yes!

    volunteering at a Mormon church

    Yes!

    and all those bake sales for the PTA will be what you were best known for.

    Yes!

    You are talking about deeds done for noble causes, for the public good, and for positive karma (no, not THAT karma :) ). I don't think that putting out a fire for a for-profit corporate entity is in the same ballpark.

    The only shitty part is you'll just be tossed into the Hudson River because you and your socialist family members don't have the money for a proper funeral and burial.

    You could always donate your body for academic research. Hopefully that academic research won't be the effect of the Hudson River on cadavers. Mother Theresa lived to help the needy, her funeral wasn't too shabby.

    --
    Education is a better safeguard of liberty than a standing army.
    Edward Everett (1794 - 1865)
  15. Re:Installation-specific questions by King_TJ · · Score: 4, Interesting

    Speaking of documenting what you do, it's my opinion that employees in I.T. would be wise to limit how much of this documentation they write.

    If you're writing lots of documentation for an employer, you should be getting paid as a "technical writer". If you're employed as an I.T. worker and they're demanding lots of documentation - you need to question it.

    After all, they should be paying you for your knowledge and expertise. Would you expect your doctor to write up documentation for you so you can self-diagnose future problems?

    When they start asking for lots of this, there's usually a boss masterminding it, with a flawed idea that he can "brain drain" you so his other people can perform your job. In reality, they should be hiring people who already possess the skills they need, or are capable of learning them on their own. They shouldn't need *your* documentation to achieve that goal.

  16. Re:The old joke by ACNeal · · Score: 4, Interesting

    This story reminds me of another.

    A company I used to work for had a pretty good record of treating women poorly, and long time employees poorly. They were an insurance company.

    A lady who had been there for over 30 years decided it was time to quit. She walked in one day, without any real notice, and tendered her resignation. She gave a month, to be fair, but no one new she was planning this before hand.

    She was a licensed (certified) actuary, and the entire actuarial department at this life insurace company. An insurance company without an actuary is like an accounting firm without an accountant, just bookkeepers.

    She worked her month, took a long (about two month vacation), and came back. The first I knew she had quit was when I over heard one of the gossips back in my department (IS) griping about what she was making. The gossip in question handled the printing of checks.

    The actuary came back billing $350 an hour, because they needed her services.

    They kept her on like that for the rest of the time I was working there (about another year at least). They couldn't find anyone to take her place.

  17. jesus did not preach subservience by fermion · · Score: 3, Interesting
    A disclaimer: I am not christian in the common American sense, and I get very annoyed at most christians attempt to pick and choose quotes in the bible, especially the words of jesus of Nazareth, to fulfill personal agendas.

    The 'turn the other cheek' quote is a prime example. As interpreted by the modern christian church, this statement is about subverting yourself to authority and not defending yourself against corrupt powers. However, the is another interpretation. As I learned recently, this statement, as is the case in many of Jesus' statement, is an attempt to use local customs and etiquette to equalize unequal relationship. The explanation is fascinating. In the time of Jesus if one was going to slap an inferior, one would use the back of ones hand. After the inferior person was slapped, Jesus said to turn the other cheek. This would force the assailant to use the front of the hand to attack. However, the kind of slap was an implicit acknowledgment that the person was an equal. Therefore, by turning the other cheek the victim is forcing the assailant to acknowledge equivalence if he or she attacks.

    So, far from bending over and taking the attack, the words tell us to not to be subservient, but be proactive in a peaceful way. Sending a reasonable bill for services is appropriate. If you did not agree on terms before the job, theft of services would probably not be appropriate. In the future, to 'turn the other cheek', agree on terms prior to the job, and let it be her choice.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
  18. Do it all the time by phorm · · Score: 4, Interesting

    I still keep contact with an ex-boss of mine who works in the web industry. I actually have a small part stock in the company based on work I've done, but I really do it because I like him, the company, and what they do. I do the same for other people I know, as long as I'm not super-busy, I'd rather be doing something productive than sitting on the couch with a beer on my stomach.

    I'm sure it's different for a big company, but I do what I do because I enjoy it. I've been offered to do more work again recently, but this time it's for pay because I'm more busy and thus my time is valuable.

    That being said, it's one thing to ask somebody you're on good terms with. It's another to "demand" assistance and then not give help. Geeze, I work expect to at least be offered dinner or a few drinks in such a circumstance.

    Reminds me of back in college, when I accepted food/drinks for fixing people's computers... :-)

  19. No Pay, No Play. by HealYourChurchWebSit · · Score: 3, Interesting



    I'm not sure what the terms of your separation from your old employer are, but here are a couple of random thoughts.

    First, if they are like most companies, they are in it for the money. Help them. Yes. But for a consulting fee. If they were willing to pay you while you were there, they should be willing to pay you now.

    Many companies have you sign agreements that you can't work for competitors, etc ... my point is, many companies basically say good bye and forget anything you did for us with various mutant forms of non-disclosures. If they are willing to separate at this level, they should not be suprised if you say "pay me" or "no thank you."

    Finally - in the future, you might also want to creating a formal agreement so they can't come back and sue your butt if something goes wrong.

    Remember, this is a business relationship.

    --
    --- have you healed your church website?
  20. She HIRED you back when she asked for help. by blastedtokyo · · Score: 3, Interesting
    Just go back to work on Monday. Sit at your old desk. Try to log in to the LAN.

    Business as usual

    When she called you no saturday, she hired you back. Be very gracious about getting your job back. Before you see her, tell all the old coworkers that she hired you back when she called you on saturday. Go back in, and THANK her for calling you Saturday and getting your job back.

    again, be very very gracious

    Kill her with kindness. Best case: you get your job back. Worst case: you make her look like the ass she is and you get a day of fun.

  21. It's Business by topham · · Score: 3, Interesting

    Rule #1. It's Business.
    Rule #2. Pay me.
    Rule #3. It was never personal.

    While I freely admit I don't run my life off these rules I do repeatedly remind myself of them anyway.

    I've helped a previous employer out a couple weeks after I was laid off. The prior-president of the company had moved to another city and in doing so his HD failed. I helped him install windows over the phone. Probably cost me a couple of dollars in longdistance.

    On the other hand, 6-8 months after working for my new company I received a call and was asked if I could do some work for them through the company I was working for now. (The first was a distribution company, the second a consulting company). So, the company I worked for got the work, and I got paid to help a previous employer.

    A couple years later the guy who was running the IT department after I left had lost his job and moved to another company, he gave my name to a consultant looking for a new employee to pickup some extra work he had available. I got the job and have been happier working for this company than previous. (amusingly doing pretty much the same work, but thats another story).

    Did it help being a nice guy? Sure. Did it make up for the couple of dollars I spent on a long distance call, sure.

    Would it have paid to be a really nice guy and do the work for them on the side when I was working for the consulting company... no. could have cost me my job and would not have been worth the pay.

    If a previous employer calls you up and wants you to do some work for them do it, and charge them consulting rates to do it. If they won't pay then they don't actually want you to help them.

    If they are only offering it to you because it would cost them less (and not because you can do it in less time because you know the system) then don't take it. It probably isn't in your interest. (10% less is one thing... 75% less is another...)