Engineering Manager

Engineering Manager

Build the engineering system behind products used by millions.

Mobiways is a fast-growing startup building AI-powered mobile and web products at the intersection of Productivity and Wellness.
Our products help people think clearer, feel better, and get more done — from AI assistants to mental health tools and psychological assessments.
Our flagship product, Genora AI, is already 5+ million users worldwide.
Now we're scaling the next generation of our products — and we need an Engineering Manager who can help us move faster without losing control. We're looking for someone who can own the whole engineering system: people, delivery, architecture, processes, tools, incidents — and increasingly, AI.

---

What you'll own

🚀 Delivery

Your job is simple to describe: get the right things shipped, at the right quality, at the right time.
You'll own the engineering side of turning business priorities into shipped products.
You'll:

• Own planning and prioritization across the engineering team.
• Build a delivery process that actually works — Scrum, Kanban, hybrid, or something better.
• Turn big, ambiguous initiatives into executable pieces.
• Challenge unrealistic estimates and make delivery risks visible early.
• Remove blockers before they turn into fires.
• Manage dependencies between teams and functions.
• Balance speed, quality, technical debt, and business impact.
• Make sure the team is spending its limited engineering capacity on the things that matter most.

We don't care what methodology you put on the wall.
We care whether things ship.

---

👥 People

You'll be the direct manager for our developers and QA engineers.
And we're serious about this part.
You'll:

• Run meaningful 1:1s — not status meetings disguised as 1:1s.
• Know who's overloaded, who's disengaged, who's growing, and who's at risk of burning out.
• Hire great people and make tough calls when someone isn't working out.
• Understand people's strengths and weaknesses and use that knowledge when assigning work.
• Give people challenges that help them grow instead of constantly plugging the nearest hole.
• Build a team that becomes stronger every quarter.
• Handle conflicts directly instead of escalating every uncomfortable conversation.

Your goal isn't to make everyone equally busy.
Your goal is to build a team that performs at a high level and keeps getting better.

---

🧠 Technical leadership

You don't have to be the best engineer in the room.
But you need to be technical enough to know what questions to ask and when something doesn't make sense.
You should be able to:

• Understand architecture at a level where you can challenge decisions and discuss trade-offs.
• Evaluate whether an engineering estimate is realistic.
• Spot technical risks before they become delivery problems.
• Understand why a team is making a particular architectural choice.
• Help engineers make better decisions without micromanaging implementation.

Mobile experience is a big plus — especially iOS / Android.

---

🧩 Architecture across multiple products

We are not building just one product with one codebase.
As our portfolio grows, one of the biggest engineering challenges is making sure we reuse what should be reused instead of rebuilding the same thing five times.
You'll help us:

• Identify common modules, services, integrations, and infrastructure.
• Decide where standardization makes sense.
• Allocate engineering capacity to shared components.
• Reduce duplicated work across products.
• Build an engineering architecture that can support a growing product portfolio.

You'll constantly ask:
“Do we really need to build this again?”

---

🤖 Make AI part of how we work

This is one of the most important parts of the role.
We don't want someone who has tried Cursor once.
We want someone who is genuinely curious about what engineering looks like when AI becomes part of the default workflow.
You'll own the evolution of our AI-enabled engineering organization.
That means:

• Building and evolving the AI tool stack for engineering — Cursor, Claude Code, Copilot, and whatever comes next.
• Looking for AI opportunities beyond engineering: QA, design, analytics, operations, etc.
• Experimenting with new models and tools.
• Measuring whether they actually make us faster or better.
• Redesigning workflows around new AI capabilities.
• Finding processes that can be automated — or eliminated entirely.
• Understanding AI both as a product capability and as an operating model for the company.

We expect you to be the person asking:

“Why are we still doing this manually?”

And then actually doing something about it.

---

🔬 Own R&D

Part of your job will be figuring out what we should learn before we build.
You'll:

