Senior engineering opportunity
A remote Android, Flutter or full-stack role that needs architecture judgment, practical execution and responsibility beyond isolated feature work.
Contact · roles · products · systems
Let’s make the next technical decision clear.
Contact me about a senior engineering role, a mobile product that needs stronger ownership, an automation workflow or an existing system that is difficult to operate. Start with the current situation and the outcome you need—not a perfect specification.
Choose a direct channel
Reach me in the way that fits your enquiry.
WhatsApp is useful for an initial conversation, a phone call works when speaking is faster, and email is best for detailed briefs or attachments.
WhatsApp conversation
Best for a concise introduction, an early product discussion or deciding whether a longer technical conversation makes sense.
Message +255 754 777 754 →Direct phone call
Use this when a spoken conversation is the clearest next step. On supported devices, the link opens your dialer and lets you choose whether to call.
Call +255 754 777 754 →Email a detailed brief
Best for role descriptions, product requirements, links, architecture context or material that should remain easy to reference.
support@mahando.com →Good reasons to reach out
Conversations where I can contribute meaningful technical ownership.
A clear fit matters more than the size of the request. These are the situations where my combination of mobile engineering, backend work, automation and product operations is most useful.
Existing product needs direction
A mobile product has accumulated technical risk, unreliable workflows, release friction or unclear ownership and needs a structured path forward.
New product or product family
An idea needs to become a maintainable application and operating system—from architecture and interface through backend services and release.
Automation or technical review
A repetitive data, publishing or operational workflow needs automation, or an important technical decision needs an independent engineering review.
Before you send the message
A small amount of context creates a much better first conversation.
What to include
You do not need a formal brief. A clear first message can be short when it covers the essentials.
- The role, product, system or workflow you want to discuss.
- What exists today and the specific constraint or risk you are seeing.
- The outcome you want and why it matters to users or the business.
- Any useful timeline, links, screenshots, documentation or technical context.
- The kind of involvement you expect: review, implementation, ownership or an ongoing role.
What you can expect
I review serious enquiries directly and use the first exchange to understand fit, scope and the most useful next step.
LocationTanzania · East Africa Time (UTC+3)
Working modelRemote international roles and focused product engagements
CommunicationClear written context first; calls when they add value
ScopeEngineering, product operations, automation and technical review
PrivacyDo not send passwords, API keys or confidential credentials
Ready when the context is clear
Start with the problem. We can determine the right next step together.
A thoughtful first message is enough. I would rather understand the real situation than receive a polished brief that hides the important constraint.