Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Engineer Misstating Professional Achievements on Resume
Step 4 of 5

135

Entities

1

Provisions

2

Precedents

12

Questions

15

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A remains 'trapped' in the ethical rule-set of honest attribution: the Board frames the obligation as a threshold constraint (C15) that cannot be discharged, transferred, or escaped through claims of ambiguity, seniority, or competitive necessity, leaving the engineer perpetually bound by the same unresolved rule structure rather than moving to a new scenario or new responsible party.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (1)
View Extraction

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

II.5.a board + analysis Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments.
How this applies in the case (showing 3 of 22)
Obligation
Engineer A Team Credit Duty
This provision requires engineers not to misrepresent or exaggerate their responsibility for prior assignments such as jointly designed patented products.
Action
Resume Submission
This provision directly prohibits falsifying qualifications or exaggerating responsibility on resumes
State
Resume Sole Credit Misattribution
This directly involves misrepresenting responsibility for prior assignments completed with others.
Obligation (1)
  • Engineer A Team Credit Duty
    This provision requires engineers not to misrepresent or exaggerate their responsibility for prior assignments such as jointly designed patented products.
Action (3)
  • Resume Submission
    This provision directly prohibits falsifying qualifications or exaggerating responsibility on resumes
  • Team Credit Omission
    Omitting team credit misrepresents the engineers individual responsibility for prior work
  • Team Design Participation
    The provision governs how actual participation in a team project must be accurately represented
State (5)
  • Resume Sole Credit Misattribution
    This directly involves misrepresenting responsibility for prior assignments completed with others.
  • Engineer A Candidacy with Employer Y
    The false resume was used to solicit employment covered by this provision.
  • Engineer A Deceptive Resume Intent
    Falsifying qualifications with intent to deceive is exactly what this provision prohibits.
  • Team Credit for Patented Products
    Claiming sole credit for team-developed patented products misrepresents responsibility for prior work.
  • Employer Competence Deception Exposure
    Misrepresented qualifications expose the employer to deception about the engineer's true competence.
Constraint (2)
  • Engineer A Resume Responsibility Misrepresentation
    This provision directly prohibits engineers from misrepresenting or exaggerating their responsibility for prior work as stated in this constraint.
  • Engineer A Sole Credit Implication Prohibition
    This provision prohibits misrepresentation of qualifications which includes falsely implying sole credit for jointly developed products.
Principle (2)
  • Honesty in Resume Credit Claims
    This provision prohibits misrepresenting responsibility for prior work which directly matches this principle
  • Honesty in Resume Representations
    The provision explicitly bars falsifying qualifications and misrepresenting past accomplishments in resumes
Role (1)
  • Engineer A Staff Engineer
    Engineer A misrepresented sole responsibility for team-designed products on his resume to a prospective employer.
Event (1)
  • Patent Issuance
    Misstating patent issuance status constitutes falsifying professional qualifications
Resource (3)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code addressing misrepresentation of qualifications
  • BER Case 72-11
    This provision governs the permissible limits of emphasizing managerial experience in a resume
  • BER Case 79-5
    This provision prohibits falsifying qualifications such as citing a diploma mill Ph.D.
Capability (4)
  • Engineer A Representation Accuracy
    This provision directly requires Engineer A to accurately represent his role and not exaggerate responsibility for the patented designs.
  • Engineer A Product Design
    The provision governs how Engineer A may describe his actual design contributions and credentials related to the patented products.
  • Five Other Staff Engineers Product Design
    The provision requires that credit for the design work be accurately shared with the five other engineers who jointly created the patented products.
  • Board Code Interpretation
    The Board directly interprets and applies the misrepresentation language of this provision to the facts of the case.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

Under the older, narrower Code provision 3(e), an engineer could ethically emphasize or de-emphasize truthful aspects of experience on a resume, as this constituted permissible 'emphasis' rather than prohibited 'exaggeration,' since he could truthfully show some degree of competence in the areas emphasized.

Citation Context:

The Board cited this case as a prior fact situation involving resume emphasis, using it initially as a lenient standard (permitting emphasis short of exaggeration), but ultimately distinguished it because the Code language has since been broadened.

