Skip to main content

Filevine

Site Reliability Engineer

United States (Remote)$147k–$168kfull-timemidAdded 3 days ago

About this role

Filevine seeks a Site Reliability Engineer to enhance platform reliability and scalability through infrastructure automation, observability, and deployment practices. You'll apply software engineering principles to operational challenges while supporting the legal AI platform serving thousands of legal teams.

What you'll do

  • Design and implement automation to reduce operational toil and manual processes
  • Build and strengthen observability systems for production monitoring and alerting
  • Support reliable deployments at scale and manage production incidents
  • Solve infrastructure and operational challenges affecting platform stability
  • Improve system scalability and operational maturity of the Filevine platform
  • Own and develop expertise in platform architecture and operations

What they're looking for

  • Infrastructure automation and infrastructure-as-code
  • Observability tools and practices (monitoring, logging, tracing)
  • Deployment systems and CI/CD pipelines
  • Production troubleshooting and incident response
  • Software engineering principles applied to operations
  • Scalability and performance optimization
  • Cloud platform experience
  • System design and architecture
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Filevine

Filevine builds a Legal AI platform that integrates into Word and web applications to help legal professionals with contract review, drafting, and workflow automation. The company is hiring UI engineers, software developers, and product design engineers to build and refine cloud-based AI-driven tools for the legal industry.

View all jobs at Filevine

Likely interview questions

  • Describe your experience building automation to reduce operational toil. What was the most impactful project and why?
  • How do you approach designing observability systems? What metrics and signals do you prioritize?