New opportunity

AI Engineering Lead

Hadrius · New York, United States

About this role

Hadrius seeks a hands-on AI Engineering Lead to work onsite in New York with its founding team. The lead will own AI architecture and development across the product, including production-ready AI experiences for a securities-compliance platform.

Responsibilities

  • Get up to speed on the product, codebase and existing AI work, with an initial goal of shipping a production pull request on day one.
  • Deploy 2–3 meaningful improvements to AI experiences in the first month and take ownership of the product’s AI architecture.
  • Guide AI efforts, address scaling challenges as the client base grows, and hire and mentor new team members. The role offers substantial technical autonomy and few meetings.

Required qualifications

  • At least 6 years of engineering experience and the ability to ship production-ready backend Python code.
  • Experience building and deploying agentic experiences end to end, including logging, labeling and evaluations.
  • Experience in a fast-paced startup, clear communication and problem-solving skills, and a bachelor’s or master’s degree in computer science or a related field.

Preferred

Experience applying machine learning in regulatory technology or the legal sector. The posting also lists ML, reinforcement learning and LLMs among its skills. This is an intensive role described as not being a 9-to-5 position. Eligibility is listed as US citizen/visa only. Compensation is $240K–$340K annually plus 0.10%–0.20% equity; benefits include a 401(k) with a 100% match up to 6%, healthcare, dental and vision coverage.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

PythonMachine LearningReinforcement LearningLLMsAI agentsBackend engineeringAI architectureLoggingData labelingAI evaluationMentoringTechnical communication

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Ship while learning the product

    The first-week plan calls for a production PR on day one while learning the codebase, existing AI work, customer profile, value proposition, pricing, and roadmap.

  • Own product-wide AI architecture

    In the first month, the lead is expected to deploy 2–3 meaningful AI-experience improvements and take ownership of AI architecture across the Hadrius product.

  • Build agentic systems end to end

    The role requires production-ready backend Python engineering and experience deploying agentic experiences, including logging, labeling, and evaluations.

  • Guide AI work as the team and client base grow

    Beyond the first month, responsibilities include directing AI efforts, addressing scaling challenges, and hiring and mentoring new team members while working closely with the founding team.

Likely challenges to think through

  • Balance release speed with production discipline

    The day-one PR and first-month improvement targets suggest little ramp-up time, but the role also calls for production-ready code. Prepare an example of how you scoped a small safe release, checked its behavior, and used what you learned to plan subsequent work; this is a preparation hypothesis, not a stated Hadrius release process.

  • Evaluate AI across varied compliance inputs

    Hadrius says its AI analyzes sources ranging from messages and marketing copy to accounts and filings to identify regulatory violations. A likely difficulty is defining useful evaluations across these different inputs without treating one aggregate result as sufficient. Prepare to explain how you would choose labeled examples, inspect errors by input type, and use logging to guide improvements; the posting does not specify its current evaluation approach.

  • Remain hands-on while expanding technical leadership

    Owning architecture, guiding AI work, and hiring and mentoring could compete for time as clients increase, especially in the stated low-meeting, high-autonomy culture. Prepare an example of how you made an architectural decision, communicated it clearly, and delegated work while continuing to ship; the exact division of work at Hadrius is not stated.

03

Practice your answers

Technical practice

Suggested practice: How would you ship a safe production Python change while learning an unfamiliar codebase?

What to coverThe role calls for production-ready backend Python and a first-day production PR. Preparation suggestion: explain how you would choose a small change, understand its dependencies, test it, and limit release risk without claiming to know Hadrius’s deployment process.

Suggested practice: How would you build and deploy an agentic experience end to end?

What to coverThe posting explicitly calls for experience owning deployed agentic experiences, including logging, labeling, and evaluations. Preparation suggestion: describe the components and integration decisions you would own, and how you would establish that the experience works in production.

Suggested practice: What would you log to diagnose an AI experience that gives inconsistent results?

What to coverLogging is an explicit part of the agentic work described. Preparation suggestion: cover the information needed to reconstruct a failure, distinguish input or orchestration issues from output-quality issues, and handle sensitive compliance data carefully.

Suggested practice: How would you create useful labels for AI evaluation?

What to coverThe posting names labeling as an end-to-end responsibility. Preparation suggestion: explain how you would define label criteria, resolve ambiguous cases, and check whether the labeled examples represent the work the product handles.

Suggested practice: How would you evaluate whether an AI improvement is ready to deploy?

What to coverThe role calls for evaluations and for deploying meaningful improvements to AI experiences in the first month. Preparation suggestion: discuss representative test cases, error categories, comparison with existing behavior, and the trade-off between improvement and regression risk.

Suggested practice: How would you structure AI architecture across the product?

What to coverThe lead is expected to own the product’s AI architecture. Preparation suggestion: discuss boundaries between backend services, agentic behavior, and evaluation workflows, including when shared components help and when they constrain product-specific needs.

Suggested practice: How would you investigate AI-system bottlenecks as the client base grows?

What to coverThe posting specifically highlights scaling challenges as more clients join. Preparation suggestion: describe how you would locate a bottleneck, weigh capacity against response time and reliability, and verify that a change helps under growing usage.

Suggested practice: How would you approach compliance analysis across different kinds of source material?

What to coverHadrius says its AI analyzes data from emails, text messages, marketing copy, investment accounts, and filings to identify regulatory violations. Preparation suggestion: discuss differences in structure and context across those inputs, plus how you would evaluate errors without assuming a particular pipeline already exists.

Suggested practice: When would you favor an LLM-based agent over a simpler ML approach?

