Together AI
Software Engineer, Customer Insights
About this role
Together.ai seeks a Software Engineer to join the Customer Insights team, building event-driven systems and analytics platforms that provide customers with visibility into their AI workload activity. You'll own end-to-end features across audit logs, activity history, notifications, and dashboards while collaborating with data and observability teams to ensure trustworthy, customer-facing visibility.
What you'll do
- Build and ship customer-facing features including events, activity history, audit logs, timelines, and analytics dashboards
- Partner with Data Platform and Observability teams to integrate core data stack capabilities into Customer Insights
- Own well-defined work end-to-end from implementation through testing and rollout
- Write and maintain critical-path backend code used by multiple teams and customer surfaces
- Surface blockers early and collaborate with the team to resolve them
- Maintain freshness, completeness, and correctness of customer-facing visibility systems
What they're looking for
- Backend engineering in TypeScript, Go, Python, Java, C++, or similar languages
- Large-scale distributed systems design and operation
- Event-driven architecture
- Data modeling and schema design
- Relational and non-relational databases
- Analytics pipelines and systems
- Code review and collaborative development
- Production system ownership and troubleshooting
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.
Together AI
Together AI builds GPU compute infrastructure and open-source model customization platforms for AI developers and enterprises. The company is hiring for infrastructure operations, ML systems engineering, go-to-market technology, customer success, and GPU research roles.
- Website
- together.ai
Likely interview questions
- Walk us through a time you owned a critical-path backend feature end-to-end in production—what were the challenges and how did you ensure correctness?
- How would you approach designing a system to track and surface customer activity events across multiple services at scale?