Senior Java Architect – Transaction & SQL Reverse Engineer

TCS•San Jose, CA

About The Position

We are seeking a highly experienced Senior Java Application Architect to reverse engineer data access and transactional behavior across a large portfolio of enterprise Java applications. The role focuses on extracting embedded SQL, reconstructing transactional workflows, and translating runtime behavior into testable data contracts and workload signatures to support large-scale database modernization initiatives. This position plays a critical role in pre-model validation and database compatibility assessment, particularly for migrations from traditional RDBMS platforms (e.g., Oracle) to distributed databases such as Google Spanner.

Requirements

10+ years of experience in Java application architecture
Deep expertise in: JDBC Transaction management (local and distributed) ORM internals (Hibernate, JPA)
Strong SQL skills, including: Complex joins Subqueries Transactional SQL patterns
Proven experience reverse engineering large, legacy enterprise systems
Ability to analyze and understand code written by multiple teams over many years
Strong analytical and problem-solving abilities
Excellent written and verbal communication skills
Ability to work across architecture, database, and QA teams
Comfortable operating in ambiguous, highly technical environments

Nice To Haves

Experience with database modernization or cloud migrations
Familiarity with distributed databases (e.g., Google Spanner)
Experience in financial services or other transaction-intensive domains

Responsibilities

Analyze large and complex Java application codebases utilizing: JDBC ORM frameworks (Hibernate / JPA) Custom data access layers
Extract embedded SQL statements and transaction boundaries from application code.
Identify implicit runtime assumptions, including: Query ordering dependencies Locking behavior Transaction isolation levels Retry and failure handling mechanisms
Normalize extracted SQL into reusable and standardized SQL signatures.
Map SQL signatures to: Database tables and columns Transaction scopes and logical units of work
Identify SQL and transaction patterns that are incompatible with distributed databases such as Spanner.
Reconstruct logical transactions spanning multiple queries and service layers.
Identify business workflows embedded within application code.
Translate low-level implementation details into intent-based transactional contracts.
Create behavioral models that reflect real-world production workloads.
Partner with Oracle database architects to validate actual runtime behavior and constraints.
Collaborate with Google Spanner architects to assess feasibility, risks, and required design changes.
Support QA and performance teams in developing realistic workload replay and test scenarios.