WRITER

Working at Writer has been one of the most rewarding chapters of my engineering career. The company sits at a genuinely interesting intersection — building enterprise-grade generative AI before most of the industry knew what that meant — and the technical problems reflect that. As a Senior Software Engineer, I get to work on systems that are both deeply complex and visibly impactful: shipping features that real Fortune 500 customers rely on every day, not toy demos.

What stands out most is the quality of the engineering culture. There's a strong bias toward ownership and shipping. Engineers are trusted to scope their own work, push back on requirements, and make architectural decisions without bureaucratic overhead. Code review is rigorous but constructive, and there's a healthy respect for craftsmanship — performance, reliability, and developer experience are taken seriously, not treated as afterthoughts. The bar for hiring is high, which means the people you collaborate with consistently raise your own game.

The product direction is another major plus. Writer built its own family of LLMs (Palmyra) and a full-stack platform around them, so engineers get exposure to everything from low-level model serving and inference optimization to product surface work, RAG pipelines, agent orchestration, and enterprise integrations. It's rare to find a company where you can move that fluidly across the stack without context-switching feeling forced.

Leadership communicates clearly and honestly. May Habib and the executive team hold regular all-hands where strategy, customer wins, and challenges are discussed openly. Roadmaps are transparent, and individual contributors have real input into what gets prioritized. Compensation and equity are competitive, remote flexibility is genuine rather than performative, and the benefits package is solid.

Areas where I'd love to see continued investment: the pace can be intense, especially as the company scales and customer commitments grow, so guarding against burnout requires intentional effort from both managers and ICs. Internal tooling and documentation occasionally lag behind product velocity — a common growth-stage problem, but one worth staying ahead of. Cross-team coordination can also get heavier as the org expands, and continuing to refine async communication norms would help.

Overall, Writer is a place where senior engineers can do their best work: meaningful problems, strong peers, real autonomy, and a clear mission. If you care about applied AI, enterprise software done well, and being part of a team that ships, it's hard to beat.

Pace and burnout risk: The cadence can be intense, especially around customer commitments and quarterly pushes. More structured "cool-down" periods after big launches, and clearer expectations around on-call and after-hours availability, would help.

Meeting load: Recurring syncs have been creeping up. A periodic meeting audit and stronger async-first norms (written updates, recorded standups, decision docs over live debate) would give engineers more deep-work time.