"Tell me about yourself"
The first question and the one most candidates fumble. Yours is scripted, tested, and tuned to your "builder/entrepreneur" angle.
01Your primary script
Aim for 60–75 seconds spoken. Don't memorize word-for-word — internalize the four beats:
- Who I am + how long
- What I do at Artlist (with one strength: performance)
- What I do beyond the day job (the entrepreneur angle)
- Why I'm here (soft pivot back to them)
I'm a senior frontend developer with over 10 years of experience, currently at Artlist, where I work on the main product's frontend. A lot of my recent work there has been around performance — improving load times, optimizing how we render and ship JavaScript, and generally making the app feel fast at scale.
What I think sets me apart from a lot of frontend devs is that I also build and ship my own products on the side. I run tutorialsearch.io, a tutorial aggregator built on a Cloudflare stack — Pages, D1, KV, R2 — where I handle everything from SEO and content syndication to affiliate integrations and infrastructure. I also run my personal blog at parish.cv where I write about my dev workflow.
So I bring two things to the table: the discipline of working in a real product team at Artlist, and the end-to-end ownership mindset of someone who ships and operates their own products. I'm looking at Omnesoft because I'm curious about what an earlier-stage environment looks like, and I'd love to hear more about what you're building.
02Why this works
- Opens with seniority anchor. "10+ years" + "currently at Artlist" — they know they're talking to a real senior dev in the first 5 seconds.
- Performance is your strongest claim. The JD literally says "optimize rendering performance for large datasets." Front-load it.
- Side projects = entrepreneur signal. The JD says they want "ownership mindset," "open source or technical writing." You hit both.
- "Two things to the table" closes neatly. Easy for them to remember when comparing candidates later.
- Soft pivot at the end hands them the conversation gracefully. Avoids the awkward silence after you stop talking.
03Customizing on the fly
If the screener is technical
After "performance," expand briefly:
"…optimizing how we render and ship JavaScript — bundle splitting, code-splitting strategies, removing dead code from translation files, that kind of work."
This signals depth without bragging.
If the screener is non-technical (recruiter)
Drop the Cloudflare stack list. Replace with:
"…where I handle everything end-to-end, from infrastructure to frontend to SEO and growth."
"End-to-end" lands harder than tech names with non-engineers.
04Practice protocol
- Read it through twice silently. Get the shape.
- Say it out loud, three times. First time, slowly, looking at the script. Second, glancing only. Third, eyes closed.
- Record yourself on your phone or laptop. Play it back. The first listen will be uncomfortable. That's the point.
- Count fillers. "Um," "like," "kind of," "basically." Aim for zero.
- Time yourself. Under 60 seconds = too short. Over 90 = too long. Trim the middle.
- Get fluent enough to sound spontaneous. If it sounds memorized, it's worse than no script at all.
05Variants for follow-up questions
"Tell me more about your work at Artlist."
Artlist is a creative platform — music, video, sound effects, footage — used by millions of creators. I'm on the frontend side of the main product. My focus areas have been performance — improving how we ship JavaScript, optimizing page load and interaction times — and locale/translation infrastructure, which sounds boring but actually has real performance implications when you're shipping translation files to dozens of regions.
I work closely with a colleague Dan on a lot of this. The codebase is large enough that the interesting work is at the architectural level — figuring out how to make changes that scale, not just how to ship a feature.
"Tell me about tutorialsearch.io."
It's a side project — an aggregator that pulls in tutorials and learning resources from across the web on a wide range of topics. The goal is to be the search-engine layer over fragmented learning content.
What's interesting to me about it as an engineer is that I run the whole thing solo. Frontend on Next.js, infrastructure on Cloudflare Pages, D1 for the database, KV for caching, R2 for storage. I built the affiliate integrations, the SEO pipeline, the content ingestion. It taught me a lot about being pragmatic — when to build, when to use a service, when to cache aggressively.
Mostly it keeps my product instincts sharp. When you have to think about SEO, conversion, infra cost, and code quality at the same time, you stop optimizing in a vacuum.
"Why are you considering leaving Artlist?"
I'm not unhappy at Artlist — I want to be upfront about that. But after several years there, I'm at a point where I want to be more intentional about my next chapter. Specifically, I'm interested in earlier-stage environments where I can have more end-to-end ownership and influence on architectural decisions, not just be one of many on a large team.
This role came up at the right time to at least have the conversation.
"What are you most proud of?"
Two things, one at work and one outside. At Artlist, the performance work — I won't claim a single hero metric, but the body of work has measurably improved how the product feels for end users, and that matters more than any single shipped feature.
Outside of work, I'm proud of tutorialsearch.io because I built and shipped it solo. It's not a unicorn — but it's live, it has users, it has revenue, and I run all of it myself. That's the kind of thing that proves to me I can ship.