developer full time infrastructure tech

Job Details

At treble.ai, we're working to help LATAM companies to engage with their today's mobile-first users. Customer communication in LATAM used to be based on email, SMS, phone calls. Now, it is based on mobile channels such as WhatsApp, Instagram, Facebook Messenger. We're working hard to help companies effectively embrace the transition.

If you join us, you’ll be an early team member helping us shape:

  • Our company culture
  • Our engineering culture
  • The vision and execution strategy of our products

What we're looking for:

  • Someone who develops and maintains domain agnostic tools and frameworks to support software engineers within the company
  • You'll design, build and operate scalable backend systems and services that power treble's tools
  • Willing to improve engineering standards, tooling, and processes.
  • Willing to work with engineers across the company to build innovative new features that operate at scale.
  • Helping us debug production issues across services and multiple levels... of the stack.
  • Willing to work with our tools: AWS (ECS, EC2, RDS, CloudWatch, Lambda, etc), Docker, Datadog, PostgreSQL, Sentry, Notion.
  • Planning for the growth of treble's infrastructure
  • Operate and maintain AWS Infrastructure
  • Excited to collaborate with everyone on the team: engineers, customer-facing teams, product folks

Skills & Experience

  • 5+ years of working full-time as a software engineer
  • A fundamental understanding of distributed system/OS/networking knowledge
  • Have 2+ years of experience building infrastructure components / services at scale. You have a proven grasp of Computer Science fundamentals and have a strong interest in distributed systems.

Here are examples challenges we wish to work on:

  • Scale a distributed system from scratch. We've been growing fast and need an infrastructure to keep up with the growth we're currently experiencing. You'll be scaling our databases, logging and monitoring systems.
  • Optimize the latency between microservices
  • Solve concurrency issues we're currently experiencing

See something wrong with this listing?

Contact support