First-round interview, led by a non-technical recruiter. Synthesized from the Role Profile, Supporting Signals rubric, and Core Technical rubric in
screening_interview/.
This is a gating screen, not the primary evaluation. The technical scenarios (CORE_01 Debugging, CORE_02 System Evolution, CORE_03 Product Thinking) drive the actual hiring decision — but those happen in the technical round, with a technical interviewer.
In scope for this round (HR can credibly evaluate):
- English clarity (technical and non-technical)
- Communication structure
- Ownership stories
- Comfort with ambiguity
- Motivation, engagement, and role fit
- Maturity (handles failure, gives accountability)
- Basic product mindset (connects work to user/business impact)
Out of scope — do NOT try to evaluate here:
- Node.js / framework depth
- Debugging quality
- System design / architecture decisions
- Code quality
If a candidate gives a technical story, listen for how they tell it (ownership, clarity, structure), not whether the technical claim is correct. That's not your job in this round.
- Role: Senior Full-Stack Engineer (IC3 / IC4), Symbium
- Reports to: Abhijeet (CTO)
- Location: Remote, Brazil
- Comp: $100K–$140K
- Target start: Q2 2026, 2 hires
The engineering team is small and scaling under pressure. Significant parts of the system were built quickly and now need to be stabilized while new features and city launches continue. This role exists to reduce dependency on the CTO — someone who takes critical parts of the system end-to-end, operates with high autonomy, and drives execution without needing a spec.
This is not a "write code to spec" role. That single line is the most useful filter you have. Candidates who treat themselves as task-executors are not the right hire — no matter how strong their resume looks.
Target: 45 minutes.
- 3 min — intro & rapport
- 4 min — candidate's elevator pitch ("walk me through your background")
- 25 min — behavioral probes (5 dimensions × ~5 min each)
- 8 min — candidate questions for us (this is itself a signal — see Engagement)
- 5 min — logistics, comp expectations, timeline, next steps
Each dimension has: a probing question, follow-up drills, what strong vs. weak answers sound like, and the 1–5 score rubric.
"Can you walk me through a project you owned end-to-end — what it was, what you did, what the outcome was?"
This is your single best signal. The candidate will talk for 3–5 minutes; you listen for how they speak as much as what they say.
Follow-ups (use the drill technique — never accept the summary):
- "What was the problem you were solving — in non-technical terms?"
- "How did you explain that to a non-engineer at the time?"
- "What part of this would be hard to explain to your CEO?"
Strong answers:
- Structures the answer (context → problem → action → outcome)
- Adapts jargon down when probed
- Pauses if the question is ambiguous and clarifies
- Comfortable English under conversational pressure
Weak answers:
- Rambles without structure
- Cannot simplify when asked — keeps reaching for jargon
- Translates from Portuguese mid-sentence, loses thread
- Long pauses, fragmented answers
Score 1–5:
- 5 — Explains complex work in layers, adapts to audience, structures reasoning naturally
- 4 — Clear and structured; minimal unnecessary jargon
- 3 — Understandable but inconsistently structured or occasionally unclear
- 2 — Attempts to simplify but remains unclear or fragmented
- 1 — Disorganized, overly technical, hard to follow
Floor: candidates scoring below 3 should not advance.
"Tell me about the most ambitious thing you've ever owned — not just contributed to, but owned. Walk me through how it ended."
Follow-ups:
- "Who decided what to build? Who decided when it was done?"
- "What was the hardest decision you had to make alone?"
- "What did you do when something went wrong?"
- "What was the impact — how do you know?"
Strong answers:
- Uses "I" naturally — distinguishes their work from the team's
- Describes decisions they made, not just tasks they executed
- Names a setback and how they handled it
- Can quantify impact (users, revenue, latency, incidents avoided — anything concrete)
Weak answers:
- Constant "we" with no clear personal contribution
- Describes assigned tasks, not scoped work
- Cannot name a decision they personally owned
- Impact is vague ("the team shipped it")
Score 1–5:
- 5 — Owned end-to-end, defined scope and decisions, quantified impact, handled setbacks proactively
- 4 — Clear ownership, explains decisions and trade-offs, measurable impact
- 3 — Some ownership but limited clarity on decisions or impact
- 2 — Partial ownership, relied heavily on others for direction
- 1 — Describes only assigned tasks; no ownership of outcomes
"Tell me about a time you had to start working on something where the requirements were unclear or kept changing. How did you handle it?"
Follow-ups:
- "Who did you go to first — and why them?"
- "What did you decide on your own vs. escalate?"
- "Did the direction change midway? How did you adapt?"
Strong answers:
- Asks clarifying questions before acting
- Makes assumptions explicit and validates them
- Defines a starting direction even without full clarity
- Communicates risks proactively
Weak answers:
- Waits for instructions
- "I asked my manager what to do" repeatedly
- Cannot describe how they decided what to do first
- Frames ambiguity as a blocker, not a normal condition
Score 1–5:
- 5 — Creates structure in ambiguity, aligns stakeholders, progresses independently
- 4 — Defines direction with reasonable assumptions, communicates risks
- 3 — Moves forward but seeks frequent validation
- 2 — Hesitant; asks questions but cannot define direction
- 1 — Waits for instructions; cannot proceed without guidance
"Tell me about a time something you owned failed or went badly. What happened, and what changed afterwards?"
Follow-ups:
- "What was your role in the failure?"
- "What did you learn? What do you do differently now?"
- "Who was affected? Did you talk to them about it?"
Strong answers:
- Names their role in the failure without prompting
- Specific lesson learned, tied to a specific behavior change
- Emotional honesty (not just a clean lessons-learned slide)
- Has a story — not a vague philosophy
Weak answers:
- Externalizes blame ("the PM didn't define it well")
- "I learned to communicate better" — generic, no specifics
- Cannot name a real failure
- Minimizes ("it wasn't really a failure, we shipped late but…")
Score 1–5:
- 5 — Deep self-awareness, structural lessons, accountability, lasting behavioral change
- 4 — Takes ownership, clear lessons learned, demonstrable change
- 3 — Basic reflection, limited depth
- 2 — Acknowledges issues but minimizes responsibility
- 1 — Cannot describe failure or externalizes blame
"What attracted you to this role specifically? What questions do you have about Symbium, the product, or the team?"
Follow-ups (most signal comes from the questions THEY ask):
- "What did you read or watch about Symbium before this call?"
- "What's a question you couldn't answer from public material?"
- "What would make this role a bad fit for you?"
Strong answers:
- Has researched the product — can describe what it does in their own words
- Asks specific questions about the work, team dynamics, or product direction
- Names what they're optimizing for in their next role (and it aligns)
- Honest about what would make it a bad fit (red flags they'd want to avoid)
Weak answers:
- Generic interest ("looks like a great opportunity")
- No questions, or only logistics questions (PTO, hours)
- Cannot describe what the product does
- Asks "what does your company do?" — they didn't prepare
Score 1–5:
- 5 — Strong alignment, proactive thinking, clear vision for role impact
- 4 — Clear motivation, solid understanding of role and context
- 3 — Some alignment, but motivation/understanding is shallow
- 2 — Generic interest, lacks depth
- 1 — No curiosity, no preparation, no specific understanding
These are nice-to-have signals you can probe if the conversation is moving well:
"When you build something, how do you decide what's good enough to ship?"
Strong: thinks about user impact, trade-offs, what can wait. Weak: "when tests pass" / "when the spec is met."
"Have you worked with US-based or fully-remote teams before? What was different about it?"
Listen for: comfort with async communication, written clarity, time-zone awareness.
"How do you use AI tools in your day-to-day work?"
Strong: concrete examples, names where AI helped and where it didn't, talks about validation. Weak: "I use Copilot for autocomplete" / "I don't really use AI."
- Tells real, specific stories with names, dates, numbers
- Uses "I" appropriately — distinguishes self from team
- Asks clarifying questions before answering
- Takes ownership of failures
- Adapts language when probed for simpler explanation
- Has researched the company and asks substantive questions
- Only theoretical answers, no concrete examples → suggests no real production experience
- Jumps to solutions without asking what the problem is → weak product thinking
- Blames others for failures → low accountability, risky in small team
- Cannot simplify explanations → will create stakeholder friction
- Describes partial contributions, never full ownership → task executor, not owner
- No curiosity about the product → low engagement, long-term fit risk
- Cannot communicate in conversational English under light pressure → bottleneck risk with US-based founders
After the call, score each of the five required dimensions 1–5. Then:
- Advance — All five scores ≥ 3, with at least one 4 or 5 in Communication AND one in Ownership.
- Hold for discussion — Any single 2, or multiple 3s in critical dimensions (Communication, Ownership, Maturity).
- Reject — Any 1, OR a 2 in Communication, OR a 2 in Engagement, OR any explicit red flag from the list above.
Floors that cannot be compromised:
- Communication < 3 → reject (will not survive working with US founders).
- Engagement < 3 → reject (low motivation in a small team is a multiplier of all other risks).
- Ownership < 3 → reject (this role does not have room for executors).
Strong charisma or polished interview presence does not compensate for weak scores. Repeated 3s across multiple dimensions is a worse signal than one 2 and four 4s — consistency matters more than peaks.
For the technical round to make sense of your work, capture:
- Scores (1–5) for each of the five dimensions
- Specific quotes — especially places where the candidate said something revealing
- Any red flag you saw, with context
- Open questions for the technical interviewer to probe (e.g., "claims to have owned the database migration end-to-end — verify technical depth")
- Advance / hold / reject recommendation, with one-sentence rationale
The technical round should not re-do this evaluation. It should build on it — confirming or challenging the signals you flagged.