Skip to content
BUSLAEVBook a call

Founding engineer for hire · Since 2008

You need it built.
You don’t need to hire anyone.

I’m Dmitry Buslaev — a founding engineer four times over. Startups bring me in to design, build, and ship production software: web apps, mobile apps, APIs, cloud infrastructure, and AI features that survive real customers.

Fixed scope agreed up front. Working software every week. The code lives in your repo and your cloud account from day one.

Job cardREV 2026.08
Status
Taking work — 2 slots open
Based
San Diego, CA · Pacific time
Works with
Seed to Series B, and solo founders
Engagement
2 weeks to 6 months
First reply
Within one business day
  • 15+ yrs

    Shipping production software

  • Companies built from the first commit

  • 3

    Acquisitions taken through diligence

  • ISO 27001 certifications delivered

  • $50M+

    Raised by teams I helped build

What I build

Six things startups hire me for

Pick one or stack several. Every engagement is scoped and priced before any work starts, so you know what you are buying.

Build the first version

An empty repo turned into a product real customers can use. Web app, API, database, auth, payments, deployment — the whole thing, not a prototype that has to be thrown away.

  • Web app and API
  • Auth, billing, admin tools
  • Live on your cloud account

Typical: 6–12 weeks

Add AI that actually works

Most AI features fail on cost, latency, or accuracy rather than on the model. I build the retrieval, evaluation, and fallbacks around it so the feature holds up once customers touch it.

  • LLM features and agents
  • RAG and vector search
  • Model deployment and cost tuning

Typical: 3–8 weeks

Cloud, deploys, and the boring parts

The infrastructure a startup needs and nobody wants to own: AWS accounts, environments, pipelines, monitoring, and a deploy that takes minutes instead of an afternoon.

  • AWS, Terraform, Kubernetes, Docker
  • CI/CD and preview environments
  • Cost review and cleanup

Typical: 2–6 weeks

Mobile apps

One React Native codebase for iOS and Android, wired to your backend and shipped through both app stores — including the review process, which is usually where teams get stuck.

  • React Native, iOS and Android
  • Push, offline, deep links
  • Store submission and release

Typical: 6–12 weeks

Security and compliance readiness

If enterprise buyers are asking for a security questionnaire, this is the work that unblocks the deal. I have taken two companies through ISO 27001 and kept them certified.

  • ISO 27001, SOC 2, HIPAA, GDPR
  • Threat and access review
  • Evidence and policy groundwork

Typical: 4–10 weeks

Second opinion on what you have

You inherited a codebase, your build is slowing down, or an investor wants technical diligence. I read the code, run the numbers, and give you a written assessment with a plan you can act on.

  • Architecture and code review
  • Technical due diligence
  • Fractional CTO time

Typical: 1–2 weeks

How it works

Four steps, in this order

No discovery phase that bills for a month before code exists. The first working version is usually running in week one or two.

  1. 01Day 0

    Talk it through

    Thirty minutes, no charge. You describe what you need and who it is for. I tell you honestly whether I am the right person, and what I would build first.

  2. 02Within 3 days

    Scope and quote

    You get a written plan: what gets built, in what order, what it costs, and when it lands. Fixed price per phase. If the plan looks wrong to you, we change it before anyone commits.

  3. 03Weekly

    Build in the open

    Work happens in your repository in weekly increments. Every Friday there is something running you can click on, plus a short note on what moved and what is next.

  4. 04At the finish

    Hand it over

    Your repo, your cloud account, your domain, documented and deployed. I can stay on for support or step away completely. Nothing is locked to me.

The trade-off

Three ways to get software built

I am not the right answer for every situation. Here is the honest comparison so you can place me against the alternatives.

Hire an engineer

Time to start
2–4 months to fill
Cost shape
Salary, equity, benefits, ongoing
Who builds it
Someone you have to manage
If it goes wrong
A hiring mistake you carry

Right answer once you know exactly what you need every week, and can lead them.

Hire an agency

Time to start
Weeks of proposals
Cost shape
Retainer plus change orders
Who builds it
Often juniors after the pitch
If it goes wrong
Code you cannot maintain

Right answer for large parallel teams and long roadmaps with a budget to match.

Hire me

Time to start
Days
Cost shape
Fixed price per phase
Who builds it
The person you talked to
If it goes wrong
Stop at the phase boundary

Right answer when you need working software soon and cannot afford a wrong hire.

Engagements

Four ways to work together

Tell me the outcome you need and the budget you have. I will tell you which of these fits, or tell you that it does not.

Sprint

A tight, well-defined piece of work: a prototype for an investor meeting, an integration that is blocking a launch, a deploy pipeline that keeps breaking.

Best for
One clear outcome, fast
Length
2 weeks
Billing
Fixed price

Build

The full job, split into phases you approve one at a time. Each phase ends with something deployed, so you can stop, extend, or redirect at any boundary.

