Interviews, Compensation, and Offers

Interview success depends on preparation that mirrors real engineering work. This lesson covers technical preparation, offer analysis, and practical negotiation.

Typical Elixir Interview Loop

Most processes include:

1. recruiter or hiring-manager screen,
2. coding round (Elixir fundamentals + problem solving),
3. system design round (reliability and scaling decisions),
4. behavioral round (ownership, communication, conflict handling),
5. final offer discussion.

What is often weighted heavily:

• failure handling strategy,
• OTP and supervision choices,
• database and queue tradeoffs,
• clarity of communication.

Preparation Framework (4 Weeks)

Week 1: Fundamentals Refresh

• pattern matching, recursion, data transformations,
• GenServer and supervision basics,
• Ecto and query reasoning,
• test design and failure-path tests.

Week 2: System Design

• design one Phoenix + Oban workflow,
• define SLOs and observability plan,
• discuss fallback and rollback strategies,
• practice tradeoff communication.

Week 3: Incident Scenarios

• provider outage runbook,
• queue backlog and recovery plan,
• database migration risk handling,
• post-incident action planning.

Week 4: Interview Simulation

• timed coding sessions,
• live system-design mock,
• behavioral story rehearsal,
• role-specific question bank review.

Coding Round Expectations

Interviewers usually test:

• idiomatic Elixir style,
• decomposition and naming,
• correctness and edge-case handling,
• tests where appropriate.

Useful verbal pattern while coding:

1. state assumptions,
2. propose approach,
3. implement incrementally,
4. validate with quick tests,
5. explain tradeoffs.

System Design Evaluation Criteria

A strong design response should cover:

• data flow,
• failure modes and retries,
• backpressure and queue strategy,
• observability and alerting,
• scaling and cost implications.

Offer Evaluation Model

Score offers with weighted criteria:

• compensation structure (base, bonus, equity),
• scope and decision ownership,
• on-call burden and support quality,
• team quality and mentorship,
• promotion path clarity,
• product and business risk.

Example weighting:

• scope and growth: 30%,
• compensation: 25%,
• team quality: 20%,
• operational burden: 15%,
• product risk: 10%.

Negotiation Strategy

Negotiate from evidence, not only preference.

Strong anchors:

• production systems you owned,
• reliability or cost improvements you delivered,
• role scope alignment with offer level.

Example framing:

Based on the expected ownership for platform reliability and incident leadership, I would like to discuss compensation alignment at [target range]. In my recent role I reduced incident recovery time by 60% and led rollout safety improvements that cut deployment rollbacks by 40%.

Red Flags During Offer Review

• unclear ownership boundaries,
• heavy on-call with weak support,
• vague leveling or promotion criteria,
• compensation package that assumes unrealistic equity outcomes,
• unresolved architecture debt with no plan.

Decision Discipline

Before accepting, confirm:

1. responsibilities in writing,
2. compensation details in writing,
3. reporting structure and success metrics,
4. first-90-day expectations.

Ambiguity now becomes conflict later.

Exercise

Summary

Interview performance improves when preparation mirrors real engineering: implementation quality, system tradeoffs, and incident reasoning. Offer decisions should be evidence-based and weighted across scope, support, growth, and compensation.

FAQ and Troubleshooting

I keep failing coding rounds. What should I change?

Practice timed Elixir problems with verbal tradeoff narration and test-first validation. Most misses come from communication and edge-case handling, not syntax gaps alone.

Is it realistic to negotiate if I have limited leverage?

Yes. Even small adjustments can be negotiated when tied to role scope and expected ownership. Ask clearly, use evidence, and prioritize total package quality over one number.