griddable.io

Pros: I liked working on real-world data science problems. As a Data Engineer, I learned a lot about specific ML infrastructure. The team is super supportive. Remote work flexibility is great.
Cons: Career growth can feel really slow here. There isn't a super clear path for promotions. For a startup, I expected more upward mobility. It's tough to move into senior roles without an established framework.
Advice to Management: Build out clearer career paths for individual contributors. Define what it takes to get promoted. This would really help with retention for folks in data roles.

Pros: As a Software Engineer at this startup, you get to touch a lot of different tech. It's good for picking up new skills, especially with their data science platform. I've learned a ton about new frameworks working remotely.
Cons: The career growth path isn't super clear, which is tough. There aren't many defined steps to move up, especially for mid-level folks. Sometimes you feel a bit stuck without a clear promotion process.
Advice to Management: Work on clearer growth frameworks for Software Engineer roles. Help us see what's next and how to get there. Formal mentorship programs would also really help.

Pros: I've learned a ton working here as an ML Engineer. The problems in AI infrastructure are genuinely tough and interesting. Team members are super bright and helpful.
Cons: Work-life balance can be tough at this startup. There are often late nights, especially before big releases. Communication from leadership sometimes feels a bit scattered.
Advice to Management: Try to set clearer expectations on deadlines. Also, maybe encourage more defined WFH boundaries for the team.

Pros: I've enjoyed the folks I've worked with here. The team is genuinely collaborative, which helps a lot when you're a remote Software Engineer tackling complex data science problems. There's a decent sense of camaraderie among the engineers.
Cons: The company culture, while friendly, can feel a bit loose. There aren't always clear guidelines or processes, which is tough for new hires or when trying to push big features. Sometimes it's hard to get clear direction from leadership on project priorities.
Advice to Management: Focus on building more robust internal processes and clearer communication channels. It would help the remote engineering team immensely.

Pros: The remote from Austin, TX, flexibility is a huge plus for this SaaS startup. I could manage my own schedule mostly, which helped a lot with personal appointments. There's also no micromanagement, so as a Software Engineer, you get a lot of autonomy.
Cons: Work-life balance can definitely suffer during crunch times. It's not uncommon to put in 50+ hour weeks when deadlines hit for the data analytics platform. Sometimes it felt like there wasn't a clear boundary between work and personal time, especially with a WFH setup.
Advice to Management: Try to better manage project scopes to avoid constant crunch mode. Clearer expectations around 'off-hours' for remote teams would really improve things.

Pros: I've really enjoyed working with my fellow engineers here. Everyone's super collaborative, which is great for a remote startup. The team culture among the Software Engineers is solid.
Cons: It's tough to build a strong company-wide bond when you're all remote. There aren't many social events, so it can feel a bit isolated sometimes. Wish there were more opportunities for casual team hangouts.
Advice to Management: Try to implement more regular, non-work related virtual social events. Maybe a weekly coffee chat or a game night to foster better company-wide connections for the remote team.

Pros: Working at griddable.io offers a lot of autonomy, which is great for a fully remote setup. You get to work with smart people on interesting AI platform challenges. The work flexibility is a big plus here.
Cons: Sometimes the leadership team lacks a super clear vision for the product. As a Software Engineer, it can be tough when priorities shift a lot. We need more consistent strategic direction.
Advice to Management: Focus on establishing a clearer product roadmap and communicating strategic shifts better. More consistent priorities would help everyone, especially the engineering teams, deliver more effectively.

Pros: The base salary for a remote Software Engineer is pretty solid for a startup, especially considering our size. They did offer equity, which is common in the tech industry, though it's still early stage. The health insurance plan is decent, nothing fancy but it gets the job done.
Cons: Annual raises haven't been huge, it feels like they're trying to keep costs down. There aren't many extra perks or benefits you'd see at a bigger tech company. The 401k match is pretty minimal, that's definitely an area for improvement.
Advice to Management: Think about improving the 401k match and adding some more unique benefits to attract and retain talent in the competitive software engineering market.

Pros: You learn a ton quickly here, especially as a Data Engineer. It's a true startup, so you get hands-on with real machine learning infrastructure. Great for building skills in a fast-paced tech environment, especially if you're proactive.
Cons: Career growth isn't super structured; there aren't clear promotion paths laid out. Mentorship is kind of informal, so you'll need to seek it out yourself. Remote work means less casual learning from senior folks sometimes.
Advice to Management: Formalize some career paths and mentorship programs. It would really help folks trying to grow into senior roles, especially for our remote teams.

Pros: I really appreciated the flexibility as a Remote Data Scientist. Being fully remote let me set my own hours most days, which is great for personal life stuff. This is common for many tech startup roles.
Cons: Sometimes the lack of a central office for this tech startup meant project coordination got messy. You really need to be good at self-management for these machine learning projects. Not ideal if you prefer constant face time.
Advice to Management: Work on clearer communication protocols for fully remote teams, especially for complex machine learning projects. Regular syncs could help bridge the distance.