For AI agents: Find a documentation index at https://talkjs.com/llms.txt (full content at https://talkjs.com/llms-full.txt). Get a markdown version of any page by appending .md to its URL path.
TalkJS default-dark logo
Sign inTry for free

Work at TalkJS

Help build chat for products worldwide

At TalkJS, we make it easy for developers to add chat to any product. We’re a small, 100% distributed team with a HQ in Eindhoven, 🇳🇱 the Netherlands. TalkJS is profitable, growing, and not dependent on venture funding.

Open roles

We're not currently looking to expand the team, sorry. Check back later!

About TalkJS

Product driven

We care tremendously about quality.

We want TalkJS to be what every developer thinks of when building chat features—much like Stripe has become for payments. This means the product has to be excellent on all fronts. To make this happen, we hire great engineers and give them the maximum amount of freedom and trust to ship fantastic SDKs, APIs, and features.

Independent people solving challenging problems

When we say “maximum amount of freedom”, we really mean it. At TalkJS, you’re the “product manager” of your own work and you run it all the way—alone or together—from inception until it’s in our customers’ hands. Work flexible hours, from anywhere. No micromanagers, almost no meetings, and lots of collaboration.

Meetups

Although we’re a fully remote team, we make time to meet in person. Our meetups are usually held somewhere in Europe and happen at least once a year, often twice. These gatherings give us a chance to connect face-to-face, share ideas, and have some fun together outside of screens.

Key culture highlights

Healthy work/life balance

Because you can't ship great stuff when you're tired and overworked

Respectful working culture

Because only constructive feedback makes the product better.

Responsibility

Every team member proactively proposes and ships improvements, which lets us skip a lot of project management overhead.

Small team, little hierarchy

Because a few fast movers can get as much done as four layers of management with hundreds of bureaucracy-shackled team members.

A no-nonsense working culture

To learn more about our culture, here are a couple of blog posts you might be interested in:

When I was a dreamy wantrepreneur, my idea of running a startup involved foosball tables, slides, unlimited book budgets, and frequent company parties. However, when Joshua and I actually started TalkJS…
Egbert Teeselink
CEO, TalkJS
Recently, I joined an organization with some radical ideas about company culture. Let's look back over my time at TalkJS so far, and discuss the things that stood out to me — both good and bad.
Steven Waterman
Developer, TalkJS

Learn more about how we work

Some more background that might interest you:

TalkJS is structured as a typical client-server application. We like new technology and we like to balance it out with proven technology. This is what we use right now, but it's always changing, and we're happy for you to learn on the job.

Core TalkJS Backend infrastructure

  • Elixir
  • Phoenix Framework
  • PostgreSQL

Frontend (prebuilt UI + JavaScript SDK)

  • TypeScript (+ a little bit JS left)
  • React
  • A little bit of NodeJS to prerender the prebuilt UI for faster loading

Website

  • NextJS
  • Tailwind CSS

Infra/devops

  • Elixir/Erlang’s parallel processing keeps our server setup simple—just Docker (Compose) and GitHub Actions.
  • Test releases spin up automatically by adding a label to a PR.
  • Production and staging use automated blue-green deployments via GitHub Actions.
  • SDK updates are automatic, as our NPM package dynamically loads JS from our site (with guaranteed backwards compatibility).
  • We don’t do continuous deployment, but we release often—usually a few times a week, sometimes multiple times a day.
  • Extensive monitoring with Datadog, AppSignal, LogDNA, Uptime.com, and Erlang’s Observer.

Key tooling

  • TalkJS → support via a TalkJS chat widget + custom Slack integration
  • GitHub → feature branch/PR workflow, issues for bugs, Discussions for specs/architecture
  • Slack → main comms tool (feel free to mute for focus); Huddles for quick calls
  • Notion → wiki, docs, drafts, and our jobs page
  • Figma → design work
  • Gmail & Google Calendar → minimal email use (mostly with customers)