Craft over volume
We would rather ship one thing that holds up for three years than five that need watching. Reviews are slow on purpose.
Careers at EGPHP
Come build the infrastructure other people rely on
We run Nginx hosting, the EGPNL control panel and dedicated servers for hundreds of businesses across Egypt and the region. Small team, real systems, work you can point at.
What you would actually work on
No abstractions: this is the stack that serves the customers.
Live infrastructure
Nginx hosting, VPS and dedicated servers with real uptime commitments. What you ship is what customers run on the same day.
The EGPNL panel
Our own control panel: provisioning, SSL automation, databases, mail and monitoring. A product, not a ticket queue.
Security and reliability
DDoS protection, backups, isolation and incident response. Work where being careful is the point of the job.
Customers you can hear
Support and engineering sit together. You will know within hours whether a decision helped somebody.
Which part of the stack fits you
Tell us what you like doing most and see where it lands. Nobody stays in one lane for long, so this is a starting point, not a box.
- If you likeKeeping servers steady while traffic is notStart withLive infrastructure
- If you likeBuilding the tool other people use every dayStart withThe EGPNL panel
- If you likeAssuming something will fail and preparing for itStart withSecurity and reliability
- If you likeSeeing the effect of your work the same dayStart withCustomers you can hear
- If you likePHP and Linux, but not sure where to startStart withSend an open application
How we work
Three things we actually hold to.
Remote-friendly, on-call honest
Work where you think best. Infrastructure has nights and weekends sometimes — we say so up front and we rotate it fairly.
You grow into the whole stack
A small team means nobody stays in one lane. Expect to touch PHP, Linux, networking and the product itself.
Open roles
Nothing posted right now — but the door is not closed.
No open positions this month
We hire when the work needs somebody, not on a calendar. Send what you have built and we will keep it on file — we read every one.
Send an open applicationA short checklist for a strong application
Nothing here is a hidden test. It is what makes a message easy to read and easy to answer.
Say what you built, not only what you used
Link one thing that runs, or describe it: what it does, who uses it and what broke along the way.
Name the part of the stack that pulls you
Pick one of the areas above, or say none fits. It tells the reader where to start.
Show how you debug
One paragraph on a problem you chased down to its cause says more than a list of tools.
Say how you like to work
Your time zone, remote or in person, and how you feel about an on-call rotation shared fairly.
Keep it short
One page is enough. A person reads it, so write it for a person.
What happens after you write
- We read it properly A person reads your mail, not a filter. Expect a reply either way within a week.
- A conversation, not a quiz One call about what you have built and what you want to build next.
- A real task, paid A small piece of actual work on a copy of our stack, scoped to a few hours. We pay for your time.
- An offer with the details written down Salary, on-call, equipment and expectations in writing before you decide.
