Lead Architect: Product Engineer

Role overview

Lead Architect: Product Engineer at Fractal

The role

Responsibilities

• Lead the engineering team.
• Track record of owning technical design for a product, not only implementing someone else’s design.

Required qualifications

• ERP connectors, schema drift, reconciliation.
• Multi-tenant platform experience, including access control and tenant separation.
• If you like wild growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!
• Not the right fit?
• Let us know you're interested in a future opportunity by clicking Introduce Yourself in the top-right corner of the page or create an account to set up email alerts as new job postings become available that meet your interest!

Preferred qualifications and skills

• Order-to-cash or accounts receivable domain knowledge, and familiarity with SAP FI-AR or an equivalent.
• Enterprise integration

Employment details

• Location: Bengaluru [India], Mumbai

Application details

• You own the engineering side: the application, the services, the data and the platform they run on.

Additional role details

• It's fun to work in a company where people truly BELIEVE in what they are doing!
• We're committed to bringing passion and customer focus to the business.
• Cogentiq I2C is Fractal’s agentic AI Product for invoice-to-cash, covering Collections, Cash Application, Deductions, Invoice Management and Credit Risk.
• It runs on a Next.js front end, a FastAPI service layer, the Cogentiq agentic runtime, and a data tier on Azure Databricks with PostgreSQL.
• The product is led by two engineering leads at the same level.
• One owns the AI side: agents, models and everything that makes them work.
• You design it, you lead the team that builds it, and you write code yourself.
• What you will own
• Technical design of the engineering side, including the platform decisions that shape what can be built later.
• Delivery across the front end, the service layer, the data tier and the infrastructure they run on.
• The interfaces between your side and the agent runtime, agreed jointly with the AI Lead.
• Technical quality: code review standards, testing, performance, and the trade-offs taken to hit a date.
• Engineering health: CI/CD, environments, release process, technical debt and incident response.
• The engineering plan: breaking the roadmap into sprint work, estimating honestly, and flagging slippage early.
• How you will work
• Set standards, coach engineers, and keep the team unblocked.
• Stay in the code.
• Take the hardest slices yourself and set the patterns others follow.
• Work with product management on feasibility, sequencing and trade-offs, so external commitments are grounded.
• What you must have
• Ten to fourteen years building software, with at least three leading a team or a full product build.
• Deep expertise in at least one tier, and enough working command of the others to lead, review and debug across all of them.
• Strong Python, and production experience with FastAPI or an equivalent service framework.
• Practical experience of a modern front end, typically React or Next.js, enough to hold the standard even if you are not the primary developer.
• Data engineering depth: Spark and Databricks, Delta Lake, SQL, and sound judgement on what belongs in a lakehouse and what belongs in PostgreSQL.
• Enough understanding of LLM and agentic systems to build the platform they depend on and to hold engineering side of a design.
• Product engineering track record: software built for many clients, not one-off delivery for a single engagement.
• Working engineering discipline: version control, CI/CD, automated testing, environment management, structured incident handling.
• Cloud experience on Azure or equivalent.