Snapdocs is an early-stage, rapidly growing company backed by investors like Sequoia, SV Angel, F-Prime and YCombinator. We’re a small team tackling the absolutely massive mortgage market. We build modern elegant software (read security, efficiency and joy) to be a pillar of the US economy that still relies on fax machines and manila envelopes.
The type of problems we focus on involves workflow, product design, and data. We are working to find a good authentication pattern that allows for people to work across companies in multiple roles (which is trickier than you might think!). Domain Driven Design is our guiding light. The team is growing quickly so now we’re looking for a servant-leader style Engineering Manager that has transitioned in recent years from committing code on the daily to a focus on people, velocity, & execution. That’s where you come in…
In this crucial role, your time will be dedicated to leading the software development efforts for our Incidents Management Engineering Team.
This team is the glue between Operations and the Engineering; While incident response is one of the team’s duties it represents only 20% of their work. We think of Incident Management Engineering as fulfilling four major functions:
Incidents Response Management : 
– being first line of defense & triage for any anomaly found in the system, but also designing incident response and escalation protocols that are adopted by other Engineering Teams, Customer Success and Operations
– Educate company stakeholders including Engineering, Customer Success and Operations around the protocols mentioned above
– Periodically tweak and refresh the protocolsDesign and maintain dashboard with metrics around incidents to help inform about areas of the system that require maintenance
– On a weekly base writing an incidents report for the company’s executive team
Incidents Program Management: 
– Adopt a data-driven approach to recurring incidents to make sure that they won’t happen again by either dispatching them to the correct engineering team and help with their prioritization or taking on the work needed to resolve the issue permanently and working alongside the team that owns that portion of the application
Product Engineering Teams Augmentation:
– A good amount of this team’s work consists in helping other teams develop our product, this is purposefully done so the incident management team learns the ins and outs of the application by building it and not when an incident arises. By doing so this engineering team has developed a very broad knowledge of the system.
Original Product Development Initiatives Aimed at Incident Prevention:
– The team designs and implements product features and services aimed at incident prevention. For instance, they are currently working on a custom-made monitoring service that will help detect anomalies before our customers do.
What future duties may look like for this team? This is where we would like your help. We have some ideas in line with improving Site Reliability and Observability but we’d like you to bring your experience to the table to help us push the envelope! In general your current responsibilities will span directing day-to-day efforts, leading new projects and initiatives, conducting code reviews, architecting distributed systems down to supporting the team in designing and developing high-volume, low-latency applications for mission-critical systems. Today the team of 4 full stack engineers with the goal to hire 2 more this quarter. Fully responsible for delivering world-class software, you’ll grow the capabilities of the team through hiring, coaching, mentoring and direct feedback. We are an agile scrum shop big on continuous improvement so expect to be running sprint planning meetings, stand-ups, retros & post mortems. While working closely with other engineering leaders, you’ll help drive innovation & establish best practices across the organization as we scale.
Ideally, during your IC engineering days (5 years? More?) you gained experience building service-oriented architectures that powered internal and external customers. During that time you worked with at least some of our stack (RoR, React.Js, AWS, Kubernetes, Docker), building back end services, APIs & scalable systems. You might have picked up proficiency in a few different languages (Ruby, Java, Scala, Go or the others) and programming styles (functional, object-oriented, script/procedural) along the way. These days (the past 3 years or so) you can be found coaching, teaching, mentoring, performance monitoring, managing scope, reviewing code, unblocking, and making technical decisions to drive the SDLC. You lead from within and understand that coaching and mentoring is almost always better than “managing” (but you know how and when to do that too). It would be icing on the cake if you had previous experience leading a support engineering team in the past but not a hard requirement. We have a distributed team and are comfortable hiring folks in a full remote capacity.
Colorado applicants: This role pays $149,000 – $215,000 annually plus equity in the company (pay for other locations may vary).
Snapdocs strongly values diversity and drive. We want to work with people of different backgrounds and different paths in life, and we trust our team to make smart decisions. This means we value independent work as well as collaboration. We provide excellent benefits (listed below) and are located in both San Francisco and Denver!
Our benefits include (but are not limited to):
– 21 days of vacation
– Company subsidized health, dental, vision insurance
– Flexible spending account for healthcare and dependent care
– 401(k) with up to 4% company match
– Life and disability insurance
– Commuter benefits