An AI engineer for hire in San Diego should be a person who still writes the connector. Nidrosoft is the San Diego studio of Cyriac Ndo Zeh, a design engineer who implements AI for small and mid-size businesses: audits, custom builds, phone and receptionist agents, training, and systems the team can own.
Written by Cyriac Ndo Zeh, Founder of Nidrosoft — 12+ years building software and AI products for San Diego small businesses. Also on LinkedIn.
Key takeaways
- The model is freelance or contract engineering with a written leftover: audit, then one live process in your accounts.
- 12+ years, 125 products shipped, 16 public. Formerly Anthropic, Microsoft (Bing and Edge), Intuit, Gap Inc.
- Skills stack that shows up on the work: React Native, large language model (LLM) APIs, automation into CRM, PMS, inbox, and phone.
- Fit is usually 30-250 people, plus smaller shops if the workflow is clear. A hire is a year and a manager. A contract is a leftover you can stop.
- DIY seats, a generic SaaS chatbot, and a custom agent remain different purchase rows.
- Book a free 15-minute AI readiness call before you post a job you do not want to manage.
Contents
- When an AI engineer for hire beats a full-time seat
- The freelance and contract model
- Skills stack: React Native, LLM APIs, automation
- Twelve years and the public work
- DIY tools versus a SaaS chatbot versus a custom agent
- What the first six weeks look like
- San Diego rooms this seat fits
- What you still own
- Frequently asked questions
- Book the engineer, or post the job
When an AI engineer for hire beats a full-time seat
A full-time engineer is the right leftover when you have a year of ranked work, a manager who can run a standup, and a backlog that will not die after the first agent. Recruiting, salary, benefits, and ramp are real. This page will not invent a San Diego salary. Public compensation sites publish ranges that move.
A contract engineer is the right leftover when you have one repeating workflow, a system of record, and an inheritor who can keep Tuesday after the guest account dies. You pay for a map and a write. You can stop. You do not owe a career path to a person who finished the queue.
The fork shows up in the first sentence of the brief. “Stand up an AI practice” is a hire. “Hygiene recall writes LastAttemptAt and a coordinator still sends” is a contract. “Make the repo AI native” is a hire or a product shop. “After-hours no-cool pages only on the phrase list” is a contract.
Agencies that staff a junior bench behind a partner fail this fork. You wanted an engineer. You bought a slide and a Slack channel. SideGuy in Encinitas is a custom software leftover when objects and screens are already named. Parsons AI and Applied Intelligence are consulting leftovers when the board needs a pack. Keep those invoices separate.
The method under a contract with this studio is Embed, Diagnose, Scope, Build, Own. The commercial sequence is AI implementation for small business. If you want the hire-versus-studio comparison in operating terms, the older essay on this site still holds the same split: a person you manage versus a leftover you can revoke.
Fit is usually 30-250 people. Under 30, the later build has to pay for itself. Past 250, pick one department before week one. A hospital-owned dental service can still contract an engineer on one floor. A group that wants a center of excellence should hire.
The freelance and contract model
Freelance here means a scoped engagement, not a marketplace bid war. You are not buying 10 hours of prompt tweaks. You are buying a leftover.
Week one and two are the audit unless you already have field names and a written scope from a prior packet. Many teams should buy only that. The packet travels.
After a written go, the contract names the outcome, the system of record, the human gates, the thirty-day metric, and the inheritor. GitHub or GitLab you already pay for. Linear or Jira the standup already walks. A time-boxed guest role with logging. No personal admin account that lives forever.
Billing follows the leftover, not an open retainer this page will invent. Typical bands: readiness call free; scoped audit often low thousands; first custom agent or integration often mid four- to five-figure depending on systems. A $50/mo receptionist SaaS plan is a different leftover. This page is not a quote.
You can pause after Own. You can reopen Diagnose for a second workflow. You cannot turn the contract into an unnamed monthly brain. If you want that, post the job.
Communication is Slack or Microsoft Teams for the unofficial path, plus the board. Cyriac is the person in the standup. There is no account manager who will “align stakeholders” while someone else writes.
California recording consent and TCPA texting sit next to phone work. Ask counsel. This page is not legal advice.
For a city-shaped calendar in North County, read AI implementation Encinitas. Confirmation texts along Coast Highway are a contract-shaped job. They are not a hire-shaped practice.
Skills stack: React Native, LLM APIs, automation
Owners ask for a stack because job posts ask for a stack. The useful stack is the one that reaches the system of record.
React Native shows up when the unofficial path lives on a phone. East County trades close from the truck. A coordinator who will not open a desktop dashboard needs a queue that works on a device they already hold. Mobile is not a default first system. It is the shape when Friday happens in a parking lot.
LLM APIs are how the model is called. OpenAI, Anthropic, and peers. Prompts live next to the code. Evaluations sit on the paths you named: Spanish confirmation, after-hours phrase list, DoNotContact, money and filing gates. A prompt in a Google Doc is not an API integration. A chat window the owner pastes into is a seat, not an engineer leftover.
Automation is the write. HubSpot and Salesforce rows. Open Dental, Dentrix, EagleSoft holds. ServiceTitan, Jobber, Housecall Pro jobs. AppFolio and Buildium packets. Dealer CRM inventory. Gmail and shared inboxes. Voice and short message service (SMS) on the published number. The engineer who cannot name the write is a prompt freelancer.
Adjacent skills that show up on the same invoice: TypeScript and web clients when the queue is a desktop; webhook and export paths when the PMS will not accept a clean API; secrets management because Nerlude exists; eval suites so a model change does not silently break Thursday holds.
Skills that do not show up as the default first job: a research lab, a foundation-model train, a company-wide copilot rollout with no department, a homepage chatbot with no hours.
If your spec is already screens and objects, you may want a product shop. If your spec is a repeating workflow with unnamed fields, you want Embed first.
Twelve years and the public work
12+ years building software and AI products. 125 products shipped, 16 public. Formerly Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. Those are the allowed bio facts. They are not a promise that your recall list will look like Bing.
Public systems you can open: Omnira Dental, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude. Published results: Nexuvo 3x inventory / 80% less outreach; TokenTra 10-30% wasted spend cut; NanoBrief briefs under 2 minutes versus 3+ hours.
Omnira Dental is the practice-shaped example. Eviction Wizard is the packet-shaped example. TokenTra is the spend-shaped example. Nexuvo is the lot-shaped example. Nerlude is the credential-shaped example. Open them before you post “AI engineer” on a job board and hope.
This page will not invent testimonials. If another engineer’s public repo fits your leftover better, hire them. Take the audit map with you.
For a vertical that often needs the mobile-plus-automation mix, read AI agent for real estate agent. Listing follow-up and inbox triage are contract-shaped. Autonomy on offers is not.
DIY tools versus a SaaS chatbot versus a custom agent
An engineer for hire is the custom row. Buyers still mix the other two rows into the same requisition. Split them.
DIY seats raise drafting speed. Same day. Prompts you save. Vendor help center. Keep them. Do not call a Copilot rollout an engineering hire.
Generic SaaS chatbots and receptionists raise pickup speed. Same week. Script templates. Vendor ticket. Some plans market near $50/mo. Keep them when the script is simple. Do not call a Rosie login an engineer.
A custom agent is the contract leftover. Audit, then a write. Fields, CRM or PMS, language, after-hours rules. Pairing and files you own.
| Approach | Typical cost | Setup time | Customization | Support |
|---|---|---|---|---|
| DIY ChatGPT or Copilot | Seat licenses | Same day | Prompts you save | Vendor help center |
| Generic SaaS chatbot or receptionist | Low monthly leftover; some market near $50/mo | Same week | Script templates | Vendor ticket |
| Contract Nidrosoft engineer | Audit in the low thousands; first agent mid four- to five-figure | Two-week audit, then a written build | Fields, write path, mobile if Friday is a phone | Pairing, runbook, files you own |
| Full-time hire | Annual comp, not published here | Months of recruiting | Whatever you manage | You are the support |
The table is a fork. A UTC founder who only needs faster proposals stays on the seat row. A Chula Vista clinic that needs Spanish-first booking leaves the SaaS row when the template cannot write the PMS hold. A Kearny Mesa lot that needs a classified-site hunt stays on the contract row. A 200-person group with a year of ranked work posts the job.
What the first six weeks look like
Days 1-14: Embed and Diagnose unless you already bought the packet. Sit with the people who close Friday. Score hours, feasibility, payback. Field names. Recommended next purchase. Stop is allowed.
Days 15-30: Scope and access. Time-boxed guest role. Counsel sentence if needed. Inheritor named. Outcome paragraph. If any of those are missing, the write does not start.
Days 31-45+: Build in your tenant. Dates move with APIs. A sandbox with a fake patient named Test is not production. Production is a real row, a real hold, or a real page the on-call person already treats as valid.
Own overlaps the last stretch. Runbook. Revoke test. Thirty-day metric. Training on your files. Workshops have been run in La Mesa if the leftover is judgment rather than a connector.
A six-week story that promises five agents is theater. One workflow. One inheritor. One metric.
Bring leftovers to week one. Copilot usage. A FrontDesk, Rosie, Goodcall, Smith.ai, DentalAssist, or Voksha trial. A prior deck. A product-shop repo. Model invoices if spend is the brief. An engineer who ignores prior spend will duplicate it.
San Diego rooms this seat fits
Encinitas and Del Mar clinics along Coast Highway: confirmation texts, consult holds. La Mesa and El Cajon trades: estimate follow-up from the truck. Workshops have been run in La Mesa. Chula Vista: Spanish-first phone paths. Carlsbad and Oceanside: tourism overflow and Saturday holds. Kearny Mesa: private-party inventory after dinner. Gaslamp: reservations and no-shows. La Jolla and UTC: 40-person companies next to biotech that do not want a 40-slide operating model. Military families: DoNotContact and broken recall lists.
Commute time is part of the calendar. Remote is normal when systems are reachable. In-room days help when the unofficial stack is a clipboard. Say which you want when you book.
We will not take a brief that forbids the unofficial stack. We will not take “make us AI native” with no department. We will not take a once-a-year process and call it an engineering seat. We will not sell a homepage chatbot as the default first system. We will not claim a HIPAA certification the facts page does not carry.
What you still own
You own the repo if the contract says so. You own the prompts. You own the keys. You own the thirty-day metric. You own the decision to stop.
The engineer owns the time-boxed role until you revoke it. Own means Tuesday does not require our Slack.
If a vendor platform hides prompts and traces, ask whether you still own the system after they raise prices. If nobody internal will pair, post the job.
Public calendar: https://calendar.app.google/GCtfuTx3Ms6K7d579. Email: cyriac@nidrosoft.com.
A week-one pairing day looks like this. Morning with the unofficial path. The coordinator shares the screen, not the SOP binder. You watch ten real tasks. You write the columns on a shared doc while they work. Afternoon with security and the system-of-record owner. Time-boxed guest role. Logging on. No personal admin. If either sitting is refused, the contract stays on the audit leftover.
Sample objects a React Native queue might show a truck tech: JobType, Zip, Window, AccessNotes, LanguagePref, NeedsHumanBuy or NeedsHumanQuote. The model call happens on the server. The phone is a viewer. If the tech will not install another app, the first write is SMS plus a desktop queue for the office. Say that in Scope.
Refusals that keep the seat honest. No foundation-model train. No company-wide copilot with no department. No homepage chatbot as the default first system. No HIPAA badge this page will not invent. No Clutch profile this page will not invent. No open retainer this page will invent a rate for.
If the honest leftover after pairing is seats and a La Mesa workshop, we say that. If it is FrontDesk or Rosie, we say that. If it is a job posting because nobody will inherit, we say that. The engineer for hire is optional after the map.
Frequently asked questions
Is an AI engineer for hire cheaper than a full-time employee?
Different leftovers. A contract often lands in a mid four- to five-figure band for the first agent after an audit in the low thousands. A hire is annual compensation plus management. This page will not invent a salary. Buy the contract when one workflow is clear. Post the job when you have a year of ranked work and a manager.
Do you work in React Native or only on servers?
Both when the leftover needs both. React Native shows up when Friday lives on a phone. LLM APIs and automation into the system of record show up on every build. Mobile is not the default first screen. The queue is.
Will you join our Slack as a fractional CTO?
No. The leftover is a ranked map and a write path, plus pairing through Own. A fractional executive chair is a different hire. If you need a classroom every Tuesday, that staffing model is not published here.
Can you start without an audit?
Only if you already have field names, a system of record, human gates, and an inheritor in writing. Most teams do not. Skipping Diagnose is how you buy a pretty agent that misses the hours.
What if we already have a product-shop repo?
Bring it. Write what it must not duplicate. Assessment will say whether to extend it, wrap it, or leave it alone. SideGuy-shaped screens against a known spec can be the right leftover. Do not pay twice for the same object.
Book the engineer, or post the job
If you can name the workflow, book the call. If you have a year of work and a manager, post the job. If you cannot tell which sentence is true, book the call and we will say so.
Book a free 15-minute AI readiness call. Write cyriac@nidrosoft.com if the calendar does not fit. Bring the job, the system, the owner, and any leftover you already paid for. The engineer writes the connector. You keep the files.