/ TEAMS · Specialist engineering · MySQL
Source engineers experienced in InnoDB transactions, replication, indexing and production query performance. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
InnoDB locking
EXPLAIN query plans
replication GTID
online schema migration
buffer pool tuning
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid-level MySQL Engineer
Available3+ years of experience · Poland
MySQL Engineer with 3 years in production systems, focused on InnoDB locking and EXPLAIN query plans.
Languages: Polish, English C1
Mid+ MySQL Engineer
Inquire availability7+ years of experience · Bulgaria
MySQL Engineer with 7 years in production systems, focused on EXPLAIN query plans and replication GTID.
Languages: Bulgarian, English B2+
Senior MySQL Engineer
Inquire availability13+ years of experience · Bulgaria
MySQL Engineer with 13 years in production systems, focused on replication GTID and online schema migration.
Languages: Bulgarian, English B2+
Senior MySQL Engineer
Available8+ years of experience · Serbia
MySQL Engineer with 8 years in production systems, focused on online schema migration and buffer pool tuning.
Languages: Serbian, English B2+
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of InnoDB locking, EXPLAIN query plans, replication GTID helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
MySQL responsibilities include innodb locking, related explain query plans, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
MySQL responsibilities include explain query plans, related replication gtid, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
MySQL responsibilities include replication gtid, related online schema migration, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
MySQL responsibilities include online schema migration, related buffer pool tuning, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
MySQL responsibilities include buffer pool tuning, related backup recovery, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
MySQL responsibilities include backup recovery, related innodb locking, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Resolve lock contention in checkout workloads. Define constraints around innodb locking, map dependencies and test how the proposed implementation behaves under real operating conditions.
Modernize a large relational schema. Define constraints around explain query plans, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve replicas and failover procedures. Define constraints around replication gtid, map dependencies and test how the proposed implementation behaves under real operating conditions.
Restore database consistency after an incident. Define constraints around online schema migration, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving InnoDB locking and what evidence led to a fix.
Which decisions around EXPLAIN query plans and replication GTID were you personally accountable for?
Describe a production issue involving replication GTID and what evidence led to a fix.
Which decisions around online schema migration and buffer pool tuning were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to InnoDB locking. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
