Search

Tim Hinderliter Phones & Addresses

  • 5012 28Th St, Seattle, WA 98108 (206) 721-3084
  • 15209 Sunwood Blvd, Seattle, WA 98188 (206) 248-5071 (206) 721-3084
  • 4921 24Th St, Seattle, WA 98108 (206) 725-4071
  • Tukwila, WA
  • Tulalip, WA
  • Snohomish, WA
  • 4921 24Th Ave S, Seattle, WA 98108 (206) 725-4071

Work

Company: Heptio Aug 2018 to Dec 2018 Position: Senior engineering manager

Education

School / High School: Lakeside School

Skills

Distributed Systems • Scalability • Agile Methodologies • Cloud Computing • Java • Software Development • Ruby • Amazon Ec2 • Linux • Software Engineering • Scrum • Management • Programming • Open Source • Programming Languages • Python • Perl • Git • Apache • Amazon Web Services • Devops • Rest • Bash • Ruby on Rails • System Architecture • Problem Solving

Industries

Computer Software

Resumes

Resumes

Tim Hinderliter Photo 1

Senior Engineering Manager

View page
Location:
Seattle, WA
Industry:
Computer Software
Work:
Heptio Aug 2018 - Dec 2018
Senior Engineering Manager

Vmware Aug 2018 - Dec 2018
Senior Engineering Manager

Heptio May 2018 - Aug 2018
Engineering Manager

Innervate Mar 2015 - Feb 2018
Chief Technology Officer at Innervate

Globalsign May 2013 - May 2014
Director of Development
Education:
Lakeside School
Skills:
Distributed Systems
Scalability
Agile Methodologies
Cloud Computing
Java
Software Development
Ruby
Amazon Ec2
Linux
Software Engineering
Scrum
Management
Programming
Open Source
Programming Languages
Python
Perl
Git
Apache
Amazon Web Services
Devops
Rest
Bash
Ruby on Rails
System Architecture
Problem Solving

Publications

Us Patents

Distributed Network Management System And Method

View page
US Patent:
20040210632, Oct 21, 2004
Filed:
Mar 1, 2004
Appl. No.:
10/790156
Inventors:
John Carlson - Seattle WA, US
Tim Hinderliter - Seattle WA, US
Leigh Metcalf - Seattle WA, US
International Classification:
G06F015/16
US Classification:
709/203000
Abstract:
A distributed network management system and method of operation. The system includes at least one hub server and at least one remote server, where the hub server and the remote server communicate with each other. The remote server additionally communicates with and monitors one or more network devices. In the event that the remote server becomes inoperational, the hub server assumes monitoring of the network device. For redundancy, primary and secondary hub servers can be provided, wherein the primary and secondary hub servers communicate with each other and are capable of communicating with the remote server. For further redundancy, primary and secondary remote servers can be provided, wherein the primary and secondary remote servers communicate with each other but independently monitor the network devices. In the peered remote configuration, the hub server is capable of communicating with either of the remote servers. Where both the hub servers and the remote servers are peered, each hub server is capable of communicating with each remote server.
Tim D Hinderliter from Seattle, WA, age ~49 Get Report