Skip to main content

Collate

Software Engineer (Backend)

San FranciscomidAdded 1 month ago

About this role

Collate, an AI-powered document automation platform for life sciences, seeks a Backend Engineer to design and scale the systems powering its drug development platform. You'll build APIs, services, and infrastructure that support the company's mission to accelerate life-saving innovations, working with an experienced founding team backed by $125M in top-tier funding.

What you'll do

  • Design and develop scalable APIs and backend services using Go
  • Build reliable database solutions and optimize data management with Postgres
  • Architect and maintain cloud infrastructure on AWS with Kubernetes orchestration
  • Ensure system performance, security, and reliability at scale
  • Collaborate with AI/ML engineers on integration of models and services
  • Implement infrastructure-as-code using Terraform and Argo CD

What they're looking for

  • Backend development (Go preferred)
  • Database design and optimization (Postgres)
  • Cloud infrastructure (AWS, Kubernetes)
  • Systems architecture and scalability
  • Infrastructure automation (Terraform, Argo CD)
  • API design and development
  • Security best practices
  • Experience with Kafka, S3, or similar distributed systems
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.

Collate

Collate is an AI-powered document automation platform that accelerates drug development and medical device creation for the life sciences industry. The company is hiring Backend Engineers, Full-Stack Engineers, and Quality Engineers to build scalable systems, ensure regulatory compliance, and drive innovation in therapeutics and diagnostics.

View all jobs at Collate

Likely interview questions

  • Walk us through how you'd design a scalable API architecture for a document generation platform that needs to handle varying request loads. What trade-offs would you consider?
  • Describe your experience with Go—what projects have you built with it, and how would you approach learning it if you haven't used it extensively?