#1 of 1IBM Watson | Multiple positions | Pittsburgh | Onsite | Full-time | Citizen; Visa for well-qualified candidates | Scala; Java; Angular.js; Bootstrap; Python; Watson Explorer
IBM Watson in Pittsburgh has several open positions as of this posting. Unfortunately, our listing page is acting up at the moment so I cannot tell exactly which ones. Try back another time or search around a bit!
All or some of these may still be open:
* Watson Technical Product Manager
* Watson User Interface (UI) Junior Developer
* Watson Software Engineer
* Watson User Interface (UI) Developer
* Watson Quality Engineer
* Watson Support Explorer Engineer
I’m the software engineer tech lead on the Watson Explorer connectivity team and former consultant with the product's Professional Services team.
We’re looking for folks versed in Java, Scala, and the Ruby on Rails stack. The UI positions are heavily focused on Angular.js and Bootstrap. We're in new development mode right now, so if you like to start from nothing, you'll like what we're doing.
We do things like TDD, real actual pair programming†, kanban, agile-ish planning (IBM Design Thinking, not some convoluted buzzword bullshit), automated builds, “use the right tool for the job even if it’s not an IBM product”, and daily stand ups that, for the most part, never run past 15 minutes.
We like to have fun, too, having regular board game lunches and evenings, hosting meetup events, weekly communal lunch cooked by one or more of our fantastic cooks, and managers that are incredibly full-of-clue and treat us like the adults we all are.
We try to keep our interview process as bullshit-free as possible. If we think you look good on paper, we’ll reach out for a phone chat and give you the details on a pretty open-ended code test, where you’ll implement a simple library. If we like your solution, then we’ll invite you for a live culture fit and technical interview, in-person if you’re near or remote if not. This process has given us a ridiculously low turnover.
† no, really. We shoot for 50%-75% pairing, otherwise known as “pair when it makes sense”.