VulCode

Developer jobs at VulCode: applications open all year round

We have no single seat to fill today, but we want to know developers we could work with on client projects and our own products. You can send an application at any time.

vulp in a terminal: an overview of repositories, recent commits, todos, pull requests and issues
: vulp, our tool for working across many repositories at once

What our code is written in

Each language's share of the code in our repositories and the number of projects it appears in.

  1. TypeScript50%51 projects
  2. Rust18.5%11 projects
  3. Go5.3%13 projects
  4. Kotlin3.8%7 projects
  5. C#3%8 projects
  6. JavaScript2.7%38 projects
  7. PHP2.4%6 projects
  8. Swift2.2%4 projects

What we work on

Our own products, developed alongside client work. Real screenshots.

  • Gyred: a list of AI agent sessions, a conversation with a session and changes to a file

    Gyred

    A control room for many AI agent sessions at once, with desktop and phone clients.

  • The Flaem panel dashboard: revenue, active clients, server nodes and the cases waiting for a person

    Flaem

    A platform for hosting companies: a panel, a site and native apps.

Your tasks

What you will work on day to day. We fit the scope to the time you have.

Developers
The best application is code that can be read.

Projects

  • Client projects
  • Our own products

Websites, stores, panels and integrations, from taking over existing code to new systems. Flaem, Plazer, Gyred and industry platforms, developed alongside client work.

Code and review

  • Open source
  • Code review

Fixes and features in projects we use ourselves. Every change is reviewed before it goes into a project.

After handover

  • Servers and deployment
  • Documentation

A project has to work after handover, so deployment is part of the job, not an extra. Code has to be possible to take over without calling its author.

What this role is about

What we do

We build websites, panels, mobile and desktop apps, integrations and bots, and next to that our own products: Flaem for hosting companies, the Plazer messenger and the Gyred panel for AI agents. We also contribute to other people's open source projects.

When to write

If you write in something that is in our code and want us to remember you for the next project, write to us. An application with a link to a repository tells us more than a CV.

Details of the role

Everything that is certain about this role, in one place.

Developers

Area
Technology
Work mode
Remote, we have no office
Languages
Polish and English
Who you work with
The VulCode team
Applications
hello@vulcode.com
Pay
A commission on contribution and results, not on time

What happens after you send it

1You send an email

To hello@vulcode.com, with the role in the subject line and examples of your work.

2We read it

The application goes straight to the person you will work with, with no HR department in between.

3An online call

A short call in Polish or English about what you do and how you see the role.

4We agree on the scope

How much time, which tasks to start with and how we settle up, before you begin.

Probably not if

You want a permanent full-time position straight away. You have no code you could show. You do not want anyone reviewing your changes.

Questions about this role

Questions about this role before you apply.

Other roles

We are looking for other people too. The nearest to this role is Client Relations.

Apply with one email

A few sentences about yourself and links to what you have already done. The subject fills itself in. It is for you if:

  • You have public code or a project you can show
  • You write in something that is in our code
  • You finish things, deployment included
  • You read the docs before you ask

No mail app? and the role's name fills itself in.

Tohello@vulcode.com
SubjectApplication: developer

Hi, I am sending an application as a developer.

  1. What I write in: languages and frameworks.
  2. Code: a link to my GitHub or a repository I am happy with.
  3. The project I am proudest of, in two sentences.
  4. How much time I can give and from when.