Home › Practice › Mock interview
Mock interview drill
A full 30-minute simulated screening, timed and scripted. Run this twice before the real call. Once with notes visible, once cold.
Setup: Phone on silent. Camera on. Webcam at eye level. Water nearby. Open this page on a phone or second screen if you have one — don't switch tabs during the drill. Set a 30-minute timer when you start. Speak out loud. Mumbling kills the drill.
01Block 1 — Opening (0:00–4:00)
00:00 — 00:30 · Greeting
Hi Parish, thanks for jumping on. Can you hear me okay?
You: "Hey, yeah, loud and clear — thanks for setting this up." Smile. Don't dive into anything yet.
00:30 — 01:30 · Small talk
Where are you joining from?
You: "Bangladesh — Rajshahi area. Working remote for Artlist for a while now, so I'm pretty used to async US/Europe schedules." (You're pre-empting the timezone question.)
01:30 — 04:00 · Tell me about yourself
So, want to start by just telling me a bit about yourself and your background?
You: Run your 60-75 second pitch. Builder/entrepreneur angle. Performance at Artlist + side projects. End on the soft pivot. Review the script →
02Block 2 — Motivation (4:00–9:00)
04:00 — 06:00 · Why us?
Cool. What got you interested in Omnesoft specifically?
You: Run the "wasn't actively job-hunting" script. Stage of company + ERP for fabrication is unsexy in the best way + here to learn more. Review the script →
06:00 — 07:30 · What attracts you about the role?
What about the role itself — what stood out in the job description?
You: "Three things. The stack maps directly to what I do — React, TypeScript, Tailwind. Performance is called out as a focus, which is something I've been deep in at Artlist. And the AG Grid / TanStack Query / Nx mention tells me you're past the toy-app phase — you're solving real ERP-scale UI problems, which is the kind of work I want."
07:30 — 09:00 · What are you looking for in your next role?
What are you hoping to get out of your next move?
You: "More end-to-end ownership. At Artlist I work on a slice of a large product — here it sounds like I'd see more of the surface. Also a smaller team where good engineering decisions actually compound — at scale you can hide behind process; at 22 people, what you ship is what you ship."
03Block 3 — Experience & technical (9:00–20:00)
09:00 — 13:00 · Walk me through your work at Artlist
Tell me about your role at Artlist day-to-day. What kind of stuff are you working on?
You: Anchor on performance work + collaborating with Dan + locale/translation work as a concrete example of cross-cutting frontend infrastructure. Don't list every project — tell ONE story end-to-end. Use the Translation Infrastructure STAR. Review STAR →
13:00 — 15:30 · A technical project you're proud of
Tell me about a project — at work or on the side — you're particularly proud of.
You: Pick tutorialsearch.io. End-to-end ownership story: Cloudflare stack, D1 for data, KV for sessions, R2 for assets, Pages for the frontend, affiliate integration, SEO work. Specific metrics if you have them. Review STAR →
15:30 — 17:30 · Performance deep-dive
You mentioned performance work — give me a concrete example. What was slow, and how did you fix it?
You: Pick ONE bug or initiative. Frame: (1) symptom, (2) what you measured, (3) what the actual cause was, (4) what you changed, (5) the metric improvement. The "diagnose before fix" structure makes you sound senior.
17:30 — 20:00 · Stack-specific question
Have you used TanStack Query before? AG Grid? What about Nx for monorepos?
You: Be honest. "TanStack Query — yes, used it on side projects, comfortable with the cache/invalidation model. AG Grid — I've worked with similar grid libs and read AG Grid's docs while prepping for this; I haven't shipped it but the model is familiar. Nx — I've used Turborepo for similar workspace problems; Nx I'd ramp up on quickly." Don't fake fluency. Review their stack →
04Block 4 — Logistics (20:00–25:00)
20:00 — 21:30 · Timezone & availability
Just to set expectations — we're a US-based team, mostly Eastern. How does that work for you?
You: "Pretty well, actually. I've been working remote with Western timezones for years at Artlist. I usually have 4-5 hours of overlap with US Eastern, and I can flex within reason for syncs that need to happen on your side of the day." Don't promise night-shift availability if you don't mean it.
21:30 — 23:00 · Notice period
How quickly could you start, if things moved forward?
You: "Standard notice for me would be a month. I want to leave Artlist on good terms — they've been good to me. I can be flexible on a start date if there's a hard deadline on your side, but I wouldn't want to leave my current team in a tough spot."
23:00 — 25:00 · Salary expectation (THE ONE)
And what salary range are you looking at for this role?
You: DEFLECT FIRST. "I'd love to learn more about the role and team before locking in a number — comp is one of several factors for me. What range did you have in mind for this role?" If they push: "$70K to $90K USD per year base for a full-time employee, with some flexibility depending on the rest of the package." Full strategy →
05Block 5 — Your turn (25:00–30:00)
25:00 — 28:00 · Your questions
Great. What questions do you have for me?
You: Pick 2-3 from your prepared list. Review the list → Best for stage 1: "What does the rest of the interview process look like?" / "What does a typical week look like for the frontend team?" / "What's the biggest technical challenge the team is working on right now?"
28:00 — 29:30 · Wrap up
This was great. Any other questions before we wrap?
You: "One last one — what's the timeline you're working with, and what should I expect as a next step?" Then: "Thanks for the time. I appreciated the conversation — I'd be glad to take this further."
29:30 — 30:00 · Sign-off
We'll be in touch within a few days.
You: "Sounds good. Thanks again." Smile. Wait for them to drop the call (don't rush off).
06After the drill — self-review
- Recording: Did you record yourself? Watch it back at 1.5x speed. Two things to look for — pace and filler words.
- Pace: Senior candidates speak slower than juniors. If you're rushing, you sound nervous. Pause before answering big questions.
- Filler: Count "um," "like," "kind of," "you know," "basically." Awareness alone cuts these in half by drill 2.
- Eye contact: Looking at the camera, not the screen. People underestimate how off it feels otherwise.
- Energy: The screener is doing 6+ of these. Be the one who's awake, curious, and easy to talk to.
- Length: Did any answer go over 90 seconds? Trim it. Concision > thoroughness in screenings.
07Curveballs — practice these too
If you have time for a third drill, have someone (or yourself, in the mirror) hit you with these:
Why are you applying to other companies and not just Artlist?
"I'm not unhappy at Artlist — they've been great. I'm at a 10-year mark and being intentional about what's next. The reasons I'd consider a move are about the next decade, not about leaving."
This is a US company — why should we hire from Bangladesh vs. a local candidate?
"Two answers. One: I've been working remote with Western teams for years; the timezone overlap is real and the async muscle is built. Two: cost-effectiveness without a quality compromise. You get senior-level work for a senior-but-not-Bay-Area rate. The role's remote, the talent pool's global — at this point the question is fit, not geography."
How do we know you'll stay? What's stopping you from jumping ship for a higher offer?
"I've been at Artlist for 10 years. That's the longest answer I can give to that question. What keeps me at a place is interesting work and good people. If you give me both, you don't have to worry."
What if we can only offer at the lower end of your range?
"I'd want to talk about the rest of the package — equity, bonus, growth path, vacation. Comp is one factor, not the only one. If the role's right and there's a real path forward, we can probably find a number that works."
You haven't shipped Nx or AG Grid in production. Isn't that a gap?
"It's a learning curve, not a gap. I've shipped React/TypeScript at scale for years; the tools change, the fundamentals don't. I'd expect to be productive within the first two weeks and fully ramped within a month. I'd rather be honest about what I haven't shipped than oversell."
What do you do when you're bored?
"Build something. tutorialsearch.io started as a 'why doesn't this exist' itch on a Tuesday night. parish.cv is where I write about my workflow. The YouTube stuff — Mirandized, TracerTales — same instinct. I don't have a great answer for 'what do you do to relax' that doesn't involve shipping."
If you nail this drill twice in a row, you're ready. The actual screening will feel calmer because you'll have already heard most of these questions. Don't try to memorize lines — internalize the structure and let the words flow.