Skip to content

Instantly share code, notes, and snippets.

@sargun
Created February 22, 2014 04:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sargun/9148842 to your computer and use it in GitHub Desktop.
Save sargun/9148842 to your computer and use it in GitHub Desktop.
We're seeking talented engineers to join the Yammer Infrastructure Engineering. Our team team builds the systems, services, tools and components upon which Yammer's production services run. Working side-by-side with the rest of Yammer engineering, our goal is to simplify the operational complexity and scalability of our distributed systems so that product engineers can focus on rapidly improving end-user functionality and experience.
We believe that what distinguishes great engineers from the rest are their dedication to results over methods, ability to learn and adapt quickly, professional integrity and humility -- not specific technical skills. Engineering is here to move the business forward. Engineers who share this vision are the ones most likely to be happy here and to help us succeed.
Responsibilities:
- Help build, maintain, and direct Yammer’s operational infrastructure.
- Research, test, benchmark and evaluate new technologies.
- Solve the types of mysteries which only occur at high scale.
Qualifications:
- Ability to learn and adapt to new technologies and environments
- Operational experience with scalable distributed systems
- Experience in systems automation
- Experience in software development
- Familiarity with a wide array of technologies
Desired Skills:
- Software development
-- one or more modern strongly-typed languages: Java, C#, C++
-- one or more modern dynamically-typed languages: Javascript, Python, Ruby
-- Unix-based development and production environments
-- unit testing
-- SCM and issue tracking
- Scalabilty Distributed systems
-- modular development
-- concurrency
-- computational complexity
-- familiarity with the CAP theorem
-- data stores and message queues
-- caching
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment