Nice cafeteria and great food. Organized. Great d.space room with cool gadgets and resting area.
Let me start by sharing demographics. 70% Indian, 29% Chinese, 1% Everyone Else 98% Male, 2% Female
As a contractor, you are basically treated as a second-class citizen. For example, you must pay for each cup of coffee you consume ($1.89), you are not allowed to ride bicycles, sick time off or any personal time off at all, and referred to as "green badge".
From the very beginning, things were rather odd. When I started, I was left alone for about a week. No introductions to team members, no lunch, nothing.
Out of boredom, I wrote a 20-page proposal with visuals and backing stats on how to improve the software I was assigned to. Well, it was completely ignored, not even a response to an email acknowledging its existence.
My Indian manager kept polite, but very distant and didn't want to hear anything about innovations or at least upgrading .NET 4.0 to something more fresh. Oh well, okay, fine.
They don't use async, SOLID, or design patterns. The code is working, well, kinda – if you are careful about clicks, you're good.
They don't engage in technical discussions, code reviews, or any active knowledge sharing.
Tools such as ReSharper are only out of your own pocket. Also had to bring my personal headphones and mic for conf calls.
The work hours and lunch time were very strict, and I always had to start and finish the day with minute precision.
I was getting tired of paying for coffee and asked if I could bring my own coffee maker. Nope.
Long story short, the place felt like a prison. I can't say if all teams are like that, but mine was.
If you are a contractor: run.
Diversity.
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
Phone call interview about the basics of: * Algorithm * Computer Architecture * Operating Systems Mostly on: * Bit manipulation * Memory management * Process scheduling * Threads * Mutex * Semaphores * Locking mechanisms * IO
It was a phone coding challenge—no IDE or development platform was available. It was an unscheduled interview where the interviewer called me out of the blue one day. I had to describe code to my interviewer because there was no online platform for
Intel's HR contacted me for an initial phone screen. This initial screen was with two engineers who were on the team for which I would be interviewing. The questions were technical, but nothing too heavy. Shortly thereafter, I was contacted to come
Phone call interview about the basics of: * Algorithm * Computer Architecture * Operating Systems Mostly on: * Bit manipulation * Memory management * Process scheduling * Threads * Mutex * Semaphores * Locking mechanisms * IO