About the Role

We’re looking for a Security & Privacy Engineering Intern who wants to build real safeguards into production systems—not just run tools and generate reports.

You’ll work on implementing core security and privacy controls across systems handling sensitive speech data. This includes access control, encryption, auditability, and data protection in a fast-moving environment where systems are still evolving.

You’ll collaborate closely with engineering and product teams to ensure security is built into the system by design—not added later. Your work will directly impact user trust, data safety, and enterprise readiness.

If you think critically about risk, care about building secure systems, and want to see your work protect real users, this role will challenge you in the right ways.

What You Will Do

• Contribute to IAM and RBAC design and implementation

• Work with encryption and KMS to secure data in transit and at rest

• Design and implement audit trails, logging, and data retention policies

• Participate in secure SDLC practices and security reviews

• Support threat modeling and risk assessments

• Build privacy-preserving patterns for PII handling and redaction

• Document security controls, guidelines, and best practices

What We’re Looking For

• Basic understanding of IAM and RBAC concepts

• Familiarity with encryption fundamentals and key management

• Exposure to secure development practices and security reviews

• Awareness of common security risks and mitigation strategies

• Understanding of privacy concepts around PII handling

• Ability to think through trade-offs between security, usability, and speed

Founding Mindset

• You think in terms of user-perceived reliability, not just dashboards

• You ask “what does good reliability look like?” before adding metrics

• You take ownership of uptime and graceful degradation

• You balance speed of change with system stability

• You proactively identify reliability gaps before they cause incidents

Bonus

• Experience with observability tools like Prometheus, Grafana, or OpenTelemetry

• Exposure to incident management or on-call workflows

• Experience with resilience testing or chaos engineering

• Familiarity with tracing and structured logging

What Success Looks Like

Within 4–6 weeks, you should be able to:

• Own monitoring and alerting for a subset of services

• Reduce noisy alerts and improve signal quality

• Contribute to incident retrospectives with actionable insights

• Improve reliability, visibility, or response time in a measurable way

What You’ll Get

• Hands-on experience building reliability practices from the ground up

• Direct collaboration with founders and core engineering teams

• Real ownership beyond a typical SRE internship

• A portfolio of dashboards, runbooks, and system improvements

• A strong pathway into SRE, platform, or production engineering roles

Who This Is Not For

• If you want predictable systems with no incidents to handle

• If you avoid ambiguity or cross-team problem solving

• If you prefer rigid, siloed environments with predefined processes

Who Will Thrive Here

• Builders who want to actively own system reliability

• Engineers who think in terms of end-to-end systems

• Calm debuggers of intermittent and complex failures

• High-agency individuals who care about keeping systems running reliably

About the Company

We’re building the speech intelligence layer for Southeast Asia—turning real-world, accented, code-switched speech into structured, usable outputs for businesses.