Best for
A product going to real users
Length
6–16 weeks
Billing
Fixed price per phase

Retainer

A reserved share of my week for a company that has shipped and now needs steady progress, on-call cover, and someone who already knows the system.

Best for
Ongoing engineering capacity
Length
Monthly, rolling
Billing
Flat monthly

Advisory

Architecture reviews, hiring your first engineers, vendor and build-versus-buy calls, technical due diligence for a raise or an acquisition.

Best for
Decisions, not code
Length
By the hour or day
Billing
Hourly
  • Every quote is fixed before work starts. No hourly surprises.
  • Code is pushed to your repository and deployed to your cloud accounts.
  • You own everything: repos, infrastructure, domains, documentation.
  • Contracts are month-to-month. Stop at any phase boundary.
Get a quote

Track record

I have done this from zero four times

Not a résumé — context for what you are buying. Each of these started with an empty repository and ended with software that customers, auditors, and acquirers relied on.

  • 2024 — 2026

    Ensemble AI

    AI model compression · Salesforce Ventures, M13

    Founding engineer. Built the Go backend, the React dashboard, the React Native app, and the Python tooling that enterprise customers used to compress and deploy models. Ran technical discovery and onboarding for those customers myself, from the first call through production rollout.

  • 2022 — 2024

    SonderMind

    Mental health platform · 1M+ patients

    Principal engineer on platform and infrastructure. Cut deploy cycle time in half with ephemeral environments, finished the move to Kubernetes and Terraform, prepared the company for its first ISO 27001 audit, and merged two acquired systems into the platform.

  • 2017 — 2022

    TotalBrain

    Brain health SaaS · 20+ countries

    Founding engineer. Built the backend and AWS platform from nothing, then grew the team to 25. Migrated off Rackspace and halved infrastructure cost, delivered and maintained ISO 27001, and led the technical relationship with Boeing, AARP, and Accenture from pre-sales to delivery.

  • 2015 — 2017

    RoundHouseOne

    Spatial intelligence and energy analytics

    Founding engineer. Built the API and analytics dashboard behind multi-million dollar government research contracts, and a data system that lowered energy cost across 250+ Hawaii school classrooms.

  • 2008 — 2015

    CitizenGlobal

    Video editing SaaS · acquired

    Founding engineer. Architected and patented the video editing platform, built engineering from one person to thirty through Series A to C and $50M+ raised, and ran the technical side of the acquisition.

Stack

Tools, chosen to fit the job

I pick what your team can maintain after I leave, not what is interesting to me this year.

Languages
  • Go
  • TypeScript
  • Python
  • Java
  • Scala
  • Ruby
  • Bash
  • SQL
Product
  • React
  • Next.js
  • React Native
  • Node.js
  • Django
  • Spring
Cloud
  • AWS
  • Terraform
  • Kubernetes
  • Docker
  • CloudFormation
  • CI/CD
  • Linux
AI
  • LLM APIs
  • RAG
  • Pinecone
  • Model deployment
  • Evaluation
  • Claude Code
Data
  • PostgreSQL
  • MySQL
  • DynamoDB
  • MongoDB
  • Redshift
  • Snowflake
  • Redis
Compliance
  • ISO 27001
  • SOC 2
  • HIPAA
  • GDPR
  • OWASP Top 10

Questions

Asked before you ask

How soon can you start?

Usually within one to two weeks, sometimes sooner for short work. Availability is on the job card at the top of this page and I keep it current.

Do you work with non-technical founders?

Often. You bring the problem, the customers, and the decisions about what matters. I handle the technical choices and explain them in plain language, without turning every question into a meeting.

Who owns the code?

You do, from the first commit. Work happens in your repository and your cloud accounts. There is no proprietary framework and nothing that stops another engineer from picking it up.

Can you work alongside our existing team?

Yes. I join your standups, your repo, and your review process. I have hired and mentored engineers for fifteen years, so I can also help your team level up rather than working around them.

What does it cost?

Every engagement is quoted as a fixed price before work starts, based on scope. Send a short description of what you need and you will get a number and a timeline within a few days.

What if the project is too big for one person?

I will say so on the first call. For larger builds I bring in engineers I have worked with before and stay accountable for the delivery, or I help you hire the team directly.

Do you sign NDAs and work with regulated data?

Yes to both. I have worked under HIPAA and GDPR, delivered ISO 27001 twice, and been through enterprise security review with companies like Boeing and Accenture.

Where are you based?

San Diego, California, working Pacific time. Every engagement in the last several years has been remote, with overlap hours agreed up front.

Contact

Tell me what you’re building

A paragraph is enough to start. You will hear back within one business day, with either a plan or an honest pointer to someone better suited.

LinkedIn
/in/dbuslaev
Send this by email

Opens your mail app with the details filled in. Nothing is stored on this site.