Original listing text, shown exactly as published by the company.
What we expect from candidate
We will prioritise candidates who are located in Kaunas or can visit our office when it is needed.
Must haves
- 2+ years of PHP in a real production codebase. Symfony or Laravel is a bonus; you'll learn Symfony fast if you don't know it.
- SQL fluency. You can read a slow query plan, spot an N+1, and decide between an index and a denormalization without panicking.
- You write tests. Not because someone asks - because you don't trust code you haven't tested. Behat, PHPUnit, whatever the stack uses.
- Git discipline. Small commits, clear messages, useful PR descriptions. You rebase before you ask for a review.
- You read code before you change it. You can land in an unfamiliar bundle, trace a flow, and ship a fix without breaking three things you didn't see.
- English, written, professional. Most of our work happens in text - tickets, PRs, docs, Slack.
AI
- You use AI tooling daily. Claude Code, Cursor - something.
- You verify what AI gives you. You don't merge code you didn't read.
- You're comfortable writing prompts, skills, or small agents to automate parts of your own workflow.
Should haves
- Frontend basics - Twig, vanilla JS, jQuery enough to be dangerous. You don't need to be a React expert, but you should be willing to learn (we're migrating to React islands).
- Experience with REST APIs — designing endpoints, versioning, auth, pagination. We have a mobile API and a partner API and you'll touch both.
- Comfort in Linux / shell — you can SSH into a box, tail a log, find a process, restart a service.
- Doctrine ORM or another mature ORM. You understand the cost of lazy loading.
Nice to haves
- Symfony specifically (events, forms, voters, bundles).
- React, Vite, modern frontend tooling.
- AWS basics (EC2, ASG, RDS).
- MCP, LLM tool-use, RAG - if you've built anything agentic, tell us about it.
How you'll be evaluated
- A short intro call - we talk about what you've built and what you want to build.
- A code conversation - we look at a real piece of our codebase together and discuss what you'd change.
- A paid trial week if both sides are still interested. Real work, real PRs, real review.
What disqualifies you
- You can't read an unfamiliar codebase without asking the team to walk you through it.
- You ship without tests and call it pragmatism.
- You're allergic to AI tooling on principle.
- You're only interested in greenfield projects - most of our work is in code that already exists.
