Production Has a Voice
Design decisions must survive real data volumes, imperfect inputs, downstream failures, support handovers, and change over time.
Careers at Bonyan System
Build Systems That Matter. Grow With the Work.
Join technical teams working on the data, revenue, and network platforms that telecom operations depend on.
Our work connects software engineering with real operational responsibility. You may trace an event across a mediation flow, investigate a billing difference, design a safer release, improve observability, or help an operator recover from a production issue.
We value people who stay curious, communicate clearly, and care about what happens after a system goes live.
The work
Complex Problems, Visible Outcomes
Telecom platforms are interconnected and operationally demanding. That makes the work challenging—and gives careful engineering a clear purpose.
Learning Crosses Boundaries
Engineers work across applications, data, infrastructure, telecom processes, testing, and operations—not inside isolated technical boxes.
Details Have Consequences
A field mapping, retry policy, pricing rule, deployment step, or missing alert can affect service and revenue. Precision matters.
Knowledge Should Travel
Useful documentation, thoughtful reviews, and patient explanation make both the platform and the team more resilient.
Ways to contribute
Technical Paths We Commonly Need
These are capability areas, not a promise that every role is currently open.
Software Engineering
Java, Python, PL/SQL, APIs, integration components, platform extensions, and operational tools.
Data Engineering
ETL/ELT, event pipelines, migration, reconciliation, data quality, warehousing, and analytics foundations.
Telecom Platforms
Mediation, charging, billing, settlement, provisioning, decisioning, and related BSS/OSS integration.
Platform and DevOps
Linux, databases, automation, CI/CD, observability, performance, availability, and production support.
Quality Engineering
Functional, integration, data, migration, performance, recovery, and release-readiness testing.
Analysis and Architecture
Requirements, process and data modeling, solution design, interfaces, delivery planning, and documentation.
How we work
What We Value in the Team
Tools can be learned. These habits are harder to replace.
Curiosity without pretending
Say what you know, what you do not know, and how you will find out.
Follow-through
Carry work through testing, documentation, handover, and the feedback that follows.
Clear communication
Make technical decisions understandable to the people who build, approve, and operate them.
Evidence over ego
Use logs, tests, measurements, and review to improve the answer—not defend the first idea.
What we offer
What You Can Expect From Us
The practical side of working here—the conditions that make demanding technical work worth doing.
Work that reaches production
You build for live operator environments, see your changes in service, and learn from how they behave.
Serious technical scope
Mediation, charging, settlement, provisioning, and data platforms at telecom scale—systems most engineers rarely get to touch.
Colleagues worth learning from
Reviews, design discussions, and support from engineers who have carried these platforms through go-lives and incidents.
Room to widen your range
Move between application, data, and operational work as your interests and the projects evolve.
Depth over churn
Long-running client engagements let you understand a system deeply instead of starting over every quarter.
Ownership that is recognized
Clear responsibility for your work, and credit when it holds up in production.
Introduce yourself
Show Us How You Think and What You Have Built
Send a concise CV and, where relevant, links to code, architecture work, technical writing, or a short description of a difficult problem you helped solve. Include the type of role you are interested in and your preferred working arrangement.
Applications are reviewed against active and upcoming needs. We may not have a matching opening at the time you contact us.
Email your application- 01Application reviewExperience, interests, and current needs
- 02Introductory conversationContext, availability, and mutual fit
- 03Technical discussionRelevant work, reasoning, and role expectations
- 04Engagement detailsResponsibilities, working model, and next steps