Data engineering & integration · Data quality & reconciliation
02 AI & Machine LearningApplied machine learning · Generative AI
03 Software & Product EngineeringCustom application development · Legacy modernization
04 Cloud & CybersecurityCloud migration & modernization · Cloud operations & support
05 Acquisition & Financial ManagementAnalysis of Alternatives · Market research & COTS/NDI evaluation
06 Program & Project ManagementProgram management & PMO support · Process improvement
Reconcile the record · instrument the definitions · ship the smallest thing that runs · close the loop.
Readiness, sustainment, acquisition and program financial systems.
IntelligenceSecure analytics, transcription and technical talent for missions.
Federal CivilianEnterprise cloud, case workflows and public financial accountability.
State, Local & TribalFederal-grade accountability on a state or municipal budget.
HealthReliability, forecasting and workforce analytics for clinical operations.
Commercial & Small BusinessFor organizations that must defend an AI-assisted decision.
Where a customer can't be named, the component and scale are characterized instead.
ALL WORKGAO, CBO and IG findings, read closely and written up plainly.
ALL INSIGHTSEngineering, data science, and Ghost Works.
OPEN ROLES INTERNSHIPSHands-on projects and practical challenges, including our Drone Development internship.
EXPLORE INTERNSHIPS →BoulevardLabs has been founder-run since 2013. We stay small on purpose: it is what lets a named person answer for a system, and it is the first thing that would disappear if we scaled the usual way.
If you want to write analysis somebody else implements, this is the wrong firm. If you want to find the problem and then build the thing that fixes it, read on.
Not aspirations. These are the constraints we have chosen, and each one costs us something we have decided we are willing to pay.
The engineer who built it joins the review. There is no delivery pyramid to route questions up.
We decline work outside our domains. That is the mechanism that keeps the depth real.
When an engagement surfaces a gap we can close in code, we close it, and you own that work.
Ghost Works postmortems go on the site. Being wrong in public is part of the practice.
Clearance helps on several of these and is not a prerequisite everywhere. If none of them fit and you think we are missing something, say so.
You will find every system that claims to answer a question, establish where they disagree, and build the pipelines that make one answer defensible, with lineage traceable to the row.
You will build models that hold up when someone outside the building asks how the answer was reached, and wire them to retrain against what actually happened.
You will analyze readiness, availability and repair pipelines for naval aviation and installation programs, and turn the findings into decisions a program office can stand behind.
You will build the screens operators actually open, inside environments that have to pass an authorization review, and you will present your work directly to the people using it.
You will design controls into systems as they are built, so accreditation evidence is produced continuously rather than assembled before an assessment.
You will take a problem worth solving before there is a contract and spend 90 days turning it into working software, a tested approach or a documented result.
Tell us about the work you have done and why this role. A partner reads every application.
Thanks. A partner will read it and reply directly.
We are not going to ask you for a week of unpaid work. We will ask you to talk through something you have actually built and where it went wrong.