Describe a proud project and handling credit conflict
Company: Goldman Sachs
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: nan
Interview Round: Technical Screen
Answer the following behavioral questions:
1. **Project you’re proud of:** Describe a project you’re proud of. Explain what you built, your role, the impact, and what you learned.
2. **Credit/academic integrity scenario:** If a college classmate takes credit for your work (e.g., uses your code/assignment as their own or claims your contribution), what would you do? Walk through your steps and how you would handle it professionally.
Quick Answer: This question evaluates interpersonal and ethical competencies such as ownership, leadership, communication, conflict resolution, and professional integrity in the context of software project work.
Solution
## 1) “Describe a project you’re proud of” (How to structure)
Use a tight **STAR / CAR** format and aim for *your* ownership.
### A. STAR outline
- **S (Situation):** What problem existed? Who was affected? What constraints (time, scale, reliability, cost, privacy)?
- **T (Task):** Your responsibility and success criteria (SLOs, latency, accuracy, adoption, revenue/cost, developer time saved).
- **A (Actions):** 3–5 specific things you personally did. Use technical depth appropriate for the role.
- **R (Results):** Quantified outcomes + validation method (A/B test, load test, incident reduction, user metrics). Include what you’d improve next.
### B. What interviewers look for
- Clear scope and *personal* contribution (not “we did X” only).
- Tradeoffs and reasoning (why that design, why that algorithm).
- Ability to execute: planning, iteration, debugging, communication.
- Impact measurement (before/after metrics).
### C. Good “Results” examples
- “Reduced p95 latency from 900ms to 220ms by caching + query rewrite.”
- “Cut cloud cost by 30% by right-sizing and batching.”
- “Improved model precision from 0.71 to 0.82; monitored drift weekly.”
### D. Common pitfalls
- Too much background, not enough action.
- No measurable impact.
- Vagueness about your role (“I helped”).
---
## 2) “If a classmate takes credit for your work, what do you do?”
This is primarily an **integrity + conflict-resolution** question. A strong answer is calm, evidence-based, and escalates appropriately.
### A. Principles
- Protect academic integrity and your own record.
- Assume misunderstandings first, but don’t ignore clear misconduct.
- Follow course/university policy.
- Keep communication professional and documented.
### B. A practical step-by-step approach
1. **Confirm facts:** What exactly was copied/claimed? Make sure you’re not misinterpreting collaboration rules.
2. **Collect evidence:** Version history, timestamps, commit logs, docs, messages, submission receipts.
3. **Talk privately first (if safe/appropriate):**
- State facts neutrally: “I noticed your submission matches my code from date X.”
- Ask for explanation; give chance to correct (withdraw/redo/cite properly).
4. **Escalate to the right channel:** If they deny or it’s serious, contact the **TA/professor/academic integrity office** with the evidence.
5. **Protect yourself going forward:** Don’t share final solutions; use private repos; clarify collaboration boundaries.
### C. What to emphasize in your response
- You act **quickly but professionally**.
- You avoid public confrontation; you follow policy.
- You focus on resolution and prevention.
### D. Edge cases / nuance
- If the course allows collaboration but requires attribution, push for **proper credit** rather than punishment.
- If there’s potential retaliation or harassment, skip direct confrontation and escalate immediately.
### E. A concise sample response (template)
“First I’d confirm the similarity and gather objective evidence like timestamps and version history. Then I’d speak to them privately to understand if it was a misunderstanding and ask them to correct it according to course rules. If it’s clear misconduct or they refuse to fix it, I’d escalate to the TA/professor with documentation. I’d keep it professional and focus on integrity and preventing it from happening again.”