About Mobivangelism

What we do

Mobivangelism is the development partner on two significant products:

• Namola - "Uber for police"
• BrandChat - "the number one content management system for messenger apps"

We are currently staffing up both projects with great developers, in preparation of spinning each product off into its own company.

With Namola, we change the way the police takes care of crime.

With BrandChat, we change the way people interact with businesses to get stuff done.

Why Work For Us

We are driven to build, to create. We shape the world through code.

By bumping our heads several times by building cool things that fizzled (or in the words of a friend, "were constantly five years too early"), we've also learned the value of building things that can build sustainable user-bases and make money. We don't work primarily for money, but without income, creating things becomes... challenging.

We believe both Namola and BrandChat will make a difference to people's lives in big or small ways. Both provide plenty of scope for creativity and innovation. Both are interesting to work on. Both of them are already generating revenue. Both have received an enthusiastic welcome.

Joining either of our teams at this point allows you to be part of the core team building something big, but without the complete "pie-in-the-sky" uncertainty of a pre-revenue, pre-execution, pre-anything-really startup.

Our Culture

We're a startup. That means hard work, solving problems, learning new things, getting better every day.

Our culture is informed by the following values:

• Be honest. If you're struggling, tell us. If you don't understand something, tell us. If you disagree, say so (and explain why). If you're stuck for more than a couple of hours on something, ask for help. If you have a better idea, speak up. If you screw up, own it.
• Be curious. Learn by doing. Improve your own processes every day. If you find yourself spending time doing the same things over and over again, do some research and find a better way. Tell the rest of the team about it. Keep up to date with new frameworks and new tools. Never take the status quo for granted.
• Be creative. You join mobivangelism because you have the need to build, to create. When building software, we create things that people will love, that'll make them more efficient, that'll connect them in new ways, that'll make the world just a little bit better. And we do that through (mostly) just a small subset of ASCII characters. That's powerful and magical. Be a creator.
• Finish. 90% done is not done. 99% done is not done. Lots of really curious, creative, honest people struggle to maintain focus when the work gets sloggy towards the end. But you need to be able to dig deep, find the will-power, and just... finish.

We work remotely. It's not a perk. It's just what we do. Let's call it a selection filter. If you can work remotely, it implies:

• You can self-manage. We don't need to micro-manage every ticket in your list.
• You have experience. You probably don't need to tap someone on the shoulder every two minutes for help.
• You can learn on your own. You don't need to be taught.
• You're disciplined. You can roll out of bed at whatever time you roll out of bed, and get shit done productively without supervision.
• You have decent written and verbal communication skills.
• You're likely at a stage in your life where you like to do things on your own terms.

Having said that, when we get cabin fever, we meet up for an extended lunch and blow off steam. Whenever we need to plan a big chunk of new work, we sit down together.

Our Engineering Processes

We discuss.
We white-board.
We implement.
We test.
We iterate.
We deploy (continuously).
You break it, you fix it, you become more careful.
We talk to customers.
We improve.
We climb the mountain, one step at a time.

Our Hiring Process

You like us (in theory).
You get in touch with us.
We look at your sample work (public Github repos, prior work, pet projects, ...)
We like you (in theory).
We sit down for an extended lunch and chat in-depth.
We write a deployment script, and deploy our relationship to staging.
If no major bugs in the relationship are discovered (mutually), we deploy to production within three months.