Skip to main content

Smarsh

Database Engineer - Professional Archive Search

US - Remote (Remote)$115k–$145kfull-timemidAdded today

About this role

Design and maintain scalable data infrastructure for a professional archive search platform serving compliance-focused clients. You'll optimize real-time data pipelines, ensure system reliability and performance, and collaborate across engineering teams to support high-velocity data processing.

What you'll do

  • Design and scale data infrastructure to handle high-velocity data reliably and securely
  • Build and optimize real-time data pipelines for archive search and compliance operations
  • Collaborate with Product, Engineering, and Site Reliability teams on system improvements
  • Ensure database performance, reliability, and security for compliance-critical workloads
  • Monitor and troubleshoot data system issues to maintain platform stability
  • Bridge application development and data reliability concerns

What they're looking for

  • Database design and optimization
  • Real-time data pipeline development
  • Data infrastructure and scalability
  • SQL and/or NoSQL databases
  • Performance tuning and monitoring
  • System reliability and observability
  • Collaborative problem-solving
  • Cloud infrastructure (AWS/GCP/Azure)
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.

Smarsh

Smarsh builds software solutions that help regulated industry clients manage digital communication risks and ensure compliance across multiple communication channels. The company is hiring for technical and sales-focused engineering roles, including Technical Support Engineers, Software Engineers, and Solutions Engineers who work across client services, product development, and enterprise sales.

Website
smarsh.com
View all jobs at Smarsh

Likely interview questions

  • Describe your experience designing databases to handle high-velocity data ingestion. How did you approach scalability?
  • Tell us about a time you optimized a slow-running query or data pipeline. What was your approach?