I have a question about the billing job posting. It says:
This role is not for you if:
You need clearly defined requirements before you start building.
Is that because you want the engineers to use their own judgement and build from vague requirements, or do you want them to create clearly defined requirements themselves, and then approve with non-engineer people? Or some other reason?
Both, we are looking for people that are not "ticket machines", that are able to drive themselves, figure out what's needed and push for it. I've seen good engineers that didn't pass probation not because they were bad at coding but because they were waiting to be told what needed to be done instead of understanding the state of things and coming up with solutions for it.
At the moment there is little overlap between what each member is doing (at least in the billing team) because there is a lot to do and we are currently three people in billing (and there is very little/none when it comes to managerial positions). So we need people that are able to work from their judgement, understand when RFCs are needed, understand when a faster or when a more robust solution is needed and talk with the non-technical people if needed (in the case of billing it is quite oftenrequired). However, even non-technical people are quite technical here so conversations are usually quite easy.
In general, if you are autonomous when doing your job with the occasional exchange of ideas it is a good place to be I think (been here for 6~ months). I think there is quite a high degree of trust put in the people that work there and if you think something is interesting/important you are most probably going to be able to work on that.
Happy to jump on a call at some point to explain this a bit better if needed.
Location: Mostly SF, but we have a hub in NYC and started hiring in CDMX. Remote possible! See my reply below.
Description: Retool is a low‑code platform to easily build UIs, connect to any API or database, and automate workflows. Retool empowers engineers and non-technical builders to solve problems while you define rules to protect your data.
Contacts: Feel free to reply, DM, or apply directly. I'm just a lowly engineer who wants my company to succeed. I also think it's a great place to work for many reasons.
~20% of our employees can be remote. Remote is 50+ mi from a hub (SF, NYC, SLC, London). People close to a hub work in the office 3 days a week -- Tue, Wed, Thu for US employees. We're still a relatively small company and can be flexible, depending on the manager/team. :)
marcecoll | 15 hours ago
Company: PostHog
Company website: https://posthog.com/
Position(s): Many positions open, check here: https://posthog.com/careers
Location: Remote GMT +2 to GMT -8
Description: Many different roles, many different options. In my case I'm hiring for the Billing team (not product)
Tech stack: Depends on the team, mainly python (django), rust, clickhouse, postgres, react, ts
Compensation: For each position there is a salary calculator based on location, role, and seniority you can check that here
Contacts: You can message me here for the billing position or go directly through the website.
jaredkrinke | 12 hours ago
I'm betting that whoever built that web site (unironically) had as much fun building it as I had playing with it. Kudos!
dprkh | 15 hours ago
I have a question about the billing job posting. It says:
Is that because you want the engineers to use their own judgement and build from vague requirements, or do you want them to create clearly defined requirements themselves, and then approve with non-engineer people? Or some other reason?
marcecoll | 15 hours ago
Both, we are looking for people that are not "ticket machines", that are able to drive themselves, figure out what's needed and push for it. I've seen good engineers that didn't pass probation not because they were bad at coding but because they were waiting to be told what needed to be done instead of understanding the state of things and coming up with solutions for it.
At the moment there is little overlap between what each member is doing (at least in the billing team) because there is a lot to do and we are currently three people in billing (and there is very little/none when it comes to managerial positions). So we need people that are able to work from their judgement, understand when RFCs are needed, understand when a faster or when a more robust solution is needed and talk with the non-technical people if needed (in the case of billing it is quite oftenrequired). However, even non-technical people are quite technical here so conversations are usually quite easy.
In general, if you are autonomous when doing your job with the occasional exchange of ideas it is a good place to be I think (been here for 6~ months). I think there is quite a high degree of trust put in the people that work there and if you think something is interesting/important you are most probably going to be able to work on that.
Happy to jump on a call at some point to explain this a bit better if needed.
dprkh | 13 hours ago
Thanks—I really appreciate the detailed response. No need for a call.
hauleth | 2 hours ago
Is the Python strong requirement, because I have not so friendly relationship with it.
marcecoll | 2 hours ago
There are some teams (particularly in ingestion) that work more with Rust, but you'd need to do some python here and there for sure.
markerz | 8 hours ago
Company: Retool
Company website: https://retool.com/
Position(s): So many roles from AI, data science, infra, backend, and fullstack -- https://retool.com/careers#open-positions
Location: Mostly SF, but we have a hub in NYC and started hiring in CDMX. Remote possible! See my reply below.
Description: Retool is a low‑code platform to easily build UIs, connect to any API or database, and automate workflows. Retool empowers engineers and non-technical builders to solve problems while you define rules to protect your data.
Tech stack: Typescript / Node.js / React / Express
Compensation: $163,800 – $306,000; stock options; dog-friendly.
Contacts: Feel free to reply, DM, or apply directly. I'm just a lowly engineer who wants my company to succeed. I also think it's a great place to work for many reasons.
Student | 7 hours ago
Remote or onsite?
markerz | 7 hours ago
~20% of our employees can be remote. Remote is 50+ mi from a hub (SF, NYC, SLC, London). People close to a hub work in the office 3 days a week -- Tue, Wed, Thu for US employees. We're still a relatively small company and can be flexible, depending on the manager/team. :)