I went through a phone screen, followed by an onsite visit, where I spoke with three pairs of engineers and the hiring manager.
The interview went well by all accounts, and the manager asked for my references the next day.
Upon contacting my references, who said nothing but good things about me (this is beyond any doubt), I received a rejection email citing vague "team fit" reasons.
At no time during the interview was there any discussion of collaboration styles, etc.
To add insult to injury, the manager wasted not only my time but also the time of my references. You shouldn't ask for references until you're ready to make an offer.
This was the first time I received a rejection after my references were checked in my entire career – highly disappointing.
Silly/unimaginative programming questions, like testing two strings for being anagrams of each other.
Design a change machine that accepts an arbitrary monetary amount and produces change in fixed denominations.
The following metrics were computed from 8 interview experiences for the Cisco Software Engineer role in Seattle, Washington.
Cisco's interview process for their Software Engineer roles in Seattle, Washington is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Cisco's Software Engineer interview process in Seattle, Washington.