Build the AI that reaches the P&L.
Senior engineers, embedded with PE-backed companies, shipping agents into production on Claude and Databricks. Six to eight people to a pod, a readout every week, no bench.
New York and remote US · SOC 2 Type II · 250+ production systems since 2016
- people to a pod, all senior
- 6 to 8
- days to the first production workflow
- 100
- weeks onsite with a client
- 1 in 6
Azure
The people you would ship with.
Part of the team in a client boardroom in New York, mapping a data platform on the whiteboard before the build. This is what the work looks like: senior people, one room, a real problem.
- production systems since 2016
- 250+
- of data and AI delivery
- 10 yrs
- headquarters; engineers across the US
- NYC
Felipe
Guido
Hema
Stephen
Six to eight people. All of them senior.
- Runs the client
Portfolio Success Partner
Owns the relationship with the operating partner and the CFO, runs the weekly readout and the board update, and keeps the work pointed at the P&L.
- Owns the bar
Delivery Lead
Sets the architecture, decides what gets cut, reviews every pipeline and agent before it ships. The person you learn from.
- Writes the code
Implementors
Two to five engineers who build the pipelines, run the agents and sit with the client's team until the run is theirs.
You scope what you build.
The engineer in the Assess room is the engineer in the Build room. There is no hand-off to a junior team after the sale.
You talk to the CFO.
Weekly, in plain English, about what shipped and what it saved. You learn to explain a pipeline to someone who signs for it.
You leave a playbook.
What you build at one company is the starting point at the next. Your work compounds across a portfolio.
A week here.
Drawn from a real engagement. The cards move; hover to hold one.
- Where
New York, or remote in the US
Onsite with a client one week in six, sometimes abroad.
- Tools
Claude, Databricks, Snowflake, dbt
Python and TypeScript. Your own Claude Code seat from day one.
- Cadence
Weekly readouts, monthly retros
Quarterly reviews with your Delivery Lead. No timesheets by the quarter hour.
Four steps, three weeks, no puzzles.
- Step 1A call with an engineer30 minutes, not a recruiter. What you have built, what you want to build.
- Step 2A working sessionTwo hours on a real, anonymized problem. Paid. You bring your own tools.
- Step 3Your Delivery LeadA conversation with the person you would work with, about how they run a pod.
- Step 4An offer in writingWithin three days of step three. Range, level and start date, no games.
Who you would talk to
Dean CirielliVP of Engineering
Rizwan YousufVP of Data and AI
Colin Van DykeCTO and co-founder
What comes with the role
- Base
- Published range per level, in the role listing
- Bonus
- Annual, tied to pod outcomes and company results
- Health
- Medical, dental and vision; the company pays the majority of premiums
- Retirement
- 401(k) with company match
- Learning
- Annual budget, plus a Claude Code seat and the platform certifications we build on
- Setup
- Home-office budget on day one; travel booked and expensed, never fronted
What we are hiring for.
Every listing carries the range and the pod it joins. If none fits, introduce yourself anyway; we read every note.
Current openings are listed on our careers site.
Common questions.
What roles is Blue Orange Digital hiring for?
Current openings are listed on our careers site, careers.blueorange.digital. We hire senior engineers to work embedded with PE-backed companies, shipping agents into production on Claude and Databricks. If nothing open fits, introduce yourself anyway; we read every note.
What is the interview process at Blue Orange?
Four steps, three weeks, no puzzles. Step one is a 30-minute call with an engineer, not a recruiter. Step two is a paid two-hour working session on a real, anonymized problem. Step three is a conversation with your Delivery Lead, and step four is an offer in writing within three days of it, with range, level and start date.
Who would I interview with at Blue Orange?
You would talk to engineering leadership, not the CEO: Dean Cirielli, VP of Engineering; Rizwan Yousuf, VP of Data and AI; and Colin Van Dyke, CTO and co-founder. Step three of the process is a conversation with the Delivery Lead you would work with, about how they run a pod.
Is Blue Orange Digital remote or in New York?
Both. Engineers work from New York or remote in the US; headquarters are in NYC, with engineers across the US. Onsite time with clients is part of the job, sometimes abroad.
What does a Blue Orange engineering pod look like?
Six to eight people, all of them senior. A Portfolio Success Partner runs the client relationship and the weekly readout, a Delivery Lead sets the architecture and reviews every pipeline and agent before it ships, and two to five Implementors build the pipelines, run the agents and sit with the client's team until the run is theirs.
What tools and benefits come with an engineering role at Blue Orange?
You work in Claude, Databricks, Snowflake and dbt, in Python and TypeScript, with your own Claude Code seat from day one. The role comes with an annual bonus tied to pod outcomes, medical, dental and vision with the company paying the majority of premiums, a 401(k) with company match, an annual learning budget and a home-office budget on day one.
Ship something that matters.
Four steps, three weeks, and an engineer on the other side of every conversation. If nothing open fits, introduce yourself anyway.