Time since we first saw it
Day 4
Early. Similar jobs usually come down between day 7 and day 53.
From 7,804 similar postings that came down. Coming down is not always a hire.
Pune, Maharashtra
Actively hiring, first seen by us 4 days agoWork setup in the employer’s posting: hybridFrom the employer’s posting
Employment type Full-time
Employment type in the employer’s posting: Full-timeFrom the employer’s posting
The Data Architect owns the technical foundation of a new data-intensive benchmarking and analytics capability embedded in Onit's enterprise legal operations platform.
Select the data platform for large-scale analytical queries, with documented cost and performance basis
Design a canonical data model that multiple source systems feed and product surfaces consume
Define and publish service contracts and API specifications, contract-first
Set and defend measurable latency, refresh cadence, and availability targets
Design tenant data isolation enforced structurally, not by convention
The Data Architect owns the technical foundation of a new data-intensive benchmarking and analytics capability embedded in Onit's enterprise legal operations platform. This is a hands-on, engineering-focused architecture role at the start of a multi-phase programme, and the work is front-loaded: within the first quarter, the Data Architect will select the data platform, design the canonical data model that several product surfaces depend on, define the service contracts, and set the performance and multi-tenant data-isolation guarantees the team builds against. Working closely with the Lead Engineer, Lead Designer, Product Management, and Data Engineering, this role stays in the code, the query plans, and the review conversations rather than handing designs over a wall.
Evaluate and select the data platform for large-scale analytical queries, with a documented cost and performance basis for the decision
Design a canonical data model that multiple source systems feed and multiple product surfaces consume
Define and publish service contracts and API specifications using a contract-first approach
Set and defend latency targets, refresh cadence, and availability requirements, and make them measurable rather than aspirational
Design tenant data isolation so that it is enforced structurally, not by convention
Experience evaluating and selecting data platforms for large-scale analytical workloads, with a documented cost and performance basis for the decision.
Strong SQL and relational data modelling; practical experience with analytical or columnar data stores and a clear view of when each is appropriate.
Experience designing canonical data models that multiple source systems feed and multiple product surfaces consume, with figures that reconcile consistently.
Experience designing and operating multi-tenant SaaS systems, including data isolation enforced structurally rather than by convention.
Experience retrofitting analytics or reporting capability into an existing transactional product.
Experience working with incomplete or inconsistent source data, and designing systems that stay trustworthy despite it.
Experience with data anonymisation or aggregation where privacy guarantees matter.
We're redefining the future of legal operations through the power of AI.
In the employer’s words · Read in context
Actively hiringFirst seen by us 4 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 4
Early. Similar jobs usually come down between day 7 and day 53.
From 7,804 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
• Experience evaluating and selecting data platforms for large-scale analytical workloads, with a documented cost and performance basis for the decision. • Strong SQL and relational data modelling; practical experience with analytical or columnar data stores and a clear view of when each is appropriate. • Experience designing canonical data models that multiple source systems feed and multiple product surfaces consume, with figures that reconcile consistently.
• API design experience with a contract-first mindset. • Cloud platform experience (AWS), including infrastructure as code. • Experience retrofitting analytics or reporting capability into an existing transactional product.
Complete your application on jobs.lever.co. The employer’s form will show what is required.
Already applied? Track this application
We file this job under Data Leadership, by the work the posting describes.
Data leaders run data teams or design how a company's data fits together. Managers hire, set priorities and answer for whether the data work pays off; architects choose the systems and the shape of the data.
Expect years of hands-on data work, experience leading people or projects, and the ability to explain tradeoffs to executives.
Unlike a senior engineer or analyst, most of a data leader's week goes to people, planning and decisions rather than building.
The government has no code for data leaders, so these figures are for the closest group, computer and information systems managers, which includes data processing and data operations managers.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 11-3021.
The Data Architect owns the technical foundation of a new data-intensive benchmarking and analytics capability embedded in Onit's enterprise legal operations platform. This is a hands-on, engineering-focused architecture role at the start of a multi-phase programme, and the work is front-loaded: within the first quarter, the Data Architect will select the data platform, design the canonical data model that several product surfaces depend on, define the service contracts, and set the performance and multi-tenant data-isolation guarantees the team builds against. Working closely with the Lead Engineer, Lead Designer, Product Management, and Data Engineering, this role stays in the code, the query plans, and the review conversations rather than handing designs over a wall.
• Architecture Ownership: Own the end-to-end architecture for a data-intensive analytics capability embedded in an existing enterprise product.
• Data Platform Selection: Evaluate and select the data platform for large-scale analytical queries, with a documented cost and performance basis for the decision.
• Canonical Data Model: Design a canonical data model that multiple source systems feed and multiple product surfaces consume, ensuring figures reconcile consistently across every surface.
• Service Contracts & APIs: Define and publish service contracts and API specifications using a contract-first approach.
• Non-Functional Requirements: Set and defend latency targets, refresh cadence, and availability requirements, and make them measurable rather than aspirational.
• Multi-Tenant Data Isolation: Design tenant data isolation so that it is enforced structurally, not by convention.
• Architecture Decisions & Reviews: Write architecture decision records that explain trade-offs honestly, including what would change the decision, and review designs and code across the team.
• Cross-Functional Translation: Translate technical constraints into terms Product and Design can act on, and translate their requirements back into architecture.
• Typically 10+ years in software engineering, including substantial time in an architect, principal, or staff-level role owning system-level decisions.
• Demonstrable experience designing data-intensive applications: systems where query performance over large datasets is the central problem.
• Experience evaluating and selecting data platforms for large-scale analytical workloads, with a documented cost and performance basis for the decision.
• Strong SQL and relational data modelling; practical experience with analytical or columnar data stores and a clear view of when each is appropriate.
• Experience designing canonical data models that multiple source systems feed and multiple product surfaces consume, with figures that reconcile consistently.
• Experience designing and operating multi-tenant SaaS systems, including data isolation enforced structurally rather than by convention.
• Hands-on performance engineering: able to profile a slow query, decompose a latency budget, and define what to measure and at which percentile.
• Writes decisions down clearly (e.g., architecture decision records that explain trade-offs honestly) and can defend them to both engineers and non-engineers.
• Working proficiency with AI tools (e.g., Claude, GitHub Copilot) to accelerate design exploration, query analysis, and documentation, with the judgment to critically evaluate AI-generated output.
• API design experience with a contract-first mindset.
• Cloud platform experience (AWS), including infrastructure as code.
• Experience retrofitting analytics or reporting capability into an existing transactional product.
• Experience working with incomplete or inconsistent source data, and designing systems that stay trustworthy despite it.
• Background in enterprise B2B SaaS or the legal technology domain.
• Experience with data anonymisation or aggregation where privacy guarantees matter.
Full-time
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Pune, Maharashtra
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.