• Identify areas where technical research is needed.
• Define research questions and experiments.
• Run investigations yourself when that's the fastest option.
• Bring in the right specialists when it isn't.
• Turn research into concrete engineering and product decisions.

We value people who are comfortable saying:
“We don't know yet. Let's find out.”

---

🔥 Engineering operations

Someone has to make sure the machine keeps running.
You'll own the operational layer of engineering:

• Development and engineering tooling.
• Accesses, licenses, subscriptions, and vendor management.
• Technical services and infrastructure-related processes.
• On-call.
• Incident management.
• Post-incident improvements.

The goal isn't zero incidents.
The goal is an organization that gets better every time something breaks.

---

What we're looking for

You probably have:

• 3–5+ years as an Engineering Manager, Team Lead, Delivery Manager, or similar role with direct people management.
• A background in commercial software engineering — backend or full-stack — before moving into management.
• Enough technical depth to discuss architecture and evaluate engineering estimates.
• Experience working in a product company, startup, or mobile-first environment.
• Experience managing a team that supports multiple products or initiatives is highly valuable.
• Real experience using AI tools in your own work.
• A strong understanding that AI isn't just another tool — it changes how teams should work.

You should be comfortable with:

People + Product + Technology + Operations
You don't need to be the deepest expert in every one of these areas.
But you should be able to connect them.
For example:

“This architecture decision will add two weeks of engineering work, we're already overloaded, it blocks the mobile release, and we can probably solve 80% of the problem with a shared service we already have.”

That's the kind of thinking we're looking for.

---

Nice to have

• Experience with subscription-based mobile products.
• Knowledge of App Store / Google Play billing and in-app purchases.
• Experience optimizing LLM API / AI inference costs.
• Experience managing several products with a shared engineering organization.
• Experience scaling engineering processes in a rapidly growing startup.
• A strong habit of experimenting with new AI models, developer tools, and automation.

---

How you'll measure your success

Six months in, we'd expect to see things like:

• Engineering delivery is more predictable.
• Important things ship faster.
• Priorities are clearer.
• Fewer blockers are allowed to linger.
• Engineers spend less time on low-value manual work.
• Shared components are reused instead of repeatedly rebuilt.
• The team is growing stronger and more autonomous.
• Incidents are handled systematically.
• AI is embedded into everyday engineering and adjacent workflows.
• You have helped us discover and implement entirely new ways of working.

Ultimately:
You make the engineering organization capable of moving faster than it was before you joined.

---

Why Mobiways?

🌍 Millions of users

Our flagship product is already 5+ million users worldwide. Your decisions won't live in Jira — they'll affect products used by real people at scale.

⚡ Startup speed

We're small enough that your decisions matter immediately.
No six-month approval process.
No endless alignment meetings.
If something makes sense, build it.

🤖 AI-native environment

We're building products with AI — and we're also rebuilding the way we work around AI.
If you're excited about where engineering is going next, you'll have plenty of room to experiment.

🏗 Real ownership

You won't be handed a perfectly designed engineering organization.
You'll help build the system itself.
Processes.
Team.
Architecture.
Tools.
AI workflows.

🌴 Remote-first

Work from home, a coffee shop, the beach — wherever you do your best work.

🕐 Flexible hours

We care about ownership and outcomes, not whether you're online at 9:00 AM sharp.

💰 Competitive compensation

We offer a competitive remuneration package based on your experience and impact.

🏖 Time off

20 vacation days and 5 sick days per year.

---

One last thing

This role is probably not for you if you want to spend most of your time managing Jira boards, running ceremonies, or forwarding problems to someone else.
It might be for you if you enjoy:

• turning chaos into a system;
• building high-performing teams;
• understanding technology without needing to write every line of code;
• making difficult decisions;
• shipping products;
• experimenting with AI;
• and asking “how can we do this 10x better?”

If that sounds like you, let's talk.