Figma
Data Engineer Intern (2027)
About this role
Figma seeks Data Engineering interns to build and optimize data pipelines that power analytics and decision-making across the company. You'll design reliable datasets, ensure data quality, and collaborate with cross-functional teams to make data more accessible, working on scoped projects from conception through implementation.
What you'll do
- Build, test, and document data pipelines that integrate product and business data into the warehouse
- Design foundational datasets that are trusted, well-documented, and user-friendly
- Optimize pipelines for performance and scalability
- Partner with engineers and analysts to understand data needs and deliver solutions
- Own scoped projects from problem definition through testing, documentation, and results sharing
- Develop ETL jobs and improve reliability of core data pipelines
What they're looking for
- Python or similar programming language
- SQL query writing
- Data pipeline design and ETL tools
- Large dataset handling
- Data warehouse experience
- Problem-solving and debugging
- Cross-functional communication
- Documentation practices
Benefits
- Housing stipend
- Travel reimbursement
- Mentorship from manager and mentor
- Learning and skill development opportunities
- Collaborative team environment
- Flexible office locations (San Francisco or New York)
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.
Figma
Figma is a design platform that leverages AI and machine learning to power intelligent features like search, ranking, and generative capabilities. The company is hiring software engineers, ML engineers, and support specialists to build scalable infrastructure, AI-powered automations, and support systems that serve millions of users.
- Website
- figma.com
Likely interview questions
- Walk us through a data pipeline you've built or worked with—what challenges did you face and how did you solve them?
- How would you approach optimizing a slow-running ETL pipeline?