Why Fibmesh
Work on something people need to work.
Our mission: Make secure connectivity easier to understand, control and put to work.
A colleague needs an office application. A business needs a dependable public identity. An engineer needs to understand why a connection failed. Behind each task is a person trying to get something done.
Fibmesh grew out of broadband infrastructure. We’re taking that experience into a platform where people can define their connections in software, understand the access they create and change it as their work changes.
Explore our mission and vision ↗The work
Hard problems. Useful outcomes.
The work spans Networks, Publish, Public IPs and Outbound. Each begins with a customer’s task and reaches all the way into the systems that deliver it.
Make access a clear decision.
Help people understand what becomes reachable, who has permission and how to take access away. Bring product thinking, interface design and security judgment together.
Product · Design · SecurityRespect the network underneath.
Work through routing, addressing, DNS and tunnel behaviour across native platforms. The details matter when an ordinary change reaches a real device.
Networking · Systems · Native softwareHelp people know what happened.
Turn configuration, observed state and troubleshooting into something an operator can act on. A saved setting and a working connection are different things.
Backend · Quality · Service operationsNetworks, Publish, Public IPs and Outbound are available. Supported platforms and deployments continue to develop across the portfolio.
Look closer
One connection.
A whole system of decisions.
A person needs to reach a private application. Who owns it? Which device can connect? Where is the policy applied? What tells the operator it worked?
Explore the platform ↗- 01IdentityKnow the resource.
- 02PermissionDefine who can reach it.
- 03ExecutionApply the decision on the device.
- 04EvidenceUnderstand the result.
Our standards
Craft is in the decisions.
These are the principles guiding the product we want to build, and the qualities that work calls for.
Explain the consequence.
A good interface or API makes the effect of an action understandable. Clear language and thoughtful defaults are part of engineering.
Protect the boundary.
Access, private keys and privileged system changes deserve deliberate treatment. Make ownership and permission explicit.
Learn the platform.
A route on a laptop and a route on a gateway face different constraints. Good abstractions start with understanding the real system.
Finish the whole job.
Think beyond the successful first setup. Changes, failures, diagnostics and removal all belong in the design.
Your craft
Bring the way you see a problem.
There is more than one path into work like this.
Engineering & systems
Networking, native software, backend policy, APIs and deployment. Bring curiosity about what happens beyond your own layer.
Product & design
Turn a complex task into an understandable choice, a useful workflow and an explanation people can trust.
Quality & service operations
Ask what can fail, what the operator needs to know and how to verify the outcome under real constraints.
Customer & deployment knowledge
Understand the environment and help connect technical decisions to the work a customer needs to do.
Show your thinking
Let the work speak.
When a relevant role opens, a useful work example can show how you approach a problem: what you noticed, the choices you made, what you tested and what you learned.
- An engineering project with a clearly explained decision.
- A design or product case study that connects the problem to the outcome.
- A testing, troubleshooting or deployment example with evidence.
- Documentation or open-source work that helps others understand a system.
Share only material you have permission to disclose. Leave out customer data, credentials and confidential employer work.
Opportunities
The problems endure.
The roles evolve.
Role-specific openings and application instructions will be listed here when confirmed. Each listing will describe the work, location or working arrangement and how to apply.
Explore the work and the people behind it while future opportunities take shape.
Before you apply
A few useful questions.
What kinds of work does Fibmesh involve?
The platform brings together networking, native software, backend policy, product design, testing and customer deployment. The areas described above explain the work; confirmed role listings will define individual positions.
Where would I work?
Each confirmed role will state its location and working arrangement, so you can assess the fit before applying.
What should a work example include?
Explain the problem, your contribution, the decisions and the result. A small example with clear reasoning can be useful. Respect confidentiality and the original owner’s permission.
How will the application process work?
Each opening will explain how to apply, who to contact and how candidate information is handled. Check the opportunities section for confirmed roles and application details.