Instagram story viewer> @tecnophille> Posts

Oliver Samuel

@tecnophille

102

followers

116

following

Tech Professional with 6+ years hands-on experience 💼| Dedicated to driving innovation & embracing new challenges.

POSTS STORIES REELS TAGGED

by @tecnophille

1

0

16 days ago

Can we please stop creating designs like this? Like you can prompt the ai to do better, it cant be that too much of a work..

Can we please stop it? by @tecnophille

2

0

25 days ago

"Why do you think that you are the best candidate for the Staff Product Manager position?"

That question landed in the middle of the interview, and I felt the room go quiet for half a second, the kind of pause where you know your next 60 seconds matter more than the last 30 minutes combined.

I didn't flinch. I leaned in.

I talked about 8+ years spent moving between fintech, logistics, and enterprise delivery not as a spectator, but as the person building the systems underneath. I talked about leading AI-driven automation initiatives that touch core business processes end-to-end, not just dashboards and roadmaps. I talked about designing and shipping workflow solutions across multiple sites for a Fortune 500 logistics operation, where "downtime" isn't an abstract KPI, it's cargo sitting still. I talked about being the person who's equally comfortable in a stakeholder meeting and in the technical weeds of a system I helped architect.

I didn't just list achievements. I connected them to what a Staff PM actually needs to be: someone who can operate at altitude and still land the plane.

I didn't get the offer.

A few months later, that same company reached back out for the same role. This time they didn't want a process. They wanted to hire me directly. Only problem? I was already deep into another engagement.

Here's the lesson I keep coming back to:

Don't be afraid to talk about yourself in interviews. Not empty boasting, substantiated confidence. A subtle blow of your own trumpet, backed by receipts.

Because even when a "no" shows up, the impression you leave doesn't expire. Sometimes it just needs the right opening to circle back around. And when it does, you might find yourself being reconsidered, not for the role you interviewed for, but for something better.

Advocate for yourself like no one else in the room will. Because often, no one else will.

#CareerGrowth #ProductManagement #InterviewTips #SelfAdvocacy #StaffProductManager by @tecnophille

3

1

2 months ago

Spent the day at APICONF Lagos 2026 — this year’s theme, “Elevating API Literacy,” couldn’t be more relevant to the work we’re doing at Curably and Andora.

As founders, we talk a lot about products and go-to-market. But underneath every fintech and healthtech innovation coming out of this ecosystem is a simple truth: APIs are the connective tissue. Whether it’s Andora securing how AI agents move money, or Curably building the infrastructure for accessible health intelligence across Africa none of it works without solid, well-understood APIs.

Great to see GSMA, AsyncAPI, and Google for Developers backing this conversation in Lagos. The more our builders not just engineers, but PMs, founders, and operators understand APIs as a literacy and not just a technical implementation detail, the faster we close the gap between “we have an idea” and “we shipped it.”

Grateful to be in the room with people pushing this forward. 🇳🇬

#APICONFLagos #APIs #BuildInAfrica #Fintech #HealthTech by @tecnophille

5

0

3 months ago

Big news from us today: we have a new name.

For a while, we were building under "Cura ID." Today, we are officially Curably.

Here is the honest reason for the change.

Cura ID made it sound like we were building an identity verification tool. We are not. We are building the infrastructure that lets African healthcare actually work — the data layer that connects hospitals, HMOs, employers, government, NGOs, and faith-based health networks so that patient information flows safely, fraud becomes detectable, and care has real continuity.

That is a much bigger mission than a name about identity could ever carry. So we changed it.

What is staying exactly the same: our team, our mission, and every conversation we are already having with hospitals, HMOs, and partners.

What is new: the name Curably, a refreshed visual identity, and a clearer way of explaining what we do — Africa's AI-powered health intelligence infrastructure.

Curably African healthcare, rewired.

letscura.com

If you know someone working in healthcare, health insurance, or health policy in Nigeria or Kenya — tag them below. We would love for this to reach the right people.

#Curably #Rebrand #AfricanHealthcare #HealthTech #Nigeria #Kenya #DigitalHealth by @tecnophille

1

0

4 months ago

Mercor AI has allegedly been breached by Lapsus

939GB of source code
4TB of data in total
All data from their TailScale VPN by @tecnophille

1

1

7 months ago

