Our Engineering Philosophy
How we think. How we build. How we work together.
This is a public statement of the principles that guide how we build at Jodo. We are sharing them because engineering culture is shaped by the choices a team makes, especially when a rule or process cannot supply the answer.
At Jodo, engineering is more than writing code, delivering features, or closing tickets. We are here to solve meaningful problems, build reliable systems, and create products that make a difference.
These are not rules to follow mechanically. They are principles for exercising judgment when the path is unclear, the trade-offs are real, and the easy answer is not necessarily the right one.
Our philosophy is simple:
High Performance. High Respect. Zero Compromise.
These are the seven principles we hold ourselves to.
1. Don’t Be a Jerk
Be demanding about the work and respectful toward people. Great engineering requires strong opinions, difficult conversations, and high standards, but none of these justify arrogance or disrespect. We should challenge weak designs, question decisions, and give direct feedback in ways that improve the work without diminishing the person.
That means respecting people regardless of role, title, or experience, and giving feedback directly enough to be useful and constructively enough to be heard. Technical expertise is never an excuse for arrogance.
Our standard: Being technically brilliant does not excuse poor behaviour.
2. Be Honest, Even When It’s Hard
Truth over comfort. Transparency over appearances. Engineering decisions depend on accurate information, and a hidden production issue, unrealistic estimate, or unspoken concern can become far more expensive than an uncomfortable conversation today.
Surface problems, risks, and uncertainty early. Admit mistakes without obscuring their impact, give honest estimates, and challenge decisions that appear technically unsound. If something is broken, say so. If you do not know, say so. If you made a mistake, own it.
Our standard: No hidden surprises. No false confidence.
3. Own It. Lead by Example
Ownership is demonstrated through actions, not titles. It does not end when code is merged or a ticket is marked complete. It means understanding whether the work solved the intended problem and behaves reliably in production.
Understand the problem before accepting the task, then think beyond the immediate code change. Consider testing, reliability, observability, and maintainability. Follow through until the problem is resolved, or make its remaining risk explicit.
If you see a problem, raise it constructively. Suggest a better approach, help solve it, or take responsibility for driving the improvement. Critique should move the work forward, not become commentary from the sidelines.
Our standard: Don’t just point at problems. Help move them toward solutions.
4. Think Deep. Start From First Principles
Understand why before deciding how. We do not want engineers to follow patterns just because they are familiar or another company uses them. We want engineers who understand the fundamental problem.
Before designing a solution, ask what problem we are actually solving and what we know to be true. Examine the assumptions we are making, look for the simplest solution that satisfies the requirements, and consider what happens when the system grows, fails, or behaves unexpectedly. First-principles thinking does not mean reinventing everything. Established patterns, frameworks, and technologies are valuable when we understand their trade-offs before adopting them.
Go deep enough to understand the problem, the system, and the consequences of your decisions. Avoid unnecessary complexity and superficial fixes.
Our standard: Question assumptions. Understand fundamentals. Solve root causes.
5. Move Fast. Stay Disciplined
Speed matters, and so does engineering quality. We want engineers who can distinguish between decisions that require deep investigation and those that can be made quickly and iteratively.
Prefer simple, maintainable solutions and break large problems into smaller deliverables. Test according to the risk and impact of a change, communicate blockers and delivery risks early, and avoid overengineering or unnecessary process.
Engineering discipline should enable speed, not become an excuse for avoiding decisions.
Our standard: Move with urgency. Build with care. Deliver consistently.
6. Challenge Ideas. Respect People
The best idea should win, not the loudest voice or highest title. Engineering improves through thoughtful disagreement, so we challenge designs, architecture decisions, assumptions, and existing systems.
A junior engineer should feel comfortable questioning a senior engineer, and a senior engineer should be willing to reconsider a decision when presented with better evidence. Debate ideas with reasoning and evidence, explain trade-offs rather than asserting preferences, and listen to understand. Disagree openly and respectfully, then commit once a decision is made unless new evidence warrants revisiting it. We challenge ideas because we care about getting things right.
Our standard: Strong opinions. Sound reasoning. Intellectual humility.
7. Raise the Bar. Together
Great engineering teams make everyone better. Engineering excellence is not just about individual brilliance; it is about creating systems, practices, and an environment where everyone can consistently produce great work.
It asks each of us to continuously improve while helping others grow. Write code that others can understand and maintain, document important decisions, give thoughtful code reviews, share knowledge, and learn from teammates. Improve developer experience and leave systems better than you found them.
The goal is not to be the smartest engineer in the room. It is to build a team where everyone’s capabilities keep improving.
Our standard: Make yourself better. Make the team better. Make the systems better.
A Note on Leadership
Leadership is not limited to engineering managers or technical leads. Every engineer leads through judgment, initiative, accountability, and example. The higher your responsibility, the higher the standard you must demonstrate.
Leaders create clarity, develop people, make difficult decisions, and demonstrate the behaviours they expect from others. Leadership is not telling people to raise the bar. It is showing them what a higher bar looks like.
Our Engineering Commitment
We will not always make the right decisions. We will make mistakes, move too slowly, introduce complexity, miss important details, and disagree on the best approach.
What matters is how we respond: acknowledge mistakes, learn from them, improve our systems, and hold ourselves accountable. We do not pursue perfection at the expense of progress or speed at the expense of responsibility.
Think Deep. Move Fast. Own Outcomes. Raise the Bar. Respect People.
That’s how we want to engineer at Jodo.
If this is the kind of team you want to be part of, we’d like to hear from you. Write to us at careers@jodopay.com.
