Sr. Software Engineer – Infrastructure

Do you want to participate in a non-start-start-up? If the answer is “yes”, or even “what the hell does that mean?”, see below…

TurboSquid’s been around a long time, not long in history of time type of way, but we started before the first dot bomb crash in 2000 when nobody knew what 3D was and people used to argue that analog cell phones were still the best. With hard work, innovation, and good timing, TurboSquid became the web's first successful content marketplace, dominating the 3D content space like iStock dominates photography. We’ve built a platform and model for content delivery that has served us well, but the landscape has changed, and the problems are more complex, and our market is growing…we need something new.

So here's a chance to join a team of developers building a next-gen content system for tens of millions of users. Through our years of experience we have gained a lot of knowledge, but we don’t know everything, and we need smart people that want to come and share their experience and knowledge. We’re looking for developers that can quickly iterate prototypes, then dig in and take it all the way to production. We’re looking for people that can contribute to building a highly scalable architecture in AWS across multiple availability zones utilizing geo-load balancing to minimize latency and deliver a great user experience. If the last sentence made sense, send a resume to If you’ve already done something similar to it, send a resume directly to our CTO,

We’re not tied up on language, and expect our system to be a mix of whatever is the best tool for the job, but having deep knowledge of one of the following languages is necessary: PHP, Java, Ruby, or Python. By deep, we mean 7+ years; by knowledge, we mean not just semantics and syntax, but efficiency tradeoffs between different ways of solving problems in that language. Oh, and we expect you know a ton about databases as well. And by ton, we mean inner, left and outer joins, foreign keys, third normal form and when to break it, row vs. page locking, etc. Go ahead and throw in some No-SQL experience as well, we have a need for that too.

So, if this sounds interesting, send us a resume, we’d love to hear from you.

Return to Jobs