ADVISORY
Charles Trinh — Engineering Team Assessment | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Most engineering problems look like process problems and are really team problems, or the other way round. I read the team's actual delivery record, interview the people in it and report what is strong, what is brittle and what would change the trajectory in a quarter.
Start with the delivery record, not the people
An engineering team's delivery record is the cheapest evidence available and almost nobody reads it. I pull the last two quarters of what actually shipped, when it shipped, how often it was reworked and how many defects were found after release. I compare that to what the team said it was going to ship. The gap between the plan and the shipped work is the first signal about whether the problem is planning, estimation, or capacity. It is rarely the people in isolation; it is the gap between the work and the system around it.
I look at the change record for the systems that carry the most risk, and measure the time from change to production and the failure rate afterwards. A team whose changes take three weeks to get through review and whose failure rate is high is not a team with a review problem alone; it is a team with a system that does not trust its own tests. I follow the history of the last thirty production incidents, because that record shows what the team has learned and, more often, what it has not.
The assessment is done before I meet anyone individually. That ordering matters: it means my conversations with the engineers are about their experience, not about verifying what I think I already know. It also means I can ask the right questions and not waste the team's time with a survey. The delivery record is documented in the report with the raw data behind it, so the findings can be tested by the leadership rather than taken on trust.
Interviewing the team without breaking it
The people assessment is short and structured. I spend forty-five minutes with each engineer and each lead, one on one, in private. I ask three questions and let them talk. What is the hardest part of your job today? What is the change you would make if it were yours to make? What stops it? The answers are consistent across teams more often than not, and the third question is where the honest assessment comes from, because it gives people permission to name what they have not been able to raise.
I do not ask people to rate their manager. I do not ask whether they plan to leave. I do not relay any statement to a manager without consent, and I confirm that before the interview starts. The assessment draws on what they tell me in aggregate and on what they are willing to attribute. That boundary is what makes the interview usable; a team that thinks a consultant is a tool of management will not tell the consultant anything useful.
I also interview the people around the team who depend on its output: the product lead, the compliance lead, the operations lead and, if the engineering is healthcare-specific, a clinician who uses the system. They often describe problems the engineering team has not noticed because they sit outside its frame. A clinician's description of a workflow defect carries more weight in my report than any process document.
The skills picture is narrower than the CVs suggest
A team of capable developers can be short of a specific capability and still look strong on paper. I look at where the team does its own work and where it leans on someone else: who writes the tests, who debugs production, who handles the database migrations, who talks to the security team. The concentration of these functions in one or two people is a continuity risk and a quality risk. A single person owning the migrations usually means the migrations are not peer reviewed.
In healthcare the specific gaps usually show up in audit logging, data de-identification, secure integration and release engineering. I test each of these with a small, real piece of work and observe the team's approach rather than asking about it. The release gate is a particularly good test: I ask the team to describe the path a change takes from commit to production and I ask what would block it. The answer shows how much of the pipeline they own versus how much they have outsourced to luck.
Where the team has built strong practices, I say so in the report and keep the specific names and patterns so the recommendation preserves them. An assessment that is uniformly negative is not credible, and it tells the team that the assessor is not listening. The strengths are half the value of the report: they are what the leadership protects while it fixes the weakest areas.
Findings written so that leadership can act
The report is structured as findings with evidence, a severity and a recommended action. Each finding has a named person who owns it and a date for the first review. I do not produce a list of generic recommendations. Each action is specific: this capability sits with one person and should be duplicated by the end of the quarter; this test suite has not been updated in three months and covers only 20 per cent of the flow; this team does not have an on-call rotation and its engineers lose six hours a week to incidents nobody is accountable for.
The report is written in a language the product lead and the finance lead can act on, because in a small healthcare company the assessment's value is in enabling decisions by leadership, not in replacing the engineering lead. Where the team's issue is capacity, I quote the cost of the work and the alternative of a hire versus a short engagement to repair the weakest point. Where the issue is judgement, I quote the specific record and what should change.
The action plan has three horizons: this month, this quarter and the next two quarters. The first horizon is limited to actions that the existing team can take without a new hire. The second horizon includes changed priorities and process changes. The third is where the structural changes live. That structure makes the assessment deliverable as much as a review, and that is how it gets used rather than filed.
What the assessment is not
The assessment is not a performance review. I do not assess individual engineers for promotion, demotion or lay-off. The findings are about the team and the system. Where I find an individual whose capability is the limiting factor, I describe the pattern without naming them in the report, and I say in person what I saw to the manager who can act on it. That division preserves the team's willingness to talk, and it keeps the assessment inside the bounds of what I was engaged to do.
The assessment is also not an audit. I do not certify security or compliance; that work belongs to the HIPAA security programme and its assessors. Where I see a compliance risk in the team's practice, I describe it as a risk and hand it to the compliance lead. An engineering assessment that quietly becomes a compliance assessment puts the organisation in a position of believing it has evidence it does not have.
On completion I present the report to the leadership in one session and stay available for a month of follow-up questions. The fractional CTO arrangement is a common follow-on when the assessment identifies gaps leadership wants to close with a part-time technical lead. The report and its action plan are handed over; they are the client's documents, not mine.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — engineering team assessment — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.