1089 | Senior PHP Engineer (with strong DB experience)

Status
Open
Remote policy
Remote
Employment type
Not stated
Salary
Not stated
Categories
Senior-PHP-Developer, Backend-Development, Web-Development, Database-Engineering, Software-Engineer, Senior-PHP-Engineer, PHP-Engineer, Lead-PHP-Engineer, Senior-Full-Stack-PHP-Developer, PHP-Software-Engineer, Senior-PHP-Architect, Senior-PHP-Development, Senior-PHP-Tech-Lead, Team-Lead-PHP-Engineer
Tech
awsphp
Source
himalayas
First observed
2026-08-21 19:47 UTC
Last seen
2026-08-21 19:47 UTC
Source claims posted
2026-08-21 19:03 UTC
Consecutive misses
1 of 10

What the posting says

Intetics Inc., a global technology company providing custom software application development, distributed professional teams, software product quality assessment, and “all-things-digital” solutions, is seeking a highly skilled and experienced Senior PHP Engineer to join our dynamic team.

The client is a leading company specializing in advanced cybersecurity solutions. They provide comprehensive security measures designed to protect sensitive data and systems from cyber threats. Their offerings include vulnerability management, threat intelligence, incident response, and compliance management. With cutting-edge technology and a team of experts, they ensure robust protection for organizations across various industries, helping clients stay ahead of evolving cyber threats and maintain a secure digital environment.

About the project: The only Risk-Based Vulnerability Management Platform purpose-built for the world’s most complex enterprises.

This role is intended to be at the platform level, so "focus on data" in this context means -

Understanding the interaction between code and the database.

Understanding the interaction between code and our data. Our data isn't necessarily unique, but we deal with data at a large scale on a legacy codebase, and we need somebody who can come on-board and identify or prevent:

Code that suffers from off-by-one errors

Code that suffers from unnecessary exponential-time (O(n^2)) issues or is generally non-performant

Code that runs fast at a small scale but doesn't run fast at a large scale, or vice versa

Writing performant queries and best implementing the code to execute them.

Ability to audit existing queries and recommend improvements either to the query itself or to the code. For instance, maybe it's better to split a single query into two separate queries, execute them separately, and then write code to utilize the result sets together instead of doing a larger, slower, single query.

Understanding how the code and queries will scale together, and how they will continue to be performant as we continually increase the data by factors of 10.

Creating databases and recommending logical sort and shard keys as well as indexes. Understanding conceptually what these things mean and how to apply them.

Auditing or reviewing existing tables and recommending schema/architecture improvement

Requirements

Minimum of 5 years of professional experience in PHP development

Excellent knowledge of DB

Extensive experience working with large volumes of data

Experience in writing complex and optimized SQL queries

Excellent knowledge of modern versions of PHP

Experience working with relational databases (SingleStore/MemSQL a bonus)

Experience maintaining applications on Linux platforms in cloud environments

Background following Agile/Scrum methodologies in a professional setting

Demonstrated experience with technical troubleshooting

Ability to work independently and with a team, including with a team across different time zones

Would be a plus:

Experience working with vulnerability scanning technologies on any part of the tech stack (e.g., SCA, SAST, DAST, IAST, VM scanning, container, etc.)

Experience working in cloud environments, ideally AWS

Experience working with data analytics and/or data science

Originally posted on Himalayas

Quality

Completeness: 65%

Not enough history yet to judge honesty signals.

Timeline

  1. *
    #252237 2026-08-21 19:47 UTC
    Published
  2. o
    #256411 2026-08-21 21:48 UTC
    Not seen
    Miss 1 in a row