> Markdown version of [/jobs/ext/4725909-big-data-engineer](https://www.wearedevelopers.com/jobs/ext/4725909-big-data-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Big Data Engineer - **Company:** TP-Link Systems Inc. - **Location:** Irvine, CA, United States - **Experience:** Experienced - **Salary:** $100,000 - $120,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Airflow, Amazon Web Services, Amazon S3, Big Data, Information Systems, Databases, Data Files, Extract Transform Load (ETL), Database Development, Software Debugging, Linux, Dimensional Modeling, Python (Programming Language), Online Analytical Processing, Open Source Technology, SQL Databases, Sqoop, Data Streaming, Parquet, Wi-Fi Technology, Scripting, Data Ingestion, Apache Spark, Boto3, Electronic Medical Records, Git, Pandas, Pyspark, Debezium, Information Technology, Apache Flink, Star Schema, Apache Kafka, Vertica, Databricks - **Published:** November 15, 2026 - **Apply:** https://www.careerbuilder.com/job-details/big-data-engineer-irvine-ca--23a7230e-7b4a-49be-9de2-2fc9c206ae48 ## About the Role Big Data, Wi-Fi, Smart Homes, Customer Support/Service, Database Extract Transform and Load (ETL), Electronic Medical Records, Reporting Dashboards, Data Sets, Python Programming/Scripting Language, SQL (Structured Query Language), * 2-4 years of hands-on data development in a production environment - pipelines that run on a schedule with real downstream consumers, that you were responsible for including when they broke. * Strong SQL: window functions, complex multi-table joins, incremental loads, and the ability to work out why a query is slow. * Python for production ETL and tooling (PySpark, pandas, boto3) - code that runs on a schedule, not only notebooks. * Hands-on experience with Spark on a cloud platform: AWS EMR, Databricks, Glue, or equivalent. * Production experience with a scheduler, Airflow preferred: DAG design, dependencies, retries, and reruns that are safe to repeat. * Working understanding of dimensional modeling: fact and dimension tables, star schema, and warehouse layering. * Comfortable working on AWS (S3 with Parquet / ORC), Linux, and Git - and comfortable picking up new tools as the platform evolves. * Effective use of AI to solve data problems - using it to move faster on SQL, debugging, and unfamiliar schemas, with the judgment to catch output that looks right but isn't. * Bachelor's degree in Computer Science, Information Systems, or a related field, or equivalent practical experience. PREFERRED QUALIFICATIONS * Data ingestion or CDC tooling: DataX, Sqoop, Debezium, Fivetran, or similar. * An OLAP / MPP engine: StarRocks, Doris, ClickHouse, Redshift, or similar. * Spark performance work: partitioning, shuffle, skew, and memory tuning. * AWS cost optimization: EMR instance sizing and Spot strategy, S3 lifecycle policies. * Lakehouse formats (Iceberg, Hudi, Delta), streaming (Kafka, Flink), dbt, or a data quality framework. * QuickSight or another BI tool: dataset and permission design. * Self-directed learning: a project, an open-source contribution, or a tool you picked up on your own and put to real use ## Description * Build, run, and own ETL pipelines on EMR (Spark) orchestrated in Airflow - including their monitoring, alerting, and recovery. * Write SQL and Python for data ingestion, transformation, and the datasets that analysts and dashboards depend on. * Own data quality for what you build - run the checks before you ship and add new ones where they're missing; confirm the results are correct, not only that the job completed. * Build and extend the data models for your area: fact and dimension tables following the team's layering conventions. * Keep your jobs efficient - watch runtime and cost, and raise slow or expensive jobs rather than living with them. * Use and extend the team's shared patterns and templates, and turn work you find yourself repeating into something automated or reusable. * Work with analysts and business stakeholders to turn requests into datasets that actually get used.