Something you made.
A product, a piece of code, a design or a written idea. Help us understand the decisions behind it.
Good work starts
with curious people.
Interested in the problems we’re working on? Introduce yourself, show us something you have made, and tell us what you would like to build next.
Show us what
you care about.
We’re not listing specific vacancies on this page. If our work interests you, you can send an introduction for future conversations. An introduction is not an application to an advertised role.
Introduce yourself ↗Your contribution.
Tell us what you worked on, what was difficult and what you learned along the way.
What comes next.
Share the kinds of problems you want to work on and why they interest you.
A CLOSER LOOK
A useful introduction tells a story.
01
Share work with context
A portfolio link is a good starting point, but the decisions behind the work are what make it useful. Explain the problem, who the work was for and the part you owned. If the project involved a team, distinguish your contribution from the wider result.
A small, complete example can say more than a long list of tools. Describe a constraint you worked within, an option you considered and the reason for the direction you chose. Include what you would change if you approached the work again.
02
Show how you think across boundaries
Bervyn’s interests include interface design, product engineering and the systems behind everyday workflows. A designer may explain an error state or an onboarding decision. An engineer may explain an integration failure, a testing choice or a tradeoff in the data model.
You do not need to have worked on every part of a product. A clear explanation of your own area, and an awareness of the people depending on it, helps make the introduction meaningful. Public code, a case study or a concise written walkthrough can each provide that context.
03
Be clear about the conversation you want
Tell us whether you are introducing yourself for future work, proposing a collaboration or sharing a project relevant to the product family. Include a way to contact you and the kind of contribution you would like to make.
There are no specific vacancies advertised on this page. Sending an introduction does not establish a hiring process or a promise of a role. If a relevant conversation develops, its scope and next steps can be discussed directly.
A LITTLE MORE CLARITY
Questions, answered.
Are there open roles listed here?
No specific vacancies are advertised on this page. It provides a route for introductions and future conversations.
What should I send?
A concise introduction, one or two relevant examples of work, your contribution and the kinds of problems you want to work on.
Can I share a collaboration idea?
Yes. Explain the idea and why it connects to Bervyn’s products or services, and send it through the contact route.