seokopat · careers
> seokopat.team.join()
Careers
There are no open positions right now. Even so, we do not wait for a job ad to meet the right person; an application that explains who you are always gets read.
We are a small team and we prefer to stay that way. Hiring is therefore rare, but when it happens we are looking for a long engagement.
Below is how we actually work, written plainly. The point is not to make ourselves look good; it is so you can decide whether this suits you.
Current status
We have no open listings. When one opens, it gets published on this page.
You can still apply. We keep the applications we receive and look at them first when a need appears. A list of people already known moves faster than starting a hiring process from scratch.
How work runs here
The person doing the work speaks
There is no account manager layer. In a client call or a code review, the person doing the work is the one at the table.
Decisions come with reasons
Technology choices, campaign structure, architecture calls: whatever it is, why it was done that way stays written down. Six months later nobody has to guess.
Small, verifiable steps
Instead of working behind closed doors for months and unveiling a surprise, we ship genuinely usable pieces on a regular cadence.
Not knowing is fine
Saying you do not know is not a weakness here. The problem is pretending otherwise and putting the work at risk.
Profiles we usually need
Even with nothing open today, needs usually appear in these areas.
- Software: developers comfortable with TypeScript and React who do not avoid databases and integrations
- SEO: specialists who can go technical and are not afraid of Search Console and log files
- Advertising: people who can set up their own measurement and think in contribution margin
- Design: designers who consider interface, content and speed together and do not hide behind templates
- Operations: people who have seen warehouse and stock flow on the floor and can write a process
How to apply
- 01
Write a short email
Send it to hello@seokopat.com. Putting your field in the subject line is enough.
- 02
Attach real work
More useful than a CV is something you actually did: a repository, a live site, an account you ran, or a process you built.
- 03
Describe a problem
Explain a problem you solved in three paragraphs: what the situation was, what you did, what happened. If something went wrong, include that too; it tells us more.
- 04
Response
We read every application. If there is a matching opening we invite you to talk, otherwise we keep it on file. We do not send template replies.
A few honest notes
- We do not read long cover letters. Three paragraphs of real explanation beat two pages of template text.
- Applications written by AI that say nothing are easy to spot. Use your own words.
- Portfolios presenting someone else's work as your own surface during the process.
- With no open position, replies can take a while; that is queue order, not disinterest.