Culture & Values
We're building something significant. Our culture reflects our commitment to quality, honest collaboration, and continuous improvement. We value partners over praise singers, data over assumptions, and fixing systems over patching symptoms.
What We Believe
**Fix the Source, Not the Symptom**: The TOOLING-FIRST principle extends beyond code. When something goes wrong, we don't patch around the problem—we understand why it happened, fix the system that allowed it, and prevent it from happening again. This applies to processes, communication, and decisions—not just software.
**Quality is Non-Negotiable**: We don't ship with known bugs. We don't ignore warnings. We don't "fix it later." Compiler warnings are bugs, linter warnings are bugs, test failures are blockers, and technical debt is tracked, not ignored. This isn't perfectionism—it's professionalism. Quality accumulates. So does its absence.
**Be a Partner, Not a Praise Singer**: Honest feedback is valuable. False agreement is harmful. Push back respectfully. Disagree constructively. Never pretend something is fine when it isn't.
**Measure, Don't Assume**: "I think it's faster" → Measure it. "This should work" → Test it. "We've always done it" → Question it. "Everyone knows that" → Document it. Intuition is a starting point, not a conclusion. Data resolves debates.
**Teach to Learn**: The best way to master something is to explain it. Document what you learn. Share patterns with the team. Review others' work carefully. Ask questions openly. Knowledge hoarding is a failure mode. Knowledge sharing is how we compound capability.
How Gen AI Changes Your Work
AI generates XML from specification, tests boilerplate once, encodes patterns in tools, automates validation, and generates documentation with code. Your expertise shifts, not disappears. Less time on boilerplate and debugging, more time on architecture decisions and business logic design.
**The AI amplifies your judgment. It doesn't replace it.**
What we expect: (1) Use the tools—don't reinvent what exists, (2) Improve the tools—every project should strengthen the platform, (3) Document the patterns—your knowledge becomes institutional memory, (4) Challenge the AI—push back when suggestions are wrong, (5) Stay curious—the tools evolve; so should you.
Working Together
**Communication Norms**: Blocked on something? Ask for help within 1 hour. Found a bug? Log it immediately, even if minor. Learned something useful? Document it. Disagree with a decision? Raise it directly, with reasoning. Made a mistake? Own it, fix it, improve the system.
**Meeting Culture**: Daily standups (quick, focused, 15 minutes max), weekly reviews (what shipped, what learned, what's next), retrospectives (continuous improvement, blameless), and no-meeting time to protect focus time.
**Remote-First**: We work effectively across time zones and locations. Async by default—don't assume immediate availability. Document decisions—if it's not written, it didn't happen. Video for nuance when text isn't enough. Overlap hours for some shared time for real-time collaboration.
Career Growth
Growth comes through demonstrated capability, not time served: (1) Deepen expertise—become the expert in your area, (2) Widen impact—build tools others use, (3) Teach others—your knowledge becomes institutional memory, (4) Take ownership—volunteer for hard problems, (5) Ship results—working software trumps perfect plans.
Quality Over Speed
But speed matters too. We deliver fast, but never at the expense of quality.
Fix Systems, Not Symptoms
TOOLING-FIRST in everything. Address root causes, not symptoms.
Honest Over Nice
But respectful always. Direct feedback strengthens the team.
Data Over Opinion
But judgment when data is insufficient. Measure to resolve debates.
Ownership Over Handoff
See it through. Take responsibility for outcomes, not just outputs.
Why Predictiv
You'll Love It If You...
Get satisfaction from elegant solutions, prefer understanding to memorizing, like building tools, communicate directly, and take ownership.
You'll Struggle If You...
Need constant validation, prefer the old way because it's familiar, want detailed instructions for everything, avoid conflict rather than addressing issues, or see documentation as someone else's responsibility.
Growth Paths
Individual Contributor Track (Developer → Senior → Staff → Principal), Management Track (Developer → Tech Lead → Engineering Manager → Director), Specialist Track (Developer → Domain Expert → Platform Architect).
Remote-First Culture
Async by default, documented decisions, video for nuance, overlap hours for collaboration.
Ready to Join Our Team?
We're building something significant. Be part of transforming enterprise software in Africa.