Relevant Excerpts
discussion: "In Case 72-11, John Doe, who had been employed as a design engineer in an aerospace company for twelve years... devised a new resume which played down his technical design experience..."
discussion: "In concluding that Doe was not in violation of the Code for rewriting his employment resume in this manner, we were inclined to the more charitable view that Doe's action can be condoned as something less than an 'exaggeration'..."
discussion: "In Case 72-11, we found that Doe could truthfully show some degree of competence in the managerial and administrative technical areas of the employment even though Doe strongly emphasized its extent and level."

Principle Established:

Under the broader Code language prohibiting misleading, deceptive, or false statements regarding professional qualifications, an engineer acts unethically by citing a credential (such as a degree from an unaccredited 'diploma mill') in a way that misrepresents its nature or value.

Citation Context:

The Board cited this case as supporting authority showing that under the expanded Code language prohibiting 'misleading, deceptive or false statements,' misrepresenting qualifications (such as citing a degree from a diploma mill without explanation) is unethical, reflecting a stricter standard than Case 72-11.

Relevant Excerpts
discussion: "In contrast, Case 79-5 involved an engineer who received a Bachelor of Science degree in 1940... In 1960 he received a Ph.D. degree from an organization... regarded by state authorities as a 'diploma mill.'"
discussion: "In concluding that the engineer was unethical in citing his Ph.D. as an academic qualification under these circumstances, we noted that the earlier Case 72-11 had been decided under old Code provision 3(e)..."
discussion: "We therefore held that the newer and broader Code language should be interpreted to prohibit the engineer from citing his Ph.D. degree as an academic credential."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 60% Facts Similarity 69% Discussion Similarity 34% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 56% Facts Similarity 50% Discussion Similarity 29% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 25%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 59% Facts Similarity 56% Discussion Similarity 16% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 14%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 59% Discussion Similarity 32% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 12%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 48% Facts Similarity 51% Discussion Similarity 39% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 20%
Shared provisions: II.5.a Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 40% Discussion Similarity 21% Outcome Alignment 100% Tag Overlap 17%
Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 45% Discussion Similarity 39% Outcome Alignment 100% Tag Overlap 20%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 55% Discussion Similarity 30% Outcome Alignment 100% Tag Overlap 25%
Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 53% Discussion Similarity 41% Outcome Alignment 100% Tag Overlap 14%
Same outcome unethical View Synthesis
Component Similarity 51% Facts Similarity 31% Discussion Similarity 34% Outcome Alignment 100% Tag Overlap 25%
Same outcome unethical View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Was it ethical for Engineer A to imply on his resume that he was personally responsible for the design of the products which were actually designed through the joint efforts of the members of the design team?

Board conclusion It was unethical for Engineer A to imply on his resume that he was personally responsible for the design of the products which were actually designed through the joint efforts of the members of the design team.
Resolved by: The board weighed Engineer A's interest in favorable self-presentation against the team's collective entitlement to credit and found the latter controlling because the resume language misstated a factual matter of authorship. (confidence 0.90)
II.5.a. 2 principles 3 facts Conditions Narrative
Implicit (4)

Where is the line between legitimately emphasizing one's own contributions to a team project and unethically implying sole responsibility, and how specific must resume language be to fairly represent a team member's role?