What to coverThe posting lists ML and LLMs among skills and calls for deployed agentic experiences. Preparation suggestion: compare approaches for a hypothetical compliance-analysis task using quality, operational complexity, and evaluation needs; do not assume one approach is used for every task.

Suggested practice: How would you choose the first two or three AI improvements to deploy?

What to coverThe first-month responsibility is to deploy two or three meaningful improvements while taking architectural ownership. Preparation suggestion: explain how you would use product understanding, existing AI work, observed failures, and implementation risk to prioritize changes and assess their impact.

Behavioural practice

Suggested practice: Tell me about a time you became productive in an unfamiliar system quickly.

What to coverThe role expects rapid onboarding to the product, codebase, and existing AI work. Use a real situation, the actions you took to learn and contribute, and the result; distinguish what you learned from what you initially assumed.

Suggested practice: Tell me about a time you balanced shipping speed with production quality.

What to coverThe posting sets a first-day PR goal and a first-month improvement goal. Use a real situation, the specific safeguards and trade-offs you chose, and the resulting release or lesson.

Suggested practice: Tell me about a time you made a technical decision with substantial autonomy.

What to coverThe role offers broad technical authority and few meetings while working with the founding team. Use a real situation to show how you sought input, communicated the decision, and measured its result.

Suggested practice: Tell me about a time you hired or mentored an engineer.

What to coverHiring and mentoring new team members are stated responsibilities. Use a real situation, your specific actions, and an observable result, without attributing a team outcome solely to yourself.

Suggested practice: Tell me about a time you changed course after feedback from teammates.

What to coverThe posting emphasizes coachability, clear communication, and a team-first mentality. Use a real situation to explain the feedback, what you changed, and the result for the work or collaboration.

02

Sharpen your knowledge

Topics to prepare

  • End-to-end agentic systems

    Review how an agentic experience moves from inputs and decisions to deployed behavior, logging, labeling, and evaluation. Exercise: draw a lifecycle diagram and identify where failures would be detected. The posting explicitly requires end-to-end ownership of deployed agentic experiences.

  • Evaluation and improvement criteria

    Exercise: define how you would compare an existing AI experience with a proposed improvement, including labeled examples and failure categories. This prepares for the stated first-month goal of deploying 2–3 meaningful improvements; the posting does not prescribe a particular metric.

  • Product-wide AI architecture and growth

    Exercise: sketch the boundaries between AI components and the rest of a hypothetical product, then explain what you would revisit as client volume grows. The role owns AI architecture across the product and explicitly calls out scaling challenges.

  • Securities-compliance context

    Exercise: map the source’s examples—emails, text messages, marketing copy, investment accounts, and filings—to possible inputs and review questions, without assuming specific regulatory rules. Hadrius describes analyzing these materials for potential violations; prior ML work in regtech or legal is a nice-to-have, not a requirement.

  • Early prioritization and technical leadership

    Exercise: outline what you would need to learn about the product, customers, roadmap, codebase, and existing AI work before prioritizing changes; explain how you would communicate tradeoffs and support a new teammate. These are grounded in the first-week goals and later responsibility to hire and mentor.

Skills to revise

  • Production-ready backend Python

    Exercise: implement a small, testable Python backend change and write a concise PR description covering behavior, tests, and deployment risk. The posting asks for production-ready backend Python and sets a day-one goal of pushing a PR to production.

  • Agent logging, labeling, and evaluation

    Exercise: use synthetic agent runs to record inputs and outcomes, label failure cases, and compare results before and after a change. This practices the logging, labeling, and eval work explicitly named in the qualifications.

  • Shipping a scoped AI improvement

    Exercise: take a hypothetical existing AI experience, specify one measurable improvement, implement a small change, and state how you would verify it after deployment. This mirrors the first-month expectation to deploy meaningful improvements without assuming Hadrius’s current implementation.

  • Explaining architectural decisions

    Exercise: give a short walkthrough of a system you built or a hypothetical design, covering tradeoffs, scaling concerns, and what you would delegate or mentor on. Clear communication, technical authority, scaling, and mentoring are all named in the posting.

04

Your preparation checklist

  • Map Hadrius’s stated problem

    Prepare a one-page summary of how Hadrius says it uses AI to analyze communications, marketing copy, accounts and filings for securities-compliance violations. Note what remains unknown about its customers, product and roadmap rather than assuming access to internal details.

  • Build an end-to-end agentic project walkthrough

    Choose a system you built and deployed, if available. Prepare a diagram and concise account of your ownership, including logging, labeling, evaluations, deployment decisions and what the results showed; these are explicit qualifications for the role.

  • Show production Python engineering judgment

    Prepare a backend Python code example or past pull request you can discuss, with tests, failure handling and rollout decisions. Be ready to explain how you would scope a safe first production PR after learning Hadrius’s codebase; the posting sets a day-one PR goal.

  • Practice an AI architecture design exercise

    Sketch a hypothetical architecture for reviewing high-volume compliance data, covering agent boundaries, evaluation, observability and scaling as clients grow. Label it as a proposal, not Hadrius’s existing design, and identify trade-offs you would validate with the team.

  • Draft a first-month prioritization plan

    Outline how you would learn the existing AI work, identify candidate improvements and select 2–3 meaningful changes using evidence from users, evaluations and engineering constraints. The posting expects improvements in the first month and product-wide AI architecture ownership.

  • Prepare leadership examples and interview questions

    Have brief examples of autonomous technical decisions, startup problem-solving, clear communication and mentoring or hiring, where applicable. Ask the founding team how it defines a meaningful AI improvement, what scaling issues are emerging and how engineers balance broad ownership with collaboration; the listed interviews include systems deep-dives and engineer chats.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…