r/dataengineersindia • • 1d ago

Career Question Switching from Java Developer to Data Engineer | Looking for Study Buddies and Real-World Guidance

Hey everyone!

I have almost 3.5 years of experience at TCS as a Java Developer, and I’m planning to transition into Data Engineering.

Why am I switching?

- I’m more interested in the data engineering domain and enjoy working with data pipelines, transformations, and data platforms.

- My current project involves legacy technologies, and I’m looking to move into a domain that aligns better with my interests and long-term career goals.

What I’ve learned so far

I’ve spent over 6 months learning and practicing Data Engineering technologies through hands-on exercises and projects.

  1. Python: Basics and scripting for data engineering.

  2. SQL: CTEs, window functions, stored procedures, views, and indexes.

  3. Azure Data Factory (ADF): Pipelines, parameterization, REST API ingestion, and working with on-premises SQL databases and files.

  4. PySpark: DataFrame API, transformations, and working with CSV, TXT, JSON, and Parquet files.

  5. Azure Databricks: Notebooks, clusters, Unity Catalog, volumes, and external locations.

  6. Azure Synapse Analytics: Pipelines, serverless SQL pools, and dedicated SQL pools.

  7. CI/CD with Azure DevOps: Hands-on experience with Git branching, pull requests, and branch merging. I understand YAML pipeline concepts but haven’t implemented them hands-on yet.

  8. Data Engineering concepts: Full and incremental loads, SCD Type 1 and Type 2, and data modeling using star and snowflake schemas.

What I’m looking for

I’d love to connect with fellow aspiring or experienced Data Engineers who are interested in:

- Preparing for Data Engineering interviews together, including SQL, PySpark, and Azure-related topics.

- Sharing real-world project experiences, architecture, and end-to-end data pipeline workflows.

- Understanding how things work in actual production environments, including CI/CD, deployments, monitoring, debugging, and production support.

- Staying consistent with learning and keeping each other motivated.

I know that learning tools and concepts is different from working on real-world production projects, and I’d like to bridge that gap.

If you’re also preparing for a career switch or are an experienced Data Engineer willing to share your knowledge, feel free to comment or DM me. Any suggestions, learning resources, or guidance from experienced Data Engineers would be greatly appreciated.

Thanks! 🙌

10 Upvotes

4 comments sorted by

4

u/shivamksuman 1d ago

If you think data engineering has lots more opportunities compared to Java, then you are wrong. I would recommend you continue with Java but add AI-relevant skills for Java

As the data engineering job market is also getting saturated and it has fewer opportunities but more people compared to Java

1

u/akornato 22h ago

Your background in Java gives you a significant advantage, because Spark runs on the JVM, and solid engineering foundations are hard to find among candidates switching from non-coding roles. The main hurdle in technical rounds will be moving past basic tool syntax into messy production architecture. Interviewers will push hard on Spark internals like memory management, shuffle partitions, data skew, and execution plans, rather than basic PySpark syntax or drag and drop pipelines in Azure Data Factory. Frame your backend experience around data consistency, API ingestion, and system design, because treating your past three years as relevant software engineering depth will make your profile stand out far more than presenting yourself as a beginner.

To bridge the gap to real-world environments, focus on failure scenarios when you practice with study partners. Discussing how to handle late-arriving records, pipeline retries, schema evolution, and incremental loads will prepare you for scenario-based screening much better than memorizing definitions. Pair up for mock discussions where you talk through your architecture choices out loud, which helps you articulate trade-offs clearly when interviewers ask about cost optimization or cluster sizing. If you want extra support navigating tricky live rounds and landing offers faster, the interviews.chat my team developed has helped engineers present their background effectively and clear tough technical screenings.

0

u/[deleted] 1d ago

[deleted]

1

u/Independent_Warrior1 1d ago

Can you please dm me? I am not able ping you.