AnalyticalThe Board's conclusion can be extended by distinguishing between resume puffery that emphasizes an engineer's role within a permissible range (as in BER Case 72-11, where emphasizing managerial experience was allowed) and affirmative misattribution of sole design responsibility. The line the Board implicitly draws is between describing one's own contributions to a joint effort in first-person active terms ('I contributed to the design of...') versus language that displaces the credit due to identifiable co-inventors on a patented product ('I designed...'). The existence of formal patent inventorship records makes this case distinguishable from 72-11 because there is an objective, verifiable standard of credit allocation that Engineer A contradicted.
Resolved by: The board balanced permissible self-promotion against accuracy obligations by anchoring the line to whether an objective, verifiable record (patent inventorship) was contradicted, rather than to the mere degree of emphasis used. (confidence 0.70)
II.5.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe Board's finding implies a structural standard: because Engineer A held equal rank with five other staff engineers on a joint design team, no individual member could ethically claim personal or primary credit absent some documented differentiation of roles (such as a formally designated lead engineer or distinct sub-task ownership). This suggests the ethical violation was not merely a matter of degree in language choice but was effectively unavoidable misrepresentation given the flat team structure, regardless of Engineer A's subjective intent.
Resolved by: The board treated the absence of any documented role differentiation as foreclosing any legitimate basis for individual credit claims, effectively subordinating Engineer A's subjective intent to the objective team structure. (confidence 0.75)
II.5.a. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, the line between legitimate emphasis and unethical misrepresentation turns on whether the resume language accurately conveys the collaborative nature of the work. Legitimate emphasis would describe an engineer's specific role, contributions, or expertise within a team effort (e.g., 'contributed to the design of' or 'served as part of a team that designed'), whereas language implying sole or personal responsibility for a jointly created product crosses into misrepresentation, regardless of how substantial that individual's actual contribution may have been, because it fails to fairly represent the credit due to all team members.
Resolved by: The board resolved the tension between self-promotion and due credit by making accuracy of characterization, not magnitude of contribution, the deciding factor. (confidence 0.80)
II.5.a. 2 principles 3 facts Conditions Narrative

Does Employer Y bear any responsibility to verify claims of individual design credit before relying on them in hiring decisions, given the competitive employment environment that may incentivize resume embellishment?

AnalyticalThe Board's conclusion focuses solely on Engineer A's ethical failure, but a fuller analysis would note that Employer Y's reliance on unverified resume claims exposes a systemic vulnerability in professional hiring processes. While this does not excuse Engineer A's misrepresentation, it suggests that the profession's ethical framework places the entire burden of honesty on the individual engineer rather than creating any complementary duty of diligence on the hiring employer, even though patent records could have provided an objective means of verification.
Resolved by: The board placed the full weight of the honesty obligation on Engineer A and did not recognize any competing or complementary diligence obligation on Employer Y, even though verification was feasible. (confidence 0.65)
II.5.a. 2 principles 3 facts Conditions Narrative

What obligations, if any, do the five other staff engineers or Employer X have to correct the record if they become aware that Engineer A misrepresented sole credit for jointly designed patented products?

Does the fact that the products were patented (implying formal, named inventorship records) create an objective standard against which Engineer A's resume claims could and should have been checked?

AnalyticalRegarding Q104, the existence of formal patent records naming all six staff engineers as co-inventors creates an objective, verifiable standard against which Engineer A's resume claims can be measured. This documentary record makes his misrepresentation more clearly demonstrable and egregious than a case involving purely subjective or undocumented team dynamics, since the patents themselves constitute independent evidence contradicting his implied sole authorship.
Resolved by: The board treats the existence of an objective documentary record as tipping the balance decisively against any claim of ambiguity in Engineer A's favor, since verifiability removes room for a benign or subjective interpretation of his language. (confidence 0.85)
II.5.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C102
Principle tension (2)

How should the principle of Honesty in Resume Credit Claims be balanced against an engineer's legitimate interest in presenting himself competitively for employment, especially when prior Board precedent (BER Case 72-11) permits emphasizing certain experience on a resume?

AnalyticalRegarding Q201, BER Case 72-11's allowance for emphasizing certain experience does not create tension with the Honesty principle here, because that precedent permits engineers to highlight genuine aspects of their role or contribution, not to claim personal credit for work product that was formally and legally attributed to a group. The competitive employment environment may explain the motivation for embellishment, but it does not excuse a factual misstatement about the nature of the design work performed.
Resolved by: The board distinguishes permissible emphasis of one's real role from impermissible claiming of exclusive credit for jointly owned work, finding no genuine tension between competitive self-presentation and honesty once this distinction is drawn. (confidence 0.85)
II.5.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe Board resolved the tension between Honesty in Resume Credit Claims and an engineer's legitimate interest in self-promotion by drawing a bright line between emphasis and misrepresentation: BER Case 72-11 permits engineers to highlight their own role or contributions within a legitimate scope of truthful description, but this liberty does not extend to affirmatively implying sole authorship of work product that was, in fact, collaborative. Competitive pressure to stand out in the job market does not create an exception to the duty of honest self-representation under Section II.5.a.
Resolved by: The Board balanced the engineer's interest in self-promotion against the duty of honesty by permitting emphasis but disallowing affirmative implication of sole authorship, refusing to let competitive pressure expand the permitted scope. (confidence 0.85)
II.5.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C102 C303

