Summary
- A 2015 professional publication lists Ahmad Faqih as an Engineer in Training and Project Field Engineer at Falcon Engineering Services. A later City of Cypress procurement submittal presents him as a Construction Manager/Construction Inspector with a California PE number and QSD/P notation.
- City of Corona records add two distinct forms of evidence. One agreement names Faqih as key personnel and Lead Roadway Inspector. A separate amendment for construction management and inspection on the McKinley Street Grade Separation Project identifies him as FALCON's Secretary on the consultant signature page.
- These records support a narrow account of visible role development and contract responsibility. They do not establish company or project ownership, sole technical leadership, individual responsibility for every contractual duty, or personal credit for project outcomes.
A career becomes visible through documents built for other purposes
Most public-works professionals do not leave behind a conventional public biography. Their work appears indirectly, inside qualification packages, staff schedules, contract exhibits, amendments and signature pages. Those records are not written to narrate a life. They are written so a public agency can identify a consultant, compare proposed personnel, define services, authorize spending and preserve a record of who signed. That difference gives the documents both their value and their limits.
They can be unusually precise about a title on a particular date, yet silent about private motives, internal team dynamics or the eventual result of the work.
Ahmad Faqih's public record has that shape. The available documents do not support an expansive executive profile or a story of personal ownership. They support something more specific: a sequence in which Faqih is first identified in a field-engineering role, later presented with PE-level construction-management and inspection qualifications, then named in municipal records as key personnel, Lead Roadway Inspector and a corporate Secretary signatory for FALCON. The sequence matters because each label belongs to a defined documentary context. It is not a collection of self-promotional claims detached from a project or procurement process.
The strongest reading starts by separating four kinds of evidence. A professional association publication supplies an early role marker. A municipal proposal package supplies a resume-style qualifications record. One City of Corona agreement identifies a project-facing inspection and key-personnel function. Another Corona document records a corporate signature on a major construction-management amendment. Together, they show several surfaces of responsibility: field work, professional qualification, designated staffing and execution of a company agreement. None of those surfaces should be collapsed into another.
That distinction is central to understanding public works. A Lead Roadway Inspector may hold a highly consequential field role without owning the project or controlling every decision. A corporate Secretary may sign an agreement without personally performing every service listed in its scope. A resume included in a proposal may describe substantial experience while remaining a consultant's representation submitted for agency evaluation, rather than an independent finding about every project entry. An accurate profile preserves those differences instead of using one impressive document to make a larger claim than the record can carry.
The 2015 field-engineering marker
The earliest dated marker in this record appears in the November 2015 issue of AlMuhandes, a publication of the Arab American engineering and architecture association. In a Southern California section listing, Ahmad Faqih is identified as an EIT and Project Field Engineer at Falcon Engineering Services, Inc. The entry is brief, but it establishes three useful facts within that 2015 context: the name, the Engineer in Training designation and a project field engineering role tied to Falcon Engineering Services.
The phrase Project Field Engineer is important because it places the work close to construction execution rather than presenting only a general professional affiliation. Field engineering typically sits where plans, site conditions, contractor activity, measurements, records and questions have to be reconciled in real time. The publication does not provide a job description for Faqih, however, so the title should not be expanded into a list of personal duties. It shows how he was publicly described at that moment. It does not identify which project he was working on, what decisions he made or whether he held authority over other staff.
The EIT notation is equally bounded. It is evidence that the publication presented him with that professional designation in 2015. Later municipal records use PE after his name, producing a visible change in the documentary record. That change can be described as movement from an EIT-labeled field-engineering role to PE-labeled construction-management and inspection roles. It cannot be turned into a private account of how, why or exactly when he pursued licensure, because the available sources do not narrate that process.
This modest starting point also prevents a common biographical error. When later documents contain senior-sounding assignments, it is tempting to rewrite the earlier career as an inevitable path toward them. The 2015 entry supports no such claim. It simply provides a fixed professional-context snapshot. Its usefulness lies in being dated, specific and compatible with the later public-works record, not in supplying a complete origin story.
From EIT notation to PE-level inspection evidence
A City of Cypress construction-management and inspection submittal provides the next kind of evidence. The public proposal material includes a resume for Ahmad Faqih that presents him as a Construction Manager/Construction Inspector. It places PE after his name, gives California PE number C88068 and includes the notation QSD/P. It also lists FALCON project experience. Compared with the 2015 publication, the submittal situates him in a more developed professional and procurement context.
The progression is documentary before it is biographical. One source says EIT and Project Field Engineer. The later submittal says PE and Construction Manager/Construction Inspector. Those labels show that FALCON was presenting Faqih to a public agency for work involving construction management and inspection at a later point. The record supports that visible change. It does not, by itself, establish the date a license was issued, its current status, or an uninterrupted sequence of employment between every dated document.
The combined Construction Manager/Construction Inspector label is revealing because the two functions overlap without being identical. Construction management organizes the administration of a contract: schedules, communication, cost records, changes, submittals, meetings and closeout. Construction inspection concentrates on whether work observed in the field conforms to plans, specifications and applicable requirements, and on creating the daily record that allows issues to be evaluated later. A proposal that presents one person under both labels signals breadth in the staffing case FALCON offered.
It does not prove that Faqih personally performed every management and inspection task on every listed engagement.
The qualification identifiers serve a similar procurement purpose. A PE number gives an agency a concrete credential reference associated with the resume. The QSD/P notation adds another stated qualification marker. In a public proposal, such details help evaluators assess whether proposed staff match the technical and regulatory demands of the assignment. For this profile, they are best reported exactly as the submittal presents them. They should not be converted into a claim that the public document independently revalidated every credential for all time.
The resume's FALCON project entries also need careful treatment. Their presence shows the company relying on past project experience to support the proposed role. That is normal in qualifications-based procurement, where an agency often evaluates both the firm and named personnel. Yet a resume entry is not an award, performance audit or outcome study. It identifies experience represented in the submission. Without separate project records, it cannot establish that a named person was solely responsible for schedule, cost, quality, safety or completion.
This distinction makes the Cypress document more useful, not less. Read narrowly, it establishes that Faqih was not merely named somewhere in a corporate directory. He was included in public procurement material under construction-management and inspection headings, with professional identifiers and project entries intended to support FALCON's qualifications. That is auditable role evidence. It is stronger than an unsupported title copied across profile pages, while still stopping short of a personal success narrative.
Key personnel and the Lead Roadway Inspector role
One City of Corona agreement adds a more assignment-specific layer. The municipal record names FALCON, identifies Ahmad Faqih, PE, among key personnel and specifies him as Lead Roadway Inspector. It also identifies him as a Secretary signatory. These labels place him on both the delivery-facing and corporate-document sides of the agreement, but they do so through separate fields. The inspection role describes proposed or assigned project personnel. The Secretary label describes the capacity in which he signed for the consultant.
Key-personnel provisions matter because public agencies contract with firms while evaluating particular people. A construction-management company may have broad organizational qualifications, but the agency also needs to know who is expected to fill essential functions. Naming a person can make a staffing commitment visible and can limit casual substitution, depending on the agreement's terms. The designation therefore carries more evidentiary weight than a generic association with the company. It ties Faqih to a defined role inside a public contract record.
Lead Roadway Inspector is the narrowest technical title in the source set. It connects Faqih directly to roadway inspection rather than to construction management in the abstract. Roadway inspection is concerned with observed work and its conformity to the governing contract documents. The record does not provide a personal diary of his field activities, and it should not be paraphrased as proof that he inspected every operation. What it establishes is that the agreement names him for the lead inspection function within its personnel structure.
The word lead should also be handled with discipline. It indicates a leading role in the identified inspection function. It does not mean sole technical leadership of the entire project, authority over every consultant and contractor, or personal control of agency decisions. Public works involve a network of responsibilities: the city, its project manager, the construction contractor, designers, specialty consultants, laboratories, survey crews and inspectors may all hold distinct duties. A lead inspector occupies an important point in that network without replacing it.
Likewise, an inspection title is not an outcome certificate. It does not prove that the project met every cost, schedule, quality or safety objective. Inspection creates observation, verification and documentation within a contract system. Outcomes depend on many entities and may be evaluated through records not present here. The defensible statement is that Corona's agreement makes Faqih's roadway-inspection responsibility auditable at the personnel-designation level. It does not award him personal credit for the completed work.
The combination with the Cypress submittal is nonetheless meaningful. The proposal presents him broadly as Construction Manager/Construction Inspector, while the Corona agreement places him more specifically as Lead Roadway Inspector and key personnel. The documents reinforce a coherent professional domain: civil construction management and field inspection for public works. They do not need to be enlarged into an ownership story to show substantial responsibility.
The McKinley Street amendment and company-level responsibility
The second City of Corona source concerns the McKinley Street Grade Separation Project. It is a Second Amendment to a Professional Services Agreement between the city and Falcon Engineering Services, Inc. for construction management and inspection services. The document says the original agreement was dated April 7, 2021 and that a first amendment followed on December 28, 2021. The second amendment was executed in October 2024.
The amendment records a substantial continuing municipal engagement. It extends the agreement term through December 31, 2026, increases the authorized compensation by $2,933,461.04 to a not-to-exceed total of $13,428,081.84, and replaces the scope-of-services and compensation exhibits. Those figures describe the agreement between the City of Corona and FALCON. They are not Ahmad Faqih's compensation, revenue attributable to him, or proof of the contract's profitability.
The project description explains why the services are extensive. It concerns a new four-lane overhead grade separation carrying McKinley Street across BNSF Railway tracks near Sampson Avenue. The planned works include a network steel tied-arch bridge, connector roads, street reconstruction, ramp changes, utilities and related property interfaces. This is the kind of public project in which construction management is not a ceremonial layer. Multiple work fronts, external parties, technical disciplines, traffic and railroad interfaces create a continuing need for records, coordination and inspection.
The agreement assigns the consultant a broad institutional role. Acting as an agent of the city within the contract framework, the consultant is to provide construction management, inspection, administration, surveying coordination, monitoring, geotechnical and materials testing, public outreach and related services. The scope discusses project controls, progress reporting, subconsultant management, change orders, document systems, payment review, labor-compliance records, field inspection, testing and closeout. These are company obligations under the professional services agreement.
The signature page does not allocate all of them personally to Faqih.
That boundary is especially important because the amendment contains detail and large numbers. A reader could easily move from "Faqih signed" to "Faqih managed the entire project" or from "FALCON held the agreement" to "Faqih owned the contract." Neither move is supported. The contract is with the corporation. Its scope defines what the consultant must provide through an organization of personnel and subconsultants. The source identifies Faqih's corporate office for purposes of signature; it does not name him as the sole project manager for McKinley or assign every scope item to him.
The amendment does provide strong evidence of responsibility in a narrower sense. A public agency preserved his name and PE designation on the consultant's signature page and labeled him Secretary. That is an auditable corporate act tied to a specific amendment, defined services, a defined term and a defined compensation ceiling. It is more concrete than a generalized claim that he was associated with the company. At the same time, the act is contractual and representative, not proof of personal authorship of every technical decision.
What the construction-management scope actually contains
The McKinley document is useful because it shows the operational system behind the phrase construction management. The scope calls for project-control information that can track schedule, budget, expenditure and change orders. It calls for recurring progress reports and meetings so the city and other entities can review activity, issues and cost responsibility. It addresses coordination of subconsultants, with the city retaining approval rights in important places. The emphasis is on maintaining a usable record across a project that changes over time.
Change management is one example. The consultant is expected to log proposed changes, evaluate whether they have merit, prepare independent cost and schedule analysis, negotiate within the contract process and prepare change-order documentation for city approval. The scope also makes the boundary of authority visible: final project cost or time changes require approval from the city and, where applicable, Caltrans. This is a distributed control system, not a license for one consultant employee to decide every issue alone.
Payment review creates another evidence chain. The consultant reviews the contractor's progress and requests for payment, then prepares material for city approval. The city remains the public decision-maker in the process described. That distinction illustrates why a contract can impose serious review responsibility without transferring project ownership. The consultant tests and documents whether a request is supported; the agency preserves approval authority.
Document management is equally central. The scope refers to logging project records, organizing electronic and hard-copy files, tracking requests for information and preserving material for turnover to the city. Daily inspection reports are expected to capture contractor activities, staffing, equipment and relevant events. These records allow later decisions to rest on dated observations rather than memory. They also make the inspector's role consequential: field notes can connect what happened on site to payment, change, compliance and closeout processes.
The inspection provisions focus on continuous observation against the construction contract. Inspectors are to be experienced and qualified, and their documentation covers work progress and items relevant to compliance. Materials testing and quality-assurance services add laboratory and field evidence about acceptability. Surveying supports construction in conformance with contract documents. Each discipline contributes a different type of verification; none alone proves the performance of the whole project.
The scope also includes limits. It distinguishes the consultant's role from that of the construction contractor and reserves decisions or approvals to the city in multiple contexts. It notes particular assumptions and identifies where the consultant is not responsible for every enforcement act or every worker identification. Those limits are not fine print to be ignored. They define the allocation of risk and authority that makes a public contract intelligible.
For a profile of Faqih, the operational detail should be used as context, not reassigned as personal accomplishment. It explains the kind of system in which FALCON's personnel and signatories appear. The Lead Roadway Inspector role belongs to an inspection structure that depends on daily records and contract conformity. The Secretary signature belongs to a corporate agreement that organizes management, testing, surveying, reporting and approvals. The document does not say Faqih personally carried out each element, so neither should the profile.
Inspection is an evidence function
Public-works inspection is sometimes reduced to watching construction. The contract record shows a more exact function. Observation has to be translated into a form that other entities can use: a daily report, measurement, test result, photograph, issue log, request, rejection or recommendation. The value of inspection lies not only in noticing a condition but in connecting it to the plans, specifications and administrative process that govern what happens next.
That is why the title Lead Roadway Inspector is meaningful even without a personal achievement claim. Roadway work unfolds through sequences that can become inaccessible after the next layer is placed. Materials arrive, grades are established, concrete is poured, utilities are relocated and traffic arrangements change. An inspection system creates contemporaneous evidence about whether observed work matches the contract requirements. The available Corona agreement identifies Faqih at the lead level of that function; it does not supply enough information to judge his individual performance within it.
Inspection also operates beside, not above, other professional roles. A designer answers design questions. A contractor controls its means and methods within contract requirements. A testing laboratory produces material results. Surveyors establish locations and elevations. The city makes reserved approvals. Construction-management staff coordinate records and decisions across these interfaces. A lead inspector can help make field evidence coherent, but the title does not erase the authority or responsibility of those other entities.
This structure clarifies the difference between responsibility and credit. Responsibility can be documented prospectively: the agreement names a person or firm for a role. Credit for an outcome requires retrospective evidence connecting actions to a result. The sources here provide the first kind much more strongly than the second. They show who was presented, designated or authorized. They do not provide a final performance evaluation, an audit of outcomes or a causal account of who produced them.
The difference protects both the subject and the public record. Inflating a role into sole authorship can misstate the contributions of an entire project team. Assigning an outcome without evidence can also make one person appear responsible for events outside that role's control. A precise profile instead recognizes the significance of being named in a municipal personnel and contract system while refusing to manufacture a performance judgment the documents do not contain.
A Secretary signature is not an ownership claim
The McKinley amendment's consultant signature page identifies Ahmad Faqih, PE, as Secretary of Falcon Engineering Services, Inc. A second Corona agreement uses the same Secretary capacity while also naming him in the project personnel structure. This repetition supports the statement that public city records placed him in a corporate signature role for FALCON. It does not support the statement that he owned the corporation.
Corporate titles and ownership interests answer different questions. A Secretary may execute or attest documents for a corporation under its governance and authorization arrangements. A shareholder or owner holds an economic or legal interest. The presence of one title on a signature page does not prove the other. No ownership record in the sources establishes Faqih as a founder, shareholder or controlling person, so those labels remain outside this profile.
The signature also should not be treated as proof of personal project ownership. The agreement names the City of Corona and Falcon Engineering Services as the parties. The city purchases professional services from the consultant corporation. Faqih signs in a stated representative capacity. The obligations remain the corporation's obligations, to be performed through the organization and personnel required by the agreement. His signature is significant because it connects him to the company's formal acceptance of the amendment, not because it transfers every contractual task to him individually.
Nor does the Secretary title automatically establish final technical authority. The PE designation shows how the document styles his professional name, but the signature block is a corporate execution block. Technical decisions on a public project may involve named managers, engineers, inspectors, designers, city representatives and other authorized professionals. The source does not map that full chain to Faqih. It is therefore accurate to describe contract-signature responsibility and inaccurate to call him the sole technical leader of the McKinley project.
This is a useful example of why exact nouns and verbs matter. The record "identifies" Faqih as Secretary. He "signs" for the consultant. Another record "names" him as key personnel and Lead Roadway Inspector. The Cypress submittal "presents" him as a Construction Manager/Construction Inspector. These verbs preserve the source type. Replacing all of them with "owned," "ran," "delivered" or "succeeded" would remove the distinctions that make the evidence auditable.
An evidence ladder, not a single sweeping biography
The four sources form an evidence ladder. At its base, the 2015 professional publication provides a dated affiliation and role label. It is concise and useful for context, but it does not describe projects or performance. The Cypress procurement submittal adds a qualifications record with professional identifiers, role descriptions and FALCON project entries. It offers more detail, though that detail is presented by a bidding or proposing team for evaluation.
The first Corona agreement adds agency-held contract evidence. By naming Faqih as key personnel and Lead Roadway Inspector, it places his role inside a municipal agreement rather than only inside a professional listing or proposal resume. It also records his Secretary signature. The McKinley amendment then supplies a second agency-held example of the corporate signature function, tied to a defined construction-management and inspection agreement.
No single source has to do all the work. The association publication should not be asked to prove a later PE-level role. The proposal should not be asked to prove that every resume entry produced a successful outcome. The key-personnel agreement should not be asked to prove company ownership. The McKinley signature page should not be asked to prove that Faqih personally managed every aspect of that project. Each source is strongest when used for the purpose reflected in its form.
The dates provide a restrained chronology. In 2015, Faqih is publicly listed as an EIT and Project Field Engineer at Falcon Engineering Services. By the time of the Cypress submittal, the public procurement record presents him as a PE-level Construction Manager/Construction Inspector with credential notations and FALCON project experience. Corona's records then show project-specific key-personnel and lead-roadway-inspection evidence as well as repeated Secretary signatures. The 2024 McKinley amendment is the latest dated event in this source set, but it does not establish a current role beyond the document's own context.
This ladder is stronger than a profile assembled from an undated biography because it exposes how each claim can be checked. A reader can see whether a statement comes from a professional publication, consultant proposal, municipal agreement or signed amendment. The method also makes uncertainty visible. When no source establishes an outcome, ownership interest or complete career history, the article can say so rather than fill the space with inference.
Auditable evidence is not the same as exhaustive evidence. These documents illuminate the parts of a professional life that intersected with public procurement. They do not reveal private biography, personal goals, internal compensation, complete employment dates or every project. Their silence should remain silence. A narrow profile is credible precisely because it does not pretend that a few public contracts disclose the whole person.
How to read a municipal staffing record
A municipal staffing record usually answers a prospective question: who is the consultant offering or committing to place in a defined role? It is not necessarily a retrospective account of who performed every hour of work. The Cypress submittal presents Faqih's qualifications so an agency can evaluate FALCON's proposed team. The Corona key-personnel record goes further by placing his name and Lead Roadway Inspector title inside an agreement. Both are strong evidence of role presentation and designation, but neither substitutes for daily staffing records or a completed-project audit.
This prospective character explains why names matter in procurement. An agency evaluating construction-management services is not buying an abstract corporate name alone. It considers the people associated with project controls, inspection, testing, administration and other functions. A named role gives the agency a point of accountability within the consultant organization. It can also make later staffing changes visible under the contract's procedures. The available documents do not show whether any substitution occurred, so the profile should not claim uninterrupted service for a period the records do not fully cover.
A signature page answers a different question: who executed the document in a stated capacity for the party? On the McKinley amendment, the party is FALCON and Faqih is identified as Secretary. That evidence is formal, but its form is corporate rather than biographical. It confirms the capacity recorded for the transaction. It does not disclose the internal authorization process, equity structure or allocation of technical duties that sat behind the signature.
Reading the records together creates a more reliable map than treating any one label as a complete title. The 2015 listing supplies professional context. The Cypress resume supplies represented qualifications. The Corona personnel provision supplies a contract-facing inspection designation. The Corona signature pages supply corporate execution evidence. Agreement among those records supports a continuing association with FALCON's civil construction-management work, while the differences among them prevent an unsupported leap from association to ownership or from designation to personal outcome credit.
What the documents do not permit
The records do not support company ownership. FALCON appears as the consultant and corporate entity; Faqih appears under professional, personnel and Secretary labels. None of the four sources presented here is an ownership filing. It would therefore be wrong to call him FALCON's owner or to imply that the company's contracts were his personal contracts.
They do not support project ownership either. Public projects are undertaken by agencies through agreements with contractors and consultants. The McKinley amendment describes the city-consultant relationship and a broad scope of services. A corporate signature does not make the signatory the owner of the public asset, the construction contract or the professional services engagement. A key-personnel designation likewise identifies staffing responsibility rather than property or contractual ownership.
The documents do not support sole technical leadership. Faqih is named Lead Roadway Inspector in one Corona record, a meaningful technical role within inspection. The McKinley amendment, however, does not identify him as sole project manager or sole engineer. Its scope depends on many disciplines and preserves authority for the city and other entities. The evidence cannot be rearranged to make one role govern every part of the work.
The sources also do not establish market success, company profitability, customer satisfaction, safety results or project performance. A compensation ceiling shows the authorized size of an agreement, not profit. An extended term shows an amended contract period, not a performance score. A project description shows complexity, not successful delivery. An inspector title shows role assignment, not a guarantee of construction outcomes.
No personal motive can be recovered from these procurement pages. They do not say why Faqih chose civil engineering, what he thought about a project or how he evaluated his own career. They do not provide a private biography. Adding such material would make the story more conventional but less accurate. Observable role markers are enough to establish the profile's point.
Current-role claims require the same restraint. The 2024 amendment records a signature at that time and sets an agreement term into 2026. It does not prove what title Faqih holds today, whether he remains in every role named in older material, or how FALCON currently organizes its staff. Contract dates are not a substitute for a current employment confirmation.
Why the narrow record matters
This public record matters because construction management is often visible only through institutions rather than publicity. The work is documented in schedules, logs, inspection reports, payment reviews, change records and signed agreements. Professionals can carry substantial responsibility inside those systems without appearing in project announcements. By tracing exact role fields, it is possible to describe that responsibility without inventing fame or ownership.
Faqih's record also shows how professional responsibility can appear on more than one plane. The 2015 field-engineering label is close to project execution. The Cypress submittal presents management and inspection qualifications. The Corona key-personnel designation places him within an agency contract's staffing structure. The Secretary signature records corporate participation in executing agreements. The planes are related, but each answers a different question.
For public agencies, those distinctions are practical. They help identify who has been proposed for essential work, what qualifications are represented, which firm is legally obligated and who executed the document for that firm. For readers, they provide a model for evaluating claims about people in infrastructure. The most reliable account may be a chain of modest statements that can each be tied to a public record.
The chain here supports a clear conclusion. Ahmad Faqih has an auditable public-works footprint associated with FALCON that moves from project field engineering into PE-labeled construction management and inspection, includes a Lead Roadway Inspector and key-personnel designation, and reaches formal corporate signature responsibility on City of Corona agreements. That is substantial evidence of role and responsibility. It remains evidence of role and responsibility, not proof of ownership or personal credit for collective outcomes.
Responsibility without unsupported credit
The most accurate profile of Ahmad Faqih is therefore not a founder story, a company history or a victory narrative about a single project. It is an account of how a civil construction-management professional becomes visible in public documents. The progression from EIT and Project Field Engineer to PE-labeled inspection and key-personnel roles is observable. The Secretary signatures are observable. The contracts' company-level scope is observable. Personal motives, ownership interests and individual outcome claims are not.
That boundary does not diminish the work. Public-works inspection and construction management depend on people who can operate inside formal systems of evidence. A named lead inspector sits where plans and field conditions meet. A qualifications resume places professional experience before an agency. A corporate signatory helps execute the agreement under which an organization performs. Each function is consequential on its own terms.
The documents ultimately offer a disciplined way to assign recognition. They support recognizing Faqih as a FALCON civil and construction-management professional with documented inspection, key-personnel and contract-signature roles. They do not support assigning him every success, decision or obligation attached to the projects and company. In infrastructure reporting, that distinction is not a disclaimer added after the story. It is the foundation of an account that can be checked.