Backend Developer (Cloud Services)

You go on call for what you build, and you take your turn on the rotation. Engineering declares risk and timelines in writing for the business to accept, and that includes yours: when a date is at risk you say so early, with evidence, rather than quietly.

Responsibilities

• Own features end to end inside your team's domain. Work that runs for weeks, touches several parts of the system and other people's code, and ends in a live, monitored change. This is the level where the work stops arriving pre-broken-down: you are the one who names the unknowns up front rather than discovering them late.
• Write the specification before the code. Turn a request into something precise enough that an agent, or another engineer, builds the right thing the first time, and resolve ambiguity in writing with the person who asked.
• Run the AI harness every day. Use agentic tooling as the default way you work, automated review in the pull-request path, and reusable skills you build and share with the team rather than leave on your own laptop.
• Verify, and put the evidence on the pull request. Tests with every change, coverage gating on changed code, and failure cases exercised — not only the happy path. A reviewer should not have to take your word for it.
• Make your reviews worth having. With no authority, review is where much of your influence lands: catch the design problem while it is still cheap to fix, be specific about what to change and why, and be fast. Review latency slows the whole team down, and yours is part of it.
• Mentor engineers earlier on the ladder. Pair on the hard changes, explain the reasoning and not just the fix, and give feedback directly and early. You lead through design, code, and review, not through a reporting line.
• Own what you run, not only what you ship. Participate in on-call for your team's services, document incidents with actions closed on dates, remove toil rather than absorb it, and write down whatever only you know so no bus factor of one is left standing.
• Work in code you did not write. A hosting platform carries years of history. You will read your way into unfamiliar parts of it, change them safely without a rewrite you cannot justify, and leave each one better instrumented than you found it.
• Clear what you need from another team yourself. Find the dependency early, agree it directly with the engineer who owns it, and land it ahead of your work rather than escalating once it is late.

Requirements

• 5+ years of experience in software engineering, building and running production software, with real ownership of what you shipped after it shipped.
• 5+ years of experience with Perl or PHP.
• 5+ years of experience with relational databases.
• Depth in at least one part of a production system, and the ability to read your way into a part you have never seen. You can read a diff in a language you do not use daily and identify what is wrong with it.
• Hands-on AI-assisted engineering in your daily work rather than as a trial. You can specify precisely, review generated code critically, and explain where it fails and what you always check before it merges.
• Tests and evidence as a habit rather than a mandate. You write them as you go, gate on changed code, and have caught your own mistakes with them.
• Experience operating what you built. You have participated in a production on-call rotation, owned an incident, and contributed to a write-up that changed something afterwards.
• Clear written communication in a remote, distributed team. You record decisions and trade-offs in writing and work effectively with colleagues across several time zones.

Preferred

• 5+ years of experience with CDN, WAF, and server security
• Experience in managed hosting, cloud, or another high-availability service business.

Employee perks and benefits

• work in a team of professionals at international level;
• opportunity to practice and improve your English;
• excellent pay and all necessary equipment;
• remote work;
• employee referral program with bonuses for successful referrals;
• support of legalization if needed.

Requirements for the employee

The job is suitable for:

• People who fled from war conflict

Minimum education required: University education (Bachelor's degree)

Language skills: English - Upper intermediate (B2)

Other knowledge:

• Perl - Skillful
• PHP - Advanced