Squarespace Engineering

engineering.squarespace.com · Company blog · on HN since 2016

The Squarespace engineering team writes about TLS, PostgreSQL, site reliability, tech debt, code review and RFC processes.

What HN saysHN links it for engineering posts, such as the code review culture series, and for hiring posts; commenters call those articles good.
26HN people shared it
6linked it in comments
33stories submitted
772story points
7 months agolast shared
2016people per year2026

Most-shared posts

  1. 1
    Implementing SSL/TLS for all Squarespace sites
    4 people · 33 points · first shared 2016 · discussion on HN
  2. 2
    Introducing the Squarespace Engineering Blog
    3 people · 91 points · first shared 2016 · 5 comments on HN
  3. 3
    Three Kinds of Good Tech Debt
    2 people · 433 points · first shared 2019 · 152 comments on HN
  4. 4
  5. 5
    Under the Hood: Ensuring Squarespace Site Reliability
    2 people · 5 points · first shared 2017 · discussion on HN
  6. 6
  7. 7
    Squarespace Announces Local Development Server
    1 people · 113 points · first shared 2016 · 39 comments on HN
  8. 8
  9. 9
    Squarespace's Block Editor
    1 people · 17 points · first shared 2021 · discussion on HN
  10. 10
  11. 11
    Implementing HTTP/2 for Squarespace Websites
    1 people · 6 points · first shared 2017 · discussion on HN
  12. 12
    Profile on Tanya Reilly, Principal Engineer, Squarespace
    1 people · 5 points · first shared 2020 · 1 comments on HN
  13. 13
    Migrating from Postgres to CockroachDB
    1 people · 5 points · first shared 2025 · 2 comments on HN
  14. 14
  15. 15
    A Blueprint for an Engineering Manager Forum
    1 people · 3 points · first shared 2021 · discussion on HN

What HN people wrote when they linked it

mattzito · 2017-04-03
Squarespace | Developers, Product Managers, SRE, Backend | NYC | Full-time, Onsite Squarespace helps people and businesses create beautiful online presences and build their brands. Our website builder and hosting platform allows anyone to create a website that looks professional for their startup, personal projects, or any small business. We've been growing like crazy the last few years, and are expanding in basically every area, particularly in engineering. We have great benefits, cool people, a beautiful working space, and have been ranked as one of the top places to work in New York by multiple sources. If you're interested in learning more about our engineering culture, you can check out our engineering blog: https://engineering.squarespace.com/ And our careers page for a more specific list of the roles we're hiring for: https://www.squarespace.com/about/careers Feel free to email me directly at mzito@ if you have questions.
mrmondo · 2016-07-22
Yes it's there - I added it to feedly / reeder just before. Here's the direct link if you need it: http://engineering.squarespace.com/blog?format=rss
mlthoughts2018 · 2018-05-31
The vector of skills vs. vector of job properties thing could be a coherent idea. I'd argue it's not a good idea (and I have created joint-embedding models for multi-modal text and image nearest neighbor search systems). But it could be a coherent idea. In deep learning anyway, it's a very similar idea in spirit to something like word2vec. In word2vec you learn how to create some arbitrary vector of real numbers, let's say a 256-component vector, that represents words. The components of the vector for each word are learned by forcing the model to solve a prediction task, like predicting whether two words were truly seen in the same context in a given document or not. The model updates the 256-vector of each word such that this prediction task (which can be based on the inner product of those 256-vectors for sets of words) gets better and better. By the end of this, you can in some sense claim a word's mapping into its 256-vector "represents" some "context" intrinsic to that word. And that 256-dimensional "space of context" where the vectors reside is known as an embedding space. So the 256-vector of a word is often called that word's embedding. For more generic problem, you aren't learning just one type of embedding, but possibly many. In TripleByte's case, I'm guessing they are inputting text characteristics of candidate resumes, self-descriptions, GitHub repos, Stack Overflow profiles, LinkedIn pages, etc. etc., and treating a candidate like a bag-of-words from all those…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close