Does Due Credit for Team Design conflict with Honesty in Resume Representations when an individual engineer's contribution within a team of equals is difficult to distinguish, making any individualized claim potentially misleading regardless of intent?

AnalyticalRegarding Q202, the difficulty of distinguishing individual contributions within a team of equals does not create a genuine conflict between Due Credit for Team Design and Honesty in Resume Representations; rather, it reinforces the need for honesty. Where individual contributions cannot be clearly separated from the group effort, the ethical resolution is to describe the work as a team accomplishment rather than to default to an individualized claim that cannot be substantiated.
Resolved by: Rather than treating indistinguishable individual contribution as grounds for permitting an individualized claim, the board resolves the apparent tension by requiring that unresolvable ambiguity default to a team-attributed description. (confidence 0.80)
II.5.a. 2 principles 3 facts Conditions Narrative
AnalyticalRather than being in true conflict, Due Credit for Team Design and Honesty in Resume Representations were treated by the Board as mutually reinforcing rather than competing principles: because the team's contributions were formally documented through joint patent credit, honestly representing one's role necessarily required acknowledging the team, and any claim to sole credit was ipso facto both a violation of due credit and an act of dishonesty. This suggests that in cases of clearly documented joint work, the two principles collapse into a single unified obligation rather than requiring separate balancing.
Resolved by: Rather than balancing competing duties, the Board found the two principles collapsed into one because honestly describing joint-patented work required crediting the team, making any sole-credit claim simultaneously dishonest and a due-credit violation. (confidence 0.80)
II.5.a. 2 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill his duty to give due credit to the other members of the design team when drafting his resume?

AnalyticalRegarding Q301, from a deontological perspective Engineer A failed his duty to give due credit to his fellow team members. The duty of honest attribution is not conditional on competitive advantage or the difficulty of parsing individual contributions; it is a categorical obligation under the profession's ethical code, and Engineer A's resume language violated that duty regardless of his intent or the practical benefits he sought.
Resolved by: From a deontological standpoint the board subordinates consequentialist considerations of competitive benefit entirely to the categorical duty of due credit, treating intent and practical advantage as irrelevant to the violation. (confidence 0.80)
II.5.a. 2 principles 3 facts Conditions Narrative

Did the consequences of Engineer A's resume misrepresentation—namely, gaining an advantage in a competitive employment environment while deceiving Employer Y about actual design competence—justify the misattribution of sole credit?

AnalyticalThe case establishes a prioritization hierarchy in which Honesty in Resume Credit Claims functions as a threshold constraint that cannot be overridden by competitive employment considerations, professional ambition, or the practical difficulty of parsing individual contributions within an equal-status team. Even where, as here, distinguishing one engineer's contribution from five equally-ranked peers may be genuinely difficult, the Board's ruling implies the default and safer ethical position is to describe work as a team achievement rather than risk a misleading individual claim.
Resolved by: The Board subordinated competitive and ambition-based interests to the threshold honesty constraint, holding that difficulty in parsing individual contributions favors defaulting to team-credit language rather than risking misleading individual claims. (confidence 0.78)
II.5.a. 2 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity, as expected of a virtuous engineer, when he implied sole personal responsibility for products that were the result of collaborative work with five other staff engineers?

AnalyticalRegarding Q303, Engineer A did not act with the professional integrity expected of a virtuous engineer. A virtuous professional would recognize that claiming individual credit for collaborative, patented work misrepresents both his own competence and the contributions of colleagues, and would instead choose resume language that accurately reflects a shared achievement, prioritizing truthful self-representation over competitive self-interest.
Resolved by: The board applies a virtue-based standard in which truthful self-representation is weighed as categorically more important than the competitive self-interest that motivated the embellishment, finding the latter insufficient to justify the former's absence. (confidence 0.80)
II.5.a. 2 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer A had held a distinctly senior or lead role on the design team rather than being one of six staff engineers of equal rank, would the Board still have concluded that implying sole responsibility on his resume was unethical?

