We're not hiring
right now.
Thanks to everyone who applied — we've closed applications for both our internship roles. We'll update this page when we're hiring again. In the meantime, feel free to follow us to stay in the loop.
These roles are now closed.
Applications are closed. Previous role descriptions are retained below for reference; this page is not an invitation to apply. Follow us on X or LinkedIn to hear when we open new roles.
Full-Stack Developer
Closed
Original role description — applications closed
You'll work on real features that ship to real users — the web app, the integrations, and the self-contained pieces that make Xolvyn feel alive. You'll build new things and help keep the existing ones sharp, with the founder right there to pair with and unblock you.
// What you'll do
- Work on the web product — ship real features and help keep the existing pages polished.
- Help build the PR-impact bot — showing what a pull request touches across the dependency graph.
- Pitch in on team workspaces — shared maps, roles, and org-wide analysis.
- Learn the integration side — GitHub/GitLab OAuth, email, billing, and the API routes behind it all.
AI/ML Developer
Closed
Original role description — applications closed
This role focused on AI-assisted code understanding, source-grounded explanations, evaluation and the infrastructure needed to make those features reliable. It does not imply that Xolvyn has trained or released a proprietary language model.
// Responsibilities
- Fine-tuning and training open-source base models (Llama, Mistral, CodeLlama) on codebase intelligence data
- Building and maintaining dataset pipelines for code understanding tasks
- Running model evaluation and benchmarking against accuracy and latency targets
- Working toward pre-training a custom model as the team and infrastructure scales
- Optimizing model inference for speed and cost (quantization, serving)
Previous application challenge.
We used this exercise during our hiring round. It's preserved here for transparency — it shows the kind of thinking we value.
View the archived challenge
Find any pull request on a public open-source repo — a real change, not a trivial one-liner. Then tell us two things: which parts of the codebase does this change touch, and what would you check or worry about before merging it?
That's the whole task. No special tools, no setup. A paragraph or two is plenty — we care how you reason about impact, not how long your answer is.
You read the source. We noticed.
Curiosity about how things are built is most of this job. You found the easter egg — nice work. Unfortunately, we're not hiring right now. Follow us on X to hear when we open new roles.