Your CV
Ship beats polish. One page. Specific projects. Links over lists. Tell us what you’ve built, what broke while building it, and what you learned. If you’ve contributed to open source or shipped for customers, name the work and the outcome.
Getting
in.
How we hire. No leetcode. No games. Real work, honest conversations, a decision in a week.
The freedom of a startup. With the stability of a large, profitable, growing company. That’s how it feels to work at Skcript.
The process
Six steps. About two weeks.
- 01
Apply
No cover letter templates. No resume keyword bingo. Tell us what you’re proud of and what you want to build next.
- 02
First conversation
A 30-minute call. What you’ve shipped. What you want to learn. Whether this is your fit — as much for you as for us.
- 03
The work itself
No leetcode. No brain teasers. A small, real problem from our actual codebase. Take a few days. Ship what you would ship if it were going to production.
- 04
Deep dive
A half-day with three or four engineers. We read your work together, pair on the next thing, walk the codebase. You leave knowing exactly what you’d be walking into.
- 05
The decision
Hire by committee. Every person you met gets a vote. No single yes, no single no. One week, usually less.
- 06
The offer
What you earn. What you own. What we expect. On paper, plain language, no games.
How to prepare
Come as you are. Bring what you’ve built.
Your interview
No trick questions. No whiteboard gotchas. Come with things you’ve built, opinions about how you’d build them today, and questions for us. We’ll read code together — yours and ours. Be ready to disagree, and to change your mind.
Ready
when you are.
Pick a role. Or tell us what you’d rather be doing. Either works.