Speckle | Head of Delivery | London (hybrid; UK-based) | Full-time | £120–140k base + variable (OTE ~£160k) + meaningful equity
Speckle is the open-source platform that makes 3D/AEC design data accessible, trustworthy, and queryable across every tool in the stack - Revit, Rhino, IFC, ACC and more. We've just launched Speckle Intelligence: ask your project models anything, trust the answer, and generate client-ready deliverables in minutes. 23 people, open-source core, enterprise tier on top, post-Series A. Repo: github.com/specklesystems
We're hiring our first Head of Delivery to own the enterprise post-sale motion: turning pilots with general contractors, owners, and large service providers into expanded production deployments. Forward-deployed role (think Palantir FDE, not SaaS customer success) - you sit inside the customer's real decision problem, make "trust the answer, take the action" true on their actual data, and feed what you learn back into product. We measure impact and not closed ticket counts.
Good fit if you've delivered technical/data products into heavy industry (AEC, construction tech, infra, or similar) and can read an enterprise's problem without a spec. AEC background a strong plus, not required. Comfortable with messy data and ambiguous orgs.
Speckle | Backend (Engineering), Founding Account Executive (Growth) | Full-Time | REMOTE | US East, London, EU | https://jobs.ashbyhq.com/speckle
At Speckle [0], we’re on a mission to shake up the AEC (Architecture, Engineering, and Construction) industry. To do that, we're building the OSS data layer for AEC to operationalize how the built environment industry works with data and automation. Think of us as a cross between Github and Palantir, with an opportunity to significantly impact a $10 trillion industry. Our platform already powers workflows on billion dollar projects at leading firms like Suffolk, Multiconsult, Pomerleau, and Stantec.
I'm the CEO/founder and I can honestly vouch that we're tight knit team that values autonomy and shipping cool product on top of our data layer (me included - and this might be a red flag for some, but it's my therapy) over hierarchy, politics, levels and complexity (my spirit animal is the grug brained developer). We love working together with our customers - construction is truly a unique place where each project is its own micro universe.
We have multiple roles open across engineering and growth (sales & marketing) [1]
Having lived in several European cities so far (Brussels, Rotterdam, Stuttgart, Berlin, Bucharest), London's (where I have lived since 10 years) public transportation is one of the best I've seen so far. It's not without its zonal imbalances, but calling it terrible, unreliable, etc. is something I do not subscribe to, and, I suspect, neither do many of its residents.
You might be right though: what is your commute/experience that made you describe it so? Am genuinely curious to understand in how much of a privileged bubble I might be in.
Shameless plug: at Speckle[0] we have the same attitude (we even have Ralph, Plangrid cofounder, on the cap table).
Only difference is we deal in 3D rather than pdfs, and we're open source for too many reasons to type on a mobile phone, but happy to elaborate if needed.
- Senior Creative Frontend Engineer: a detailed oriented person to combine the role of application developer with that of UI/UX specialist.
- Senior .NET Developer: a fast track to tech lead position in which we're looking for an experienced person with desktop development chops and a passion for performance as well as pastoral care.
- An ambitious founder's assistant for the COO track. The challenge: take a startup from "garage & pizza boxes" stage to professional shop status.
Feel free to send me an email directly (it's in my profile), or apply via our jobs page.
SomaFM is an amazing institution. I was introduced to it mid/early 2000's by travelling tech nomad from Germany that passed by Bucharest; I spread it to my family (dad keeps a recurring donation going and we have a family heirloom soma fm t-shirt). Fast forward to now, my 2mo old seems to enjoy Space Station Soma, and, if I'm lucky, falls asleep on Deep Space One.
I hope future generations will get to enjoy it. As others said (tbatchelli), "it's an example of how we believed the Internet is going to be".
Hi! Random plug: we're building an OSS data platform for 3d data called Speckle [0]. Currently focused on architecture, engineering and construction, but we already have integrations with Revit, AutoCAD, Rhino, etc. - it might be worth a look if you're interested, and perhaps some bits and parts can be adapted for your PLM.
Speckle | London/Remote | Full Time | Sr. Frontend Eng.
We're a young COSS company building the git for 3D. We're looking for a proactive & social sr. front-end engineer that is willing to build the future UIs for data informed design, serving architecture, construction to manufacturing and more. We have an awesome remote-first & non-boring team, but since we're first time doing this we'll need ±4-6hrs overlap with the London timezone.
Hi! Dimitrie, founder @ Speckle. We are revolutionising how architects, engineers and construction professionals deal and interact with building and infrastructure data: we believe in a modern ecosystem created around an open source platform (Speckle!). When we use big words, we like to say that we're building the "git & github" for a $10T industry (AEC - architecture, engineering and construction).
We have two openings of interest, one for a Frontend Engineer[0] and for a Backend/Devops Wizard[1]. Both positions are remote, but we ideally would like a ~4-6h overlap with the London timezone.
Our stack crosses from NodeJs, Postgres, Kubernetes, to C#, Python and sprinklings of C++. There's always something fun to hack on at Speckle! We work in the open, constantly engaging with our community and users from across backgrounds, domains and cultures[2]. We have other openings too, just head over to our careers page [3] for more info & company culture snippets.
For those inclined, there's a nice article by Marilyn Strathern, The Tyranny of Transparency [0] that echoes the sentiments in this article. It builds upon Hari Tsoukas' The Tyranny of light: The temptations and the paradoxes of the information society [1], which I heartily recommend if interested in reflections on this topic.
To entice, here's a small excerpt from the abstract of [1]:
> The overabundance of information in late modernity makes the information society full of temptations. It tempts us into thinking that knowledge-as-information is objective and exists independently of human beings; that everything can be reduced into information; and that generating ever more amounts of information will increase the transparency of society and, thus, lead to the rational management of social problems. However, as argued in this paper, the information society is riddled with paradoxes that prevent it from satisfying the temptations it creates. More information may lead to less understanding; more information may undermine trust; and more information may make society less rationally governable.
Agreed. That's definitely not the scale we operate at (digitally latent, partially marginal by hn standards industry). Nevertheless, this restricts free software to only "critical" need infrastructure that has high value from the start (rather than being allowed to develop it), doesn't it?
While I resonate fully with the ideals encompassed by free software, I find that the "logistics" of supporting them "in real life" are a completely different story, that has little to do with the ethos behind them.
This comes as a singular, personal data point, or course. There's wider context behind my trials and tribulations, but, succinctly put, starting a for profit company around my 5 year-ish old OSS project was the only way I managed to find to safeguard its continued existence and development. This road involves a lot of uneasy compromises that don't fit in the original discourse around free software.
Perhaps, what I'm lacking, is a "how to get there" guide - the ideals are clear, the way to achieve them is not so much so.
Speckle | London | VP/Exec Commercial/Strategy | Full-time | Remote
Our mission is to build the open source data platform for the AEC (architecture, engineering & construction) and foster a community of hackers and builders that will digitally transform the built environment.
We're looking for someone with a strong record of commercial, operational and strategic experience in the COSS landscape/early stage startups. AEC experience is welcome, as well as an emphatic and generous approach to creating value. We're at a very early stage (seed), nevertheless Speckle has been evolving, maturing and gathering traction as an OSS project for the last 3 years. We have a diverse community, and we're keen to offer them the best tools to disrupt a $10 trillion global industry.
If you're keen to help shape the future digital processes which underpin the building that you're reading this from, the city/town that you live in, the roads and transport networks that you travel on - get in touch: [email protected].
As a little side note - possibly helpful if you are willing to invest more time in this project in the long term: I've had some discussions long time ago with people from wikihouse [1], and am still struggling with similar issues with my own adventures (academic research sponsored by an industry network). The model wikihouse adopted was that everyone has a seat at the table, but nobody owns the table itself (or the chairs).
It can be simplistically simmered down to:
If this is a core feature that will allow your project to expand and make it relevant to a wider audience, considering labelling this as a "core feature" and insist on it being part of the open source project. They could sponsor it and/or have direct support of the developer and/or "first adopter" privileges but the code will fold back in the public branch after a given time. It would help if you had another company expressing interest (maybe just ask).
I'm afraid I can't provide a realistic answer to your question, only my encouragement to keep things open.
Nevertheless, I am tangentially curious: once a project already is open source, can it be realistically (legally) closed up again?
Envision the following scenario: I'm just going to clone your project now, as it is - open source - on my machine. You might close it later, transfer ownership, etc. Am I not holding a legally valid open source pile of code, regardless of what Company X decided to do later?
Interesting read. I question though the need for a robot: why don't we use said sensing tech to empower Bob the Builder to "position brick within a seven mm" tolerance, and have the added advantage of well honed human heuristics judging a much wider variety of situations?
From personal experience, the constraints that robotic manufacturing introduce in the design of an architectural object are huge: you end up designing specifically for the affordances of these tools, to the extent that you sometimes get nonsensical results.
As a little extra introduction, what this tool allows for is essentially the online mass customisation of parametric designs of any sort (from iphone cases to urban planning). The novel approach is that content creators are not required to hard-code their design logic in js, or threejs, etc but can use a standard design software package [1].
Fab project otherwise!