Toa Payoh - Senior Data Engineer (Python / JAVA / SQL)

JOB SUMMARY:

This role is ideal for someone with at least 5 years of experience in data engineering who is passionate about clean data architecture, performance optimization, and enabling data-driven decision making.

KEY RESPONSIBILITIES:

• Data Infrastructure: Design, develop, and maintain robust data pipelines and storage systems.
• Data Quality: Ensure high data reliability, consistency, and accuracy across all data flows.
• Performance Tuning: Optimize data processing jobs and system performance at scale.
• Process & Mentorship: Improve data engineering workflows and mentor junior data engineers.
• Collaboration: Work with analysts, data scientists, and backend teams to deliver timely, usable data solutions.

JOB REQUIREMENTS:

• Bachelor’s degree in Computer Science, Information Systems, or equivalent qualification.
• Experience: Minimum 5 years in data engineering or related backend roles.
• Tech Stack: Proficient in SQL, Python or Java/Scala; experience with big data tools like Spark, Flink, Kafka, Airflow, and cloud platforms (AWS/GCP/Azure).
• Data Modeling: Solid experience in building and maintaining data models, data warehouses, and ETL/ELT pipelines.
• System Design: Ability to design scalable, reliable data architectures that support analytics and real-time use cases.
• Data Governance: Familiar with best practices for data quality, security, lineage, and compliance.
• Cross-team Work: Strong communication skills and ability to work closely with product, engineering, and analytics teams.
• Fluent in English and Mandarin (written/spoken) to understand technical requirements.

Soft Skills:

• Team Mindset: Contribute to shared goals and support team members with a collaborative approach.
• Ownership: Take initiative and full responsibility for delivering high-quality data solutions.
• Adaptability: Open to feedback, eager to learn new technologies, and flexible in changing environments.
• Communication: Communicate complex technical topics clearly to both technical and non-technical stakeholders.