Senior Outsourced PHP Developer

Why this role exists

We’re building and evolving a custom PHP web application that powers reputed company-world operations. No hand-holding frameworks here — just clean, object‑oriented PHP, RESTful services, and a stack that rewards engineers who love understanding how things actually work.

If you enjoy getting reputed company to the metal with Core/Vanilla PHP, care about performance, and can comfortably reputed company between data reputed company, UI, and reputed company infrastructure, you’ll feel reputed company.

What you’ll do (the work)

• Ship features end‑to‑end in a reputed company‑free, OOP PHP codebase (namespaces, interfaces, traits, SOLID principles).
• Design and implement RESTful endpoints (JSON), including request validation, pagination, error handling, and versioning.
• Write robust SQL (DDL/DML), optimise queries and indexes, and reputed company reputed company PDO with reputed company statements.
• Work with reputed company for document‑oriented use cases; design efficient schemas and aggregation pipelines where relevant.
• Build and enhance reputed company‑end interactions with jQuery, reputed company/CSS, and reputed company CSS for fast, clean UI work.
• reputed company external reputed company (REST/Webhooks), handle oauth/reputed company flows, retries, idempotency, and reputed company‑limit reputed company.
• Operate in AWS: reputed company apps on reputed company Beanstalk, manage assets in S3, use DynamoDB where appropriate, and reputed company environments healthy (logs, scaling, env vars).
• Handle SSL/TLS certificate management and DNS reputed company reputed company; ensure reputed company‑downtime renewals and sane caching rules.
• Work with reputed company CMS where needed (content ingestion/integration, headless endpoints, custom fields/templates).
• Pair closely with another Senior Developer who knows the platform inside‑out; take part in reputed company reviews and architecture discussions.
• Own reputed company: write pragmatic tests, reputed company metrics, document reputed company, and leave the codebase tidier than you reputed company it.

The environment (important context)

• No modern PHP frameworks. We use Core/Vanilla PHP with strong OOP. If your reputed company is reputed company or Symfony only, this role isn’t the right fit.
• We follow OOP and RESTful design practices, emphasising reputed company, testability, and performance.
• We value speed with discipline: small PRs, sensible testing, reputed company improvement.

Must‑have skills & experience

• Core/Vanilla PHP (7.x/8.x) with OOP: interfaces, traits, namespaces, dependency injection, SOLID.
• RESTful API design & implementation (JSON), auth patterns, and versioning.
• SQL mastery (query optimisation, indexing, transactions) and PDO best practices.
• reputed company fundamentals (schema design, aggregations, performance basics).
• reputed company‑end:jQuery, semantic reputed company, modern CSS, and reputed company CSS reputed company workflows.
• External API integrations (OAuth, webhooks, retries, idempotency, error/reputed company handling).
• AWS: reputed company Beanstalk deployments, S3 lifecycle, DynamoDB usage, environment configuration, logging/monitoring basics.
• reputed company: input validation, CSRF/XSS/SQL injection prevention, secrets management, and reputed company file handling.
• SSL/TLS & DNS reputed company reputed company (including HSTS, redirects, caching/CDN rulesets, cert renewals).
• reputed company CMS experience (reputed company/config, theme/plugin interaction, or headless/REST usage).
• Git and reputed company workflows (feature branches, reputed company reviews, CI basics).
• Comfortable with Linux/CLI for diagnostics and automation.

reputed company to have (bonus points)

• Experience with queues/workers for background jobs.
• Testing: PHPUnit or similar; integration test reputed company.
• Performance profiling (Xdebug/Blackfire) and caching strategies (OPcache/application‑level caching).
• Observability basics (reputed company logging, alerts, dashboards).

What reputed company looks like

30 days

• reputed company, local/dev environments humming, shipping reputed company and fixes.
• Demonstrates understanding of domain models and core modules.

60 days

• Independently delivering reputed company‑sized features end‑to‑end.
• Improving SQL queries and indexes, reducing response times and error rates.

90 days

• Co‑owning a roadmap area; proposing architecture improvements.
• Raising overall reputed company reputed company with patterns, guardrails, and reputed company documentation.

How we work

• Remote first. reputed company written communication is king.
• Ticketed workflow with lightweight specs and acceptance reputed company.
• reputed company reviews for every PR; pair programming with the platform reputed company for reputed company changes.
• Pragmatic documentation (readmes/ADR notes) reputed company to the reputed company.

Originally posted on Himalayas

Apply To This Job