AnalyticalRegarding Q401, if Engineer A had held a distinctly senior or lead design role, the Board's analysis would likely differ: a lead engineer might legitimately claim primary responsibility for design decisions while still owing acknowledgment to supporting team members. However, since Engineer A was explicitly one of six staff engineers of equal rank with no supervisory distinction, there is no factual basis to claim personal responsibility, making the misrepresentation more clear-cut than it might be in a hierarchical team structure.
Resolved by: The Board weighed personal claim-to-credit against the factual absence of any hierarchical basis for such a claim, finding no legitimate ground for Engineer A to assert primary responsibility. (confidence 0.82)
II.5.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101

If the products in question had not been jointly designed and patented by the full team but had instead been solely attributed to Engineer A by Employer X's own records, would the Board still find his resume claim to be a misrepresentation?

AnalyticalRegarding Q402, if Employer X's own records had solely attributed the designs to Engineer A rather than crediting the full team via joint patents, the Board would likely have reached a different conclusion, since the resume claim would then accurately reflect the documented allocation of credit. The ethical violation in this case stems specifically from the discrepancy between the objective patent record showing joint inventorship and Engineer A's resume language implying sole credit.
Resolved by: The Board treated the objective patent record as the benchmark against which the resume's honesty was measured, finding the violation in the mismatch between record and claim rather than in self-promotion itself. (confidence 0.83)
II.5.a. 2 principles 3 facts Conditions Narrative
Decisions & Arguments (4)
View Extraction

Should Engineer A describe the patented product designs as a team achievement on his resume, or word his resume so as to imply that he was personally or primarily responsible for the design?

Options considered:
O1 State on the resume that the patented products were designed by a team, without necessarily naming all five other engineers, accurately conveying joint responsibility. Board's choice
O2 Word the resume so that it implies Engineer A alone was responsible for designing the patented products, omitting any reference to the team.
O3 Describe Engineer A's specific contributions and expertise while explicitly acknowledging that the products resulted from a team effort, following the BER 72-11 model of permissible emphasis.
Argument structure (Toulmin):
Grounds

The products were designed jointly by a six member design team at Employer X and issued as patents; Engineer A submitted a resume to Employer Y that omitted mention of the team and implied personal responsibility for the designs.

Warrant

Engineers must give credit for engineering work to those to whom credit is due (III.10.a); engineers must not misrepresent facts concerning their qualifications or the work for which they were responsible (II.5.a).

Rebuttal

Would not apply if Engineer A held a distinctly senior or lead design role with documented individual accountability, or if industry convention treated such phrasing as ordinary self-promotion rather than a deliberate false claim of sole credit.

Engineer A Team Credit Duty Engineer A Resume Responsibility Misrepresentation

Should Employer Y independently verify Engineer A's claimed design credit against patent records before relying on it in hiring, or accept the resume claim at face value?

Options considered:
O1 Accept Engineer A's resume claims at face value without independently checking patent or employment records, consistent with the Code's current placement of the honesty burden solely on the engineer. Board's choice
O2 Cross check Engineer A's claimed design credit against the publicly available issued patents listing all six co-inventors before finalizing a hiring decision.
O3 Contact Employer X or the design team's supervisor to confirm the scope of Engineer A's individual role before relying on the resume claim.
Argument structure (Toulmin):
Grounds

Employer Y received a resume from Engineer A implying personal design credit; the products in question were patented with all six team members listed as co-inventors in publicly accessible records.

Warrant

The NSPE Code's misrepresentation and due credit provisions (II.5.a, III.10.a) impose obligations only on the engineer submitting the resume, not on the hiring employer's verification practices.

Rebuttal

This absence of formal duty would not excuse an employer that ignores readily available and dispositive documentation, such as issued patents, when verification is feasible and low cost, particularly given the competitive environment that incentivizes resume embellishment.

Should the five other staff engineers or Employer X take corrective action upon learning of Engineer A's misrepresentation, or take no action absent direct knowledge or a formal complaint?

