Performance work is detail work. At Cyberex Labss, the people who do it best are the ones who get genuinely annoyed by a 400ms frame drop or an unexplained memory spike at 3am on a Tuesday.
Founded in 2025, we work directly with product teams on mobile apps that need serious optimization — not surface-level fixes, but root-cause analysis across iOS and Android stacks. We are looking for specialists who already know the difference.
Each role is focused on a specific layer of mobile performance. Read carefully — we are not looking for generalists, and the descriptions are intentionally specific.
Diagnose startup latency, memory pressure, and rendering issues in Swift/Objective-C codebases. Use Instruments, MetricKit, and custom profiling scripts to identify what is actually slow — not just what looks slow.
Apply nowWork at the ART layer — GC tuning, Doze mode edge cases, Choreographer frame timing. Kotlin or Java, either works. What matters is that you can read a Systrace output without getting lost.
Apply nowReact Native and Flutter apps have their own performance failure modes — bridge overhead, Dart isolate scheduling, JS thread blocking. We need someone who has debugged these in production, not just in tutorials.
Apply nowHTTP/3, connection pooling, payload compression, retry logic — mobile network conditions are unpredictable and most apps handle them poorly. Map the failure modes, then fix them systematically.
Apply nowWrite reproducible performance test scenarios, maintain baseline benchmarks, and flag regressions before they reach production. Familiarity with Firebase Performance or Datadog mobile SDK is a plus.
Apply nowTranslate performance audit findings into language that product managers and CTOs can act on. Requires both technical depth and the ability to write a one-page summary that does not lose anything important.
Apply nowAsync by default, with two fixed sync points per week. Nobody tracks hours — output and communication quality matter more than when you were online.
Code reviews are direct and specific. If something is slow or fragile, we say so with a concrete reason. Feedback is not personal, and good arguments change decisions regardless of seniority.
Every claim in a report needs a measurement behind it. "It feels slow" is not a deliverable — a Instruments trace with annotated frames is.
When we choose one approach over another, we write down why. Future team members — including yourself in six months — will thank you.
Clients come to us with real deadlines. We scope honestly, communicate blockers early, and do not overpromise on what a single sprint can fix.
Write to help@cyberexlabss.com with the role name in the subject. Include a short note on one specific performance problem you have debugged — what the symptom was, what the cause turned out to be, and how you found it.
A 45-minute call with one of our engineers. No whiteboard algorithms — we look at real profiling output together and discuss what you see. Bring a past trace or benchmark if you have one.
A small paid task — typically 3 to 4 hours — based on a real (anonymized) client scenario. The goal is not perfection, it is to see how you approach an unfamiliar codebase and communicate findings.
If both sides want to move forward, we send an offer within two business days. Onboarding starts the following Monday with the structured week you see above — no surprises, no sink-or-swim first day.
