AlphaSense

Pros: As a Sales Development Representative, I got great initial training on their market intelligence platform. It's a fantastic way to learn about the financial data industry and build your sales foundation. The team in the New York City office is pretty motivated.
Cons: Career growth for SDR roles can feel pretty limited after a certain point. It's tough to get promoted internally to an Account Executive role without a really long wait or having to jump through a lot of hoops. There's not much upward mobility if you're looking to quickly move up within the sales org.
Advice to Management: Create clearer paths for SDRs to advance into AE roles, perhaps with more mentorship or a structured internal promotion program. Reduce the perceived bottleneck for growth.

Pros: I've had some really good projects building out new features for the fintech software. There's a decent amount of autonomy if you're a performing engineer. My specific team tried to keep things reasonable, mostly 40-45 hour weeks.
Cons: Work-life balance here isn't consistent across the board. Some teams definitely had late nights and weekend work, especially closer to big releases. The pressure to deliver for the market intelligence platform can get intense for product teams.
Advice to Management: Try to standardize expectations around work hours across different engineering and product teams. It would help a lot with burnout and retaining good people.

Pros: It's nice that they offer a hybrid work model for Software Engineer roles, so I'm not always in the NYC office. You get some leeway to manage your schedule, which is good for personal appointments.
Cons: However, the 'flexibility' often means you're still expected to be online late, especially collaborating across time zones on financial data projects. It can be tough to truly unplug even with the remote option, and sometimes it feels like just showing up isn't enough.
Advice to Management: Really encourage managers to model true work-life balance and respect the hybrid policy. The pressure to always be 'on' counteracts the flexibility you're trying to offer, especially for engineering teams working on critical financial data platforms.