Options considered:
O1 Refrain from any corrective action unless and until the other engineers or Employer X gain direct, verified knowledge of the specific misrepresentation on Engineer A's resume. Board's choice
O2 Upon learning of the misrepresentation, formally notify Employer Y or the relevant licensing board to correct the record regarding true design credit.
O3 Address the misrepresentation directly and informally with Engineer A, seeking a correction before involving any external party.
Argument structure (Toulmin):
Grounds

Engineer A's resume to Employer Y implied sole personal responsibility for products that patent records show were jointly designed by six named co-inventors at Employer X.

Warrant

Engineers must give credit for engineering work to those to whom credit is due (III.10.a), which implies a shared interest among team members in accurate attribution of joint work.

Rebuttal

Would not apply if the other engineers or Employer X lack direct knowledge of the resume's content, have no formal channel for raising the issue, or reasonably believe the matter is outside their professional responsibility absent a complaint.

Due Credit for Team Design

If Engineer A had held a senior or lead design role, or if Employer X's own records had solely attributed the designs to him rather than crediting the full patent team, could he then legitimately claim primary or sole credit on his resume?

Options considered:
O1 In the absence of any formal record distinguishing Engineer A's role from the other five engineers, describe the design work as a joint team achievement. Board's choice
O2 If company or patent records formally designated Engineer A as lead engineer or principal designer, claim primary responsibility while still acknowledging supporting team members.
O3 If Employer X's internal records solely attributed the design to Engineer A notwithstanding joint patent listing, rely on those internal records to claim sole credit on the resume.
Argument structure (Toulmin):
Grounds

Engineer A was one of six staff engineers of equal rank; the patents named all six as co-inventors, and no company record designated Engineer A as lead or sole designer.

Warrant

Engineers must give due credit according to the actual, documented allocation of responsibility for the work (III.10.a), and must not misrepresent that allocation on a resume (II.5.a).

Rebuttal

Would not apply if Engineer A's actual role carried supervisory authority or final design accountability, or if Employer X's own records had in fact attributed the design solely to him, since in either case there would be a documented basis distinguishing his contribution from the team's.

Engineer A Team Credit Duty Engineer A Resume Responsibility Misrepresentation
Event Timeline (8)
8 sequenced 4 actions 4 events
Case timeline
Between Case 72-11 and Case 79-5, the Code provision was expanded from prohibiting merely exaggerated statements of qualifications to embracing misleading, deceptive, or false statements regarding professional qualifications.
Engineer A, as one of six equal-rank staff engineers at Employer X, participated in and was credited with the joint design of a series of patented products.
Fulfills (1)
  • Obligation to Perform Assigned Design Work
Causal-normative reasoning(confidence 0.75)
Team Design Participation fulfills the Obligation to Perform Assigned Design Work and legitimately causes the Patent Issuance shared among the team, which makes the later individual claiming of credit in the Resume Submission ethically problematic precisely because the design achievement was a collective, obligation-fulfilling effort rather than solely Engineer A's own.
State changes (1)
  • began: Team Credit for Patented Products
A series of products jointly designed by the six-member team at Employer X became patented, with all six engineers including Engineer A credited for the design.
State changes (1)
  • began: Team Credit for Patented Products
Since the decision in Case 79-5, the NSPE Code of Ethics was again modified, with new Section II.5.a further restricting the representations engineers may make in resumes, brochures, and correspondence.
State changes (1)
  • began: Section II.5.a In Force
Engineer A failed to express on his resume that the design work was performed as a team effort, omitting due credit to the five other staff engineers who worked with him.
At stake (1)
  • Obligation to Give Due Credit to Others (Section III.10.a)
Causal-normative reasoning(confidence 0.65)
Team Credit Omission, though not separately marked as fulfilling or violating an obligation, is the direct behavioral consequence of the Resume Submission's misrepresentation and due-credit violations, illustrating how the initial ethical breach concretely manifests as the erasure of colleagues' contributions.
Engineer A submitted a resume to Employer Y implying he was personally responsible for the design of products that were actually designed through a joint team effort.
Violates (2)
  • Obligation Not to Misrepresent Professional Qualifications (Section II.5.a)
  • Obligation to Give Due Credit to Others (Section III.10.a)
