Head Of Engineering

The Role
We're hiring a Head of Engineering to lead and grow a team of 6–15 engineers building d4. This is not a pure management role — you'll set technical direction, get into architecture reviews and design docs, and course-correct teams in flight, while also owning delivery, hiring, and process. You'll be the senior-most technical leader in the company and will report directly to the CPO.
 

What you'll own
- Architecture & technical direction — Own the technical roadmap for d4 across our stack: AWS/Snowflake and GCP data infrastructure, ETL pipelines orchestrated via Airflow, LLM/agentic AI integration (Claude, OpenAI, Gemini), Genie (our text-to-SQL agent), and the emerging recommendation and action layers of the platform. This is an architecture-level role — you need to deeply understand how every layer of the system fits together, including the UI layer, even though you won't be writing UI code yourself
- Team leadership — Lead, mentor, and grow a 6–15 person engineering team; set engineering standards, review process, and delivery cadence; course- correct teams in flight when architecture or execution drifts
- Hands-on involvement — Get into the weeds when it matters: architecture decisions, tricky production issues, design reviews, and unblocking teams —
not just running standups
- Deployment & infrastructure — Own the ability to deploy d4 into a client's cloud environment or onto our own managed cloud infrastructure, including spinning up and configuring cloud instances as needed
- Security & DevOps — Ensure sound security practices across the platform (data access, cloud config, client environments) and mature DevOps processes
(CI/CD, environment management, monitoring)
- Client-facing technical communication — Be able to sit across the table from client technical stakeholders and explain our architecture clearly and credibly — this role is client-facing on the technical side, not just internal
- Delivery quality — Standardize delivery processes across client deployments (we work with enterprise customers and channel partners, so consistency and
reliability matter)
- Product-first mindset — Everything here is in service of the product: building configurable, reusable features and a future-ready architecture — not
one-off client customizations. This role is scoped entirely to product/engineering; no marketing or GTM tooling
- Cross-functional partnership — Work closely with Product (data/AI roadmap) and with customer-facing teams supporting our channel partner (Tech Mahindra) and direct enterprise clients
- Scaling the org — Build out hiring plans, interview processes, and team structure as we grow
 

What we're looking for
- 10-14 years in software engineering, with 4+ years leading engineering teams of meaningful size (6+ engineers)
- Strong architectural judgment — comfortable owning system design decisions, not just reviewing others'
- Multi-cloud fluency: hands-on experience with AWS and GCP; strong understanding of Snowflake/GCP/Databricks-based data architecture
- Experience with ETL pipeline design and orchestration (Airflow or equivalent)
- Exposure to building with LLMs/AI agents in production — Claude, OpenAI and/or Gemini, agentic workflows, text-to-SQL or similar — this is core to where d4 is headed
- Architecture-level understanding of UI/front-end systems — you need to know how the UI layer fits into the whole, though you won't be writing UI code
- Solid grasp of DevOps practices (CI/CD, environment management, monitoring) and cloud security fundamentals (access control, data security, secure client environments)
- Demonstrated ability to deploy and stand-up solutions in client-owned cloud environments as well as our own managed cloud
- Strong technical communication skills — able to explain architecture clearly and credibly to client-side technical stakeholders, not just to internal teams
- Track record of shipping reliably in a startup or scale-up environment, including managing technical debt and delivery pressure simultaneously
- Comfortable operating fully remote, with strong written communication and async collaboration habits 

Strong pluses (not required)
- Experience with enterprise finance, ERP, or B2B SaaS data models — domain fluency accelerates ramp-up significantly here
- Prior experience as a first or early engineering leader (vs. inheriting an established team)
- Experience building configurable, multi-tenant product architecture (vs. bespoke per-client builds)