Founding Engineer (Infrastructure)

**About** \& Senibina makes Enjin. Enjin uses AI to carry design work from the first idea towards the buildings, interiors and places that get built in real life. It starts where projects get hardest. That is the later stages, when the design is still changing but has to get ready for common data environments. It works with the software practices already use instead of replacing it, and it grows with computing power, not with software seats or specialist hours. It's now in private alpha with practitioners across Asia, the Middle East and Europe. **The Role** You'd be the first engineer to join the team! We are small and scrappy, so you will wear a few hats, scaling compute one day and sitting with a practice team the next. If that sounds like fun, we would love to hear from you. Every time someone asks Enjin for a change, it builds a new model in the cloud and checks it first. If the new model has a problem, they keep the last one that worked. Next, we want Enjin to build many options of the same idea at once, so a team can compare them and pick the best one. That takes far more compute running in parallel, and scaling it is the work you would lead. Our technical founder comes from AEC practice and has been learning the infrastructure side along the way, so your advice will shape how we build it! **What you'll work on** * Growing the cloud machines that build models, and keeping them healthy under real load * Job queues and recovery, so a slow or failed job never holds up someone else's work * Keeping each practice's files and work separate and secure * Measuring what each model costs to make, then bringing that cost down * Deploys, monitoring and incident response for a small production system **You might be a fit if** *For the role* * You've run production systems on a major cloud provider (AWS, Azure or Google Cloud), from virtual machines and networking to sign\-in, permissions and cost controls * You've run production systems where jobs are long, hold state and can fail halfway through * You can explain where the cloud bill goes * You keep exploring AI as it changes, try new models and tools yourself, and share what you find *For the founding part* * You have worked with design software like AutoCAD, Rhino or SketchUp, and with BIM software like Revit, and you know how work moves between them on a real project * You have built with visual programming tools like Grasshopper or Dynamo, or written scripts and plug\-ins for design and BIM software * You understand BIM as the information a model carries, its properties, quantities and decisions, from early design through to construction * You have seen what breaks when a design model and a BIM model run side by side and drift apart * You enjoy talking with architects, designers and property teams, and asking what slows their work down * You are happy to sit with a practice team on their own project, watch how they use Enjin, and turn what you see into fixes the same week * You have spent time in architecture, engineering or construction, or you simply love geometry. If the difference between G1, G2 and G3 surface continuity makes you curious, you might be the person we are looking for * Bonus points if you cycle. Most of our best ideas so far have come on a bike ride