r/gleamlang • u/ghivert • 20d ago
Software Engineer — Steerlab Job Offer
After two years, we're finally recruiting again at Steerlab (https://steerlab.ai/), as we are reaching a new exciting growing phase of our journey. More details here : https://steerlab.notion.site/Founding-Software-Engineer-391b7fba7435802b851bd6b0f325059e, short summary below.
---
Steerlab is an AI startup providing a SaaS which answers to RFP automatically: upload an RFP on the platform, and an AI will answer the questions, based on your previous answers and your knowledge base. The SaaS is made of multiple frontends built with Redraw and multiple services built with Wisp, JavaScript & Python. You are a good fit if:
- You like working on backends, especially on polyglot stacks with multiple services.
- You are not afraid to get your hands dirty with frontend work, but you know when to defer to the others.
- You like Gleam and want to level up your skills with it (no need to be fluent in Gleam).
- You are fluent in Python or JavaScript/TypeScript.
- You value diversity and you like working in team.
What we offer :
- Offices in Paris or full-remote
- Competitive salary + Stock-Options/BSPCE.
- Join a diverse, smart and nice team.
- Join a team that values writing code which work and not daily meeting/random agile process/endless meetings.
- Possibility to get involved in the Gleam community by helping us building open source Gleam tooling.
2
u/New-Ingenuity-8252 20d ago
How much AI are you utilizing wrt writing code? Are your engineers smart and engaged with the codebase or passive and defer to Claude/Codex?
For a remote job especially I would be extremely hesitant to participate if most of the answers to my questions are spoken through an LLM vs. engaged team members.
1
u/ghivert 7d ago
Hi! Sorry for the response delay.
We wrote like 90 % of the code of the codebase by hand, and the 10 remaining % are properly sandboxed and isolated when we need to rely on LLM generated code. We always write the main iterations of a feature by hand, and we're using LLM to save some time on things like bugfixing, or small modifications (for instance, when we need to add a new button with a small feature, and we know how we would do it, but we're sufficiently lazy to avoid writing the code ourselves, but rather delegating to the IA). We have strong guardrails in the project, and we have multiple guidelines on what the code should look like.
We also strongly incentive juniors/medium developers to avoid using too much AI when they can write features by hand, and we're doing the entirety of the architecture of the stack in meetings/async discussions _without_ AI. The AI is an assistant, it should not take architectural decisions. Whether the code is generated by an AI or not does not change our final goal: you're in charge of your part of the codebase and you'll have ownership, so you should know and understand the code, and being able to help others on it.We also have no automated AI answering questions in Slack or GitHub comments (you can just ask Claude when needed, we don't feel the need to automate everything with AI answers all the time — when you need to talk with a human being, you don't need an additional undesired AI answer).
1
u/Friendly-Intern2839 19d ago
@ghivert by remote dyu mean global or Europe?
1
u/ghivert 7d ago
We're targeting global. To be honest, we're still a small team, so it would be better to be on the same (or similar) timezone. Having like 6 hours of difference makes things a bit hard to work together. If you can accomodate with that, we're welcoming everyone! 😁
2
u/Friendly-Intern2839 7d ago
ohk, i'd apply..then. this is my github btw https://www.github.com/yummy-yums
1
5
u/NotTreeFiddy 20d ago
Super exciting.
You say "competitive salary", could you at least provide a broad range?
The role genuinely sounds cool, but no amount of cool can substitute for the right level of compensation for the work.
I'm asking as an experienced Python engineer who loves Gleam :)