Omg!! Will Remita ever recover from this?? by @tecnophille

2

1

7 months ago

The shift from Technical Architect to Business Strategist isn't just a change in title; it is a fundamental rewiring of how you define "success." Early in my career as a tech and product lead, my dopamine hit came from a clean deployment, an elegant system architecture, or solving a complex edge case that nobody else could crack.

I viewed the business requirements as constraints to work around rather than the heartbeat of the project. But as I transitioned deeper into product management and executive leadership, I realized that the most sophisticated architecture in the world is a liability if it doesn't move a business metric that matters.

The hardest part of this evolution was learning to let go of the "how" so I could obsess over the "why." As an architect, you are trained to build for every possible future, layering in scalability and modularity until the system is a masterpiece of engineering. As a strategist, you have to be comfortable with "good enough" technical debt if it means getting a product into a customer's hands fast enough to validate a market hypothesis. You start to see that code is a cost, not an asset, and that your real job isn't to build software, it's to build a sustainable, profitable engine that solves a human problem at scale.

This transition requires a unique kind of technical empathy that many pure strategists lack. Because I’ve been in the trenches as a lead, I know exactly what I’m asking of an engineering team when we pivot.

I understand the weight of technical debt and the cost of context switching. However, my responsibility now is to bridge that gap: to translate high-level business goals into technical reality without breaking the culture or the codebase.

High-value leadership in this space is about finding the intersection where technical feasibility meets market demand, and having the courage to kill a "perfect" technical project because it no longer serves the business strategy. by @tecnophille

5

0

7 months ago

BREAKING: Grokipedia has started to outrank Wikipedia on Google search results.

The downfall of Wikipedia has officially begun. by @tecnophille

0

0

8 months ago

The power of Seedance 2.0 is absolutely shocking
Seedance 2.0 can generate this type of effect.😗 by @tecnophille

3

0

8 months ago

Over the past few years, my career has taken turns I never fully planned for, but every step taught me something I needed.

I started out writing code and fixing systems. Then I found myself managing projects, working with product teams, and eventually leading technology and delivery. Somewhere along the way, I realized that what I enjoyed most wasn’t just building software. It was understanding the problem, aligning people, and turning chaos into something that actually works.

I’ve worked across startups and large organizations, in fintech, logistics, infrastructure, and consumer products. I’ve sat in rooms where things were breaking, deadlines were tight, and expectations were high. I’ve also been part of moments where a well-designed system made work easier for everyone involved.

Being a C-suite Engineer taught me how to think long-term, Product management taught me how to think clearly while Operations taught me how to stay grounded in reality. All of it shaped how I approach work today.

Right now, I’m focused on building and shipping products that solve real problems, especially in payments, platforms, and operational systems. I care about clarity, ownership, and doing things properly, even when no one is watching.

If there’s one thing I’ve learned, it’s that good products come from good thinking, honest collaboration, and a willingness to keep learning.

Looking forward to what’s next. by @tecnophille

2

0

9 months ago

Building in healthcare has taught me lessons I never learned in tech alone.

I came into health tech thinking the hardest problems would be engineering, scale, or infrastructure. I was wrong.

The real challenge is trust.

Healthcare is not just about software. It is about people at their most vulnerable moments. A delayed system, a broken workflow, or poor data handling does not just cause inconvenience. It affects care, outcomes, and sometimes lives.

One of the first things I learned is that innovation moves slower here for a reason. Regulation, caution, and resistance to change are not flaws. They are safeguards. When you understand that, you stop trying to “disrupt” everything and start designing with responsibility.

Another lesson is that interoperability matters more than features. A perfect system that cannot talk to other systems is almost useless. Hospitals, pharmacies, labs, and insurers do not work in isolation, so neither should the technology that supports them.

I have also learned that adoption matters more than ambition. If doctors cannot use it easily, they will not use it at all. If patients do not trust it, they will avoid it. Good health tech feels invisible. It fits into existing workflows instead of forcing new ones.

Finally, healthcare teaches patience. Progress is slow. Pilots take time. Approvals take longer. But when something works, the impact is real and lasting.

Building in this space has changed how I think about technology. It is no longer about speed or hype. It is about responsibility, clarity, and long-term value.

And honestly, that has made me a better builder. by @tecnophille

2

0

9 months ago