Causal-normative reasoning(confidence 0.80)
Resume Submission violates the Obligation Not to Misrepresent Professional Qualifications and the Obligation to Give Due Credit to Others because it takes the collectively produced design work from Team Design Participation and misrepresents it as an individual accomplishment, a violation whose downstream effects include the Team Credit Omission and the triggering of the Code Interpretation Ruling that formally condemns this conduct.
State changes (2)
  • began: Employer Competence Deception Exposure
  • began: Resume Sole Credit Misattribution
The Board interpreted Section II.5.a's term 'misrepresentation' to include intentional implications that obscure truth, finding Engineer A's resume conduct prohibited and also finding a violation of Section III.10.a for failing to credit the team.
Causal-normative reasoning(confidence 0.60)
A1 is the downstream ruling triggered by Engineer A's Resume Submission and shaped by prior Code Modification, so its normative significance lies in formally adjudicating whether the misrepresentation and credit-omission conduct violated the Code, even though the ruling itself neither fulfills nor violates an obligation since it is an interpretive act rather than a professional duty-bearing action.
Section III.10.a of the Code, under which Engineer A was found to have failed to give due credit to his teammates, was later removed and no longer exists.
Narrative (3 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer A, currently employed as a staff engineer by Employer X, where you hold the same rank as five colleagues on a shared design team. Over the course of your tenure, this six person team collaborated on a series of product designs that were subsequently patented, with credit for those patents reflecting the joint effort of all six engineers. You are now preparing a resume to submit to Employer Y as part of a job application, and you must decide how to present your role in those patented designs. The resume includes descriptions of the design work, and the wording you choose will shape how Employer Y interprets your individual contribution versus the team's collective effort. Employer Y will review this resume as part of its hiring process, and your former colleagues at Employer X may at some point become aware of how you represented this work. You face a series of decisions about how to characterize this work and how others involved might respond to your choices.

Main characters (3)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Employer X Roles in this case: Employer

Guided by: Honesty in Resume Credit Claims, Honesty in Resume Representations, Due Credit for Team Design

Employer Y Roles in this case: Prospective Employer

Engineer A has a duty to ensure the five other staff engineers who worked on the project receive appropriate recognition, but presenting the project on a resume in a way that implies sole responsibility for the work directly undermines that duty. Fulfilling the personal career interest of standing out to a prospective employer conflicts with the obligation to share credit fairly with the team.

Engineer A Roles in this case: Staff Engineer

Engineer A has a duty to ensure the five other staff engineers who worked on the project receive appropriate recognition, but presenting the project on a resume in a way that implies sole responsibility for the work directly undermines that duty. Fulfilling the personal career interest of standing out to a prospective employer conflicts with the obligation to share credit fairly with the team.

Tension between Engineer A Team Credit Duty and Engineer A Resume Responsibility Misrepresentation

Other people involved in the case but not central to the opening narrative.

Engineer A has a duty to ensure the five other staff engineers who worked on the project receive appropriate recognition, but presenting the project on a resume in a way that implies sole responsibility for the work directly undermines that duty. Fulfilling the personal career interest of standing out to a prospective employer conflicts with the obligation to share credit fairly with the team.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

It was unethical for Engineer A to imply on his resume that he was personally responsible for the design of the products which were actually designed through the joint efforts of the members of the design team.
Opening States (7)
Resume Sole Credit Misattribution Engineer A Candidacy with Employer Y Engineer A Deceptive Resume Intent Section II.5.a In Force Employer Competence Deception Exposure Team Credit for Patented Products Competitive Employment Environment
Summary
  • Resumes are professional representations subject to the same honesty standards as technical reports, so exaggerating individual credit for team work is a misrepresentation, not just self promotion.
  • Engineers who work on collaborative projects have an affirmative obligation to accurately describe their own role rather than implying sole authorship or responsibility.
  • Career self interest in appearing more accomplished to a prospective employer does not excuse inflating one's contribution at the expense of colleagues who share credit for the work.

© Licensed under the GNU GPL v3