View from Seed
DECEMBER 17, 2015
Saurya Velagapudi is a senior software engineer at Google, based in their Cambridge, Mass., I recently chatted with Saurya about how he approaches hiring engineers at Google and what founders can learn. We also talked about how he’d want to be interviewed if approached by a non-technical startup founder. (I’ve
Startup Lessons Learned
MAY 19, 2011
The low-fidelity nature of the deliverable also encourages non-designers to join the discussion. Demos have become our design reviews.” The conversation around this sketch provides enough directional insight for the rest of the team to voice any concerns, to begin the estimation process and to start coding.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
mashable.com
NOVEMBER 30, 2010
Brett Miller is the president of Custom Software by Preston (CSP). For more than 10 years CSP has impressed clients with highly effective software solutions and teams of multi-talented software engineers. There are multiple approaches you can take to staffing when it comes to IT projects.
David Teten
FEBRUARY 3, 2012
Following is a guest post from ff Venture Capital winter intern Max Segan , a Colgate senior majoring in computer science, who is starting at Facebook this summer as a software engineer. For phone interviews I recommend websites such as Collabedit to let you watch candidates code in real time. Keep candidates engaged.
www.joelonsoftware.com
MARCH 24, 2010
Joel on Software Fog Creek Compensation by Joel Spolsky Wednesday, August 30, 2000 At Fog Creek Software, the way we make sure that people are paid fairly and rewarded for excellent work is based on a professional ladder. So all Fog Creek software engineers are ranked at one of several different levels, level 8 through level 15.
blog.alinelerner.com
JUNE 21, 2013
As soon as you get someone who’s never been an engineer making hiring decisions, you need to set up proxies for aptitude. Bemoaning that non-technical people are the first to filter resumes is silly because it’s not going to change. Frequency of buzzwords (programming languages, frameworks, OSes, software packages, etc.).
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Expert insights. Personalized for you.
120 
Let's personalize your content