Coderific

rating for International Business Machines Corporation

3.0 7 years old: OS/2 team posted on February 15, 2007

I worked on the OS/2 team in the 1990s. While some of upper-management's decisions weren't on the mark, lower management and the upper-ranked technical people went to bad for the lower-level coders much more often than not. What was then called the Software Group wasn't the place to be if you liked small, innovative projects, but it was a great place to learn all there was to know about running a large product like an operating system.

IBM has many divisions. Whatever you want in your career, there is probably a division or department with your name on it. Get in any way you can, prove your worth, then scout the internal jobs database. About the only thing IBM doesn't offer is entrepreneurial opportunities. However, a good number of IBM alumni start their own businesses. Some of them wind up back at IBM after a buyout.

A word for mid-career people:
I don't know if it's still practice, but in the 1990s, the Software Group rarely hired experienced people unless they needed to fill a specific position quickly and couldn't find a good internal candidate. If you are mid-career you may be better off taking some college courses or earning a masters degree and working through a campus recruiter. Another alternative is to work through a contracting outfit. In the 1990s, IBM subcontracted some low-level tasks to manpower firms. Subcontract "employees" could work with their "IBM managers" to bypass the normal HR weed-out process and get hired as a "real" employee.

See 8 more ratings for International Business Machines Corporation!

0 comments

Write a comment!
    scores in this rating

    development process

    clear requirements 3.0
    design and planning 4.0
    quality assurance 4.0
    automated testing 4.0
    peer review 3.0
    development environment 4.0
    development hardware 4.0
    physical workspace 4.0
    infrastructure and support 4.0
    issue tracking 4.0
    source control 4.0
    product quality 3.0

    culture

    cultivation of creativity 3.0
    mitigation of risk 3.0
    reasonable workload 3.0
    prevention of crunch time 2.0
    hitting deadlines 2.0
    taking responsibility 3.0
    development autonomy 3.0
    keeping ego in check 3.0

    compensation

    salary 4.0
    health coverage 4.0
    paid time off 4.0
    snacks 3.0
    other perks 1.0

    organization

    advancement opportunities 3.0
    employee retention 4.0
    hiring process 4.0
    quality of development management 4.0
    quality of upper management 3.0
    quality of developers 3.0
    team-to-team communication 4.0
    internal team communication 4.0
    management-developer communication 3.0

    general

    location 4.0
    nearby food 2.0
    business model 3.0
    cool technology 2.0
    vision and strategy 3.0
    warm fuzzy feeling 3.0
    overall 3.0

    preferences

    casual dress code 4.0
    use of Free Software 4.0
    development of Free Software 2.0
    use of GNU/Linux unrated
    use of Mac OS unrated
    use of Solaris unrated
    use of Windows 4.0
    use of BSD unrated
    use of Python unrated
    use of Perl unrated
    use of Ruby unrated
    use of Lisp unrated
    use of Java 2.0
    use of C# unrated
    use of Objective-C unrated
    use of C 4.0
    use of C++ unrated
    use of PHP unrated
    use of ASP unrated
    use of legacy languages unrated