I applied through a recruiter. The process took 1 week. I interviewed at uStudio (Austin, TX)
Interview
I worked with a recruiter to start the process. I had a 30-minute phone interview with the development team manager. I then went to an on-site interview, which was divided up into multiple panels.
In the first panel, I met with two members of the dev team and completed a coding exercise involving writing a program that consumed a RESTful API. The coding was completed on my laptop, not a whiteboard, which was very refreshing. I was allowed to use any programming language and software libraries I wanted. The coding was intended to simulate pair programming in a real work environment.
In the second panel, I met with two more devs and we discussed software process and architecture topics. I then had lunch with the entire dev team. After lunch, I met with the CTO and members of the QA and Product teams to discuss more architecture and personality topics.
Overall, I found the interview process pleasant. The interviewers were clearly more interested in whether I fit culturally, that I was willing to learn new things, and that I *enjoy* learning new things. Whether I knew the answers to all of their technical questions seemed less important.
Interview questions [1]
Question 1
Describe, in as much detail as you can, what happens when you enter a URL in a web browser.
I applied through a recruiter. The process took 3 days. I interviewed at uStudio (Austin, TX) in Mar 2016
Interview
I sought this position for the purposes of getting back into a local, Austin friendly company where people matter.
The process started with a phone interview with dev lead, which led into another phone interview with a developer, and ended with a full day on-site interview. The on-site interview started with a set of technical design questions, followed by a lunch, a live coding session, and a meet and greet with various members of the team.
All in all, seems like a good dev team, but my first impression is that leadership lacks focus. Specifically, CTO, Josh Marshall opened our one on one by telling me he hadn't read my resume. Moreover, he spoke frenetically and without focus which left me with the sense that he wasn't interested in getting to know me as a candidate. A poor ending to a promising start!
Interview questions [2]
Question 1
How do you prevent a web server from being a single point of failure?
