Software Engineer (L3)
Twilio (company site, opens in a new tab)5–7 yrsRemoteDirect career pageEst. 30–45 LPA
Posted 3h ago
Reach people at Twilio
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Twilio you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Build and scale high-scale data ingestion and processing systems handling hundreds of thousands of data points per second for Twilio Segment Data platform.
- Design and deliver robust, always-available routing experiences for data pipelines in cloud environments, ensuring system reliability and operational excellence.
- Collaborate cross-functionally with product, design, and engineering teams; mentor junior engineers; participate in on-call rotation and improve operational tooling.
Minimum Requirements
- Bachelor’s or Master’s degree in Computer Science, Engineering, or related field.
- 5-7 years experience writing production-grade code in Go, Java, Python, or similar object-oriented languages.
- Hands-on experience with high-scale messaging/streaming systems and distributed systems on cloud infrastructure.
- Location restricted to Delhi, Karnataka, Maharashtra, Telangana, or Tamil Nadu states in India.
Ideal Candidate Profile
- Experience shipping cloud-native services with CI/CD development practices and operational excellence.
- Technical depth in distributed systems, high-scale ingestion, and cloud architectures, preferably with container orchestration and observability tools.
- Comfortable working in geographically distributed teams and clearly communicating technical trade-offs and system design decisions.