Life at openecore

Life at openecore.

openecore is early, so this page is about the engineering environment we are building rather than a list of things we already have.

How we work

Four things we hold to.

These are statements of intent, not achievements. You are welcome to hold us to them.

Build with purpose

Work starts from a real problem and a real constraint, not from a technology someone wanted to try. If a simpler thing solves it, we build the simpler thing.

Think across boundaries

Software, intelligence and hardware usually have to work together, and the difficult parts sit exactly where they meet. Nobody here is confined to one side of that line.

Learn by building

Prototypes, measurements and bring-up teach more than a long document does. We would rather find out early than plan around a guess.

Keep it simple

Clear engineering over clever engineering. Code and systems should be readable by whoever inherits them, including us in a year.

How we hire

Conversations, not a gauntlet.

A one-to-one about what you have built, a technical discussion about how you think, and a group session — because most of the work here happens between people rather than alone.
Two people at a laptop in a small interview room, code on the screen, beside a whiteboard listing the topics for the discussion.

One to one

Your work, your questions, and what you want to build next.

A technical interview in progress: three people at a meeting table facing a screen, with a whiteboard beside it listing problem solving, embedded systems, Bluetooth, system design and communication.

Technical interview

A conversation about how you think, not a quiz.

A group discussion around a long table, a facilitator standing at a whiteboard that lists the steps: introduce yourself, share your perspective, listen and build, collaborate, summarise.

Group discussion

How you work with other people, which is most of the job.

Work with us

Work across the whole problem.

Most engineering jobs hand you one layer. Here the interesting parts are usually the seams between them — firmware meeting a model, a device meeting a network that is not there.