RECRUITER · TECHNICAL LEADER
You need to know what I can own.
Inspect the cases, the operating scope and the decisions I keep reviewable. Then write with the role, technical perimeter and decision authority.
RAN VALIDATION PORTFOLIO · TAKWA SEBAI
RAN validation that survives review.
Telecom technical manager with 10+ years across 4G/5G RAN validation, network OSS, automation and technical team leadership.
I connect the requested network state, the observed radio state, the decoded trace and the delivered service before I name a cause.
- 01ConfiguredWhat the network was asked to provide.
- 02ActiveWhat the UE and network actually activated.
- 03ScheduledWhat resources were made available in the same interval.
- 04DeliveredWhat the application and service finally received.
TWO DECISIONS · ONE PROOF BASE
Are you assessing the engineer or the product?
The evidence stays the same. The decision, and therefore the next useful action, does not.
OPERATOR · INTEGRATOR · PRODUCT BUYER
You need to know what HiCellTek changes in the workflow.
Follow the path from live capture and decoded signalling to a controlled test and an evidence handoff. Product claims stop at the same proof boundary as the engineering analysis.
SELECTED EVIDENCE
The conclusion stops at the first missing proof.
These records show the engineering decision, the decisive observation and the boundary that remains.
CASE 001 · CONTROL PLANE TO ACTIVE RADIO STATE
The command answered. The serving state still had to be proved.
- Decision
- Did the requested LTE target become the active serving cell?
- Positive evidence
- The target PCI became the active serving PCI during the controlled refresh.
- Boundary
- No internal modem root cause and no portability claim across modem families.
CASE 002 · 5G NSA THROUGHPUT VALIDATION
Ten uploads completed. That did not make ten comparisons valid.
- Decision
- Could BBR and CUBIC be compared while the 5G NSA bearer state changed?
- Positive evidence
- Only one run per branch met the pre-declared radio validity contract.
- Boundary
- No algorithm winner. The surviving sample was below the declared minimum.
PRODUCT PROOF · HICELLTEK
I did not stop at describing the field problem.
I founded HiCellTek and took an Android radio-diagnostics product from field need to commercial delivery. The mobile workflow brings serving and neighbour context, advanced radio parameters, decoded RRC or NAS messages and controlled HTTP tasks into one investigation path.
Engineering boundary: one application screen is an observation. A defensible RCA still needs aligned clocks, a controlled comparison and the first missing proof.
EXPERIENCE LEDGER
From network applications to a field product.
- 2014 → 2017
Freelance Telecommunications Software Engineer · Self-employed
Designed and evolved mobile and web applications, from requirements and functional or technical specifications to testing, acceptance, change management and user documentation.
- 2017 → 2019
Telecom Business Analyst · Novatel IT
Network-application validation, mobile anomaly reporting, BSS KPI analysis and quality-assurance plans.
- 2019 → 2020
Tech Lead · Davidson Telecom & IT, Lyon
Led a field telecom application project, a five-developer team, Agile delivery and code review.
- Since 2020
Founder · HiCellTek
Product design and development for automated 2G to 5G SA radio diagnostics, QoS/QoE analysis and supported Analyzer workflows.
- 2020 → today
OSS Network Technical Lead · SFR
Critical application subsystem, Cisco NSO and ZTP industrialisation on private cloud, multi-vendor delivery, KPIs and supplier governance.
WORKING SCOPE
What I can carry into a technical team.
- RAN validation
- Versioned test catalogues, multi-site campaigns, interoperability, regression, go/no-go, waivers and rollback.
- Trace and RCA
- RRC and NAS decoding, active-state verification, KPI baselines and synchronised evidence boundaries.
- OSS and industrialisation
- Critical network applications, automation, capacity, operability KPIs, private cloud and supplier handoff.
- Technical leadership
- Cross-functional arbitration, quality governance, expert coaching and decisions that remain reviewable.
PUBLISHED FIELD WORK
The methods are available for inspection.
Recruiters and engineering teams can read the same material I use to explain a decision boundary.
ONE MESSAGE · ONE DECISION
Tell me what you are deciding.
A useful first message names the role or product question, the technical perimeter and the next decision. No generic discovery call is required.