Mock interviews

Practise the interview with someone who runs them for real.

I interview engineers for hiring decisions, from interns to tech leads. Book a mock at the level you are aiming for and get the same interview, the same bar, and then what candidates never get: the scorecard, the verdict, and exactly why.

One session, any level, written feedback after.
Any level, intern to tech lead
A hire or no hire verdict, with the reasons
A short list of what to fix first, and how

Levels

Pick the level you want to be judged at.

The questions change less than you think between levels. The bar changes a lot. I hold you to the bar of the role you are applying for, not the one you have now.

0 to 2 years

Intern and junior

The bar. Solid basics, clean code for a small problem, and asks when stuck instead of guessing.

  • Language and OOP fundamentals
  • Data structures and complexity
  • A small coding task, talked through
  • Git, testing, how you learn

2 to 5 years

Mid level

The bar. Delivers a feature end to end without hand holding and knows why the framework does what it does.

  • Framework internals (Spring, Angular)
  • Databases, transactions, queries
  • Debugging a real looking failure
  • REST design, testing strategy

5+ years

Senior

The bar. Designs a service others can run, sees the failure modes before production does, and raises the people around them.

  • System design with real numbers
  • Concurrency, reactive, messaging
  • Performance and cost trade-offs
  • Code review and mentoring

Leading a team

Tech lead

The bar. Turns a fuzzy requirement into a plan a team can deliver, says no with reasons, and recovers a project that is slipping.

  • Architecture and its trade-offs
  • Estimation, planning, release risk
  • Stakeholders and hard conversations
  • Growing and hiring engineers

Formats

Run one round, or the whole loop.

Companies split the interview into rounds. You can practise the one that worries you, or all of them in sequence the way a real loop runs.

01

Technical deep dive

Java, Spring, Spring WebFlux, Angular, databases, messaging. I start where you are comfortable and keep going until we find the edge of what you know. Everyone has one; what matters is how you behave there.

02

Live coding

A realistic problem in a shared editor, not a puzzle. I watch how you clarify, structure, test and recover, more than whether you finish.

03

System design

Design something real, under constraints I give you and change halfway. Scaled to the level: a single service for mid, a distributed system for senior, the team and the roadmap around it for a lead.

04

Behavioural and leadership

The questions about conflict, failure, ownership and influence that decide more senior offers than any algorithm. I push for specifics, the way a hiring manager does.

05

CV and project walkthrough

You present something you built; I dig into the decisions. Most candidates undersell their best work and oversell their weakest, and both are easy to fix once you hear it.

06

Full loop

Several rounds back to back, then a single debrief across all of them, the way a hiring committee would reach a decision.

How I evaluate

The scorecard, out in the open.

In a real interview the scorecard is written after you leave and you never see it. Here you get every line of it. Each dimension is scored 1 to 4 against the bar of the level you picked, with the moments in the interview that earned the score.

DimensionWhat I look forWhy it matters

Fundamentals

What I look forYou explain why, not just what. Correct terms, no hand waving at the edges.

Why it mattersFrameworks change every few years. Someone who understands the layer below learns the next one quickly.

Problem solving

What I look forYou clarify before coding, break the problem down, and notice when your approach is wrong.

Why it mattersReal tasks arrive vague. How you handle ambiguity predicts how much guidance you will need.

Code quality

What I look forReadable names, small functions, edge cases, a test you would actually write.

Why it mattersCode is read far more often than it is written. Your team inherits whatever you leave.

System design

What I look forRequirements and numbers first, then a design, then its trade-offs and failure modes.

Why it mattersAbove mid level the expensive mistakes are design mistakes, and they are expensive for years.

Communication

What I look forYou think out loud, structure your answers, and admit what you do not know.

Why it mattersAn interviewer can only score what they hear. So can a team.

Ownership and leadership

What I look forConcrete stories with your own decisions in them, including the ones that went wrong.

Why it mattersSeniority is the size of the problem you can be trusted with alone. This is where that shows.

Then one verdict, like a real debrief.

Scores are evidence, not a sum. The verdict is the decision I would argue for in a hiring debrief for this level, and the feedback says what would have moved it up.

No hire

Below the bar in a way that would show in the first months. Usually one or two clear gaps, and the feedback names them.

Lean no hire

Close, but the evidence is not there yet. Often the knowledge exists and the interview did not show it.

Lean hire

Meets the bar with a gap a team could live with. Many real offers are made here.

Hire

Clearly at the level, with no dimension that worries me. The feedback is about the next level up.

How it works

From request to written feedback.

The interview is realistic on purpose. I do not coach during it, because the point is to see what happens when nobody helps you.

  1. Tell me the target

    The level, the stack, the kind of company, and the round you want. A job ad helps if you have one. I reply within one business day with times.

  2. The interview

    About an hour on a video call, run exactly like the real thing: the same pacing, the same follow ups, the same silence when you are stuck.

  3. Debrief on the call

    Straight after, fifteen minutes out of character. How it felt from my side, the moments that counted, and your questions.

  4. Written evaluation

    Within two business days: the scorecard, the verdict and its reasons, and the three things to work on first, each with how to practise it.

Who interviews you

A tech lead who hires engineers.

I lead engineering teams in banking and e-commerce, and I interview candidates for hiring decisions at every level up to tech lead. I have been on the other side too, often enough to know which parts of an interview are about knowledge and which are about nerves.

Today
Technical lead, banking
Since 2017
Java engineer, then e-commerce tech lead
Stack
Java, Spring, WebFlux, Angular, Kafka, Pulsar, PostgreSQL
Certified
SAP Commerce Cloud Developer
Degree
Computer Science, Babes-Bolyai University
Languages
English, Romanian

For companies

Also for teams that hire.

The same experience works from the other side of the table.

01

Calibrate your interviewers

I sit in on your interviews or run one alongside your panel, then compare scorecards. Most disagreements turn out to be an unwritten bar.

02

Design your loop

Rounds, questions and a written bar per level, so two interviewers reach the same verdict about the same candidate.

03

Prepare people for promotion

A mock at the next level up for engineers you want to promote, with a written plan they can work through with their lead.

Questions

Before you book

Can you prepare me for a specific company?

For the level and the style of interview, yes: tell me the company and the role and I shape the session around how they hire. I will not share questions from any company I interview for. Those are confidential, and memorised answers fall apart at the first follow up anyway.

I am not a Java developer. Is this still useful?

The deep technical round is strongest for Java, Spring and Angular. System design, behavioural, leadership and the CV walkthrough work for any backend or full stack engineer.

Will you go easy on me?

No, and that is the value. A kind mock teaches you nothing. You will get a candid verdict, delivered respectfully, with what to do about it.

In which language?

English or Romanian. If the real interview will be in English, do the mock in English, even if it feels harder.

What does it cost?

It depends on the format, one round or a full loop. I quote a fixed price when I reply, before anything is booked, and you pay nothing until you agree to it.

Is what I tell you confidential?

Yes. Your recording, if you ask for one, your CV and the evaluation are yours and go to nobody else, including your employer or any company I interview for.

Book an interview

Tell me what you are preparing for.

Useful to me: the role and company type, your stack and years of experience, the date of the real interview, and what worries you most about it. Two or three sentences is plenty.

I reply within one business day with a price and a few times. No mailing list. How your message is handled.