Explain why EDG and why you fit

Prompt

You have 4 minutes of total time per question to prepare and answer. You may re-record / answer each question up to 2 times.

Answer the following:

1. Why do you want to work at EDG?
2. What makes you a good fit for EDG? Provide specific examples from past jobs, internships, or projects that demonstrate relevant skills and impact.

Expectations

• Be concise and structured.
• Use concrete, evidence-based examples (metrics, scope, stakeholders, constraints).
• Connect your experience to what EDG likely values (role requirements, company mission/products, team culture).

Solution

What a strong answer looks like

Treat this as two separate but linked mini-stories:

1. “Why EDG” = your motivations + what you know about the company + why now.
2. “Why you” = your evidence (skills, behaviors, outcomes) mapped to what EDG needs.

Because you have limited time, aim for:

• 60–90 seconds for “Why EDG”
• 2–3 minutes for “Why you (examples)”

---

Step-by-step framework

1) Build a tailored “Why EDG” (not generic)

Use a 3-part structure:

A. Mission/product pull (specific):

• Mention 1–2 concrete things: product area, customer segment, technical challenges, recent launches, market positioning.

B. Role pull (what you’ll do):

• Name 2–3 responsibilities from the job description.
• Explain why those match what you want to do next.

C. Growth pull (why now):

• The new scope you’re seeking: scale, ownership, cross-functional collaboration, mentorship, domain.

Pitfalls to avoid

• Vague statements (“I like your culture”).
• Over-indexing on perks/location.
• Saying you’ll “learn a lot” without what you’ll contribute.

---

2) Answer “Why you’re a fit” with 2 evidence-backed examples

Pick two examples that cover different dimensions, typically:

• Execution/impact (shipping, measurable results)
• Collaboration/ownership (ambiguity, cross-team alignment, leadership)

Use STAR (Situation, Task, Action, Result) but compress it:

• S/T (10–20 sec): context + your responsibility
• A (40–60 sec): what you did, decisions, tradeoffs
• R (20–30 sec): outcome with metrics + what you learned

Add a “relevance bridge” after each example: One sentence tying it back to EDG’s needs.

Good metrics to include

• Latency/throughput improvements (e.g., p95 latency −35%)
• Reliability (e.g., reduced error rate from 1.2% to 0.2%)
• Cost (e.g., infra cost −20%)
• Business/product (e.g., conversion +3.1%, retention +2pp)
• Delivery (e.g., shipped in 6 weeks, unblocked 3 teams)

Pitfalls to avoid

• Listing technologies without impact.
• Taking full credit for team outcomes without clarifying your contribution.
• Using only one “big project” example if it doesn’t show collaboration/communication.

---

How to tailor quickly (prep checklist)

In your prep minute, write:

1. Top 3 job requirements (from posting): e.g., backend APIs, distributed systems, data pipelines, stakeholder management.
2. Two matching stories (project A and B) + one metric each.
3. One specific EDG reason (product/mission/market/engineering challenge).

---

Example answer outline (template you can fill)

Why EDG (60–90 sec)

• “I’m excited about EDG because [specific product/mission] and the engineering challenges around [scaling, reliability, ML, data, etc.].
• This role stands out because it emphasizes [2–3 responsibilities], which aligns with what I’ve been doing in [your recent work] and what I want to deepen next.
• I’m also looking for [ownership/cross-functional impact/scale], and EDG seems like a place where I can contribute immediately while growing.”

Why I’m a fit (2 examples)

Example 1 (execution/impact): STAR + metric + relevance bridge.

Example 2 (ownership/collaboration): STAR + metric + relevance bridge.

Close (10 sec):

• “Overall, I bring [skill 1], [skill 2], and a track record of [impact theme], which maps directly to what this team needs.”

---

Using the “two attempts” rule effectively

If you can re-answer:

• Attempt 1: deliver the structured response.
• Attempt 2 (if needed): tighten wording, add missing metric, improve the EDG-specific detail, and shorten any rambling section.

A good reason to redo is if you:

• forgot a key result/metric,
• didn’t clearly connect your story back to the role,
• spent too long on setup.

---

Edge cases

• No prior internship/job: Use school projects, open-source, hackathons; emphasize scope, constraints, and measurable outcomes.
• Switching domains: Focus on transferable skills (problem decomposition, debugging, stakeholder alignment, shipping) and show a learning plan tied to the role.
• Limited metrics: Use proxy measures (load test results, number of users, reduction in manual steps, time saved per week) and be transparent about estimates.