There are good'ish benefits and ok pay. There are perks like free snack and soda and beer in the office if you are local to Austin. There are plenty of social events. The sales and customer support teams are very capable.
Engineering leadership is quite bad. Architecture is ancient, so is the core code base. In essence, the core business revolves around keeping maintaining a customized data processing engine written two decades ago couldn't be fitted to properly use modern data tech stacks.
Knowledge is very siloed, and lots of red tape to get anything done. Internal documentation on core architecture is almost non-existent. If you want to know how something works, a meeting with the architect in that area is required to have them explain while they walk through the code themselves. All technical knowledge distribution is on a "need-to-know" basis, very difficult to learn anything outside the area you're working on.
Architect level engineers are more interested in protecting what they've already designed and built rather than doing what needed to be done to make the system more efficient or cost effective.
There's a big disconnect between dev and infrastructure where neither side really cares what the other side is doing.
Stop letting the architects siloing the knowledge.
Get some fresh minds involved in architecture design decisions.
The ancient architecture is highly cost inefficient, the core had to change, but the architects are holding on not wanting to let go.
Really clean and easy process. The recruiter was helpful, the coding challenges were complex but relevant to the job I was applying for. The negotiation phase was also clean and easy.
First a technical phone interview with engineering manager. Then an onsite with 4/5 engineers and lunch with manager/director. The engineer interviews were purely technical, white board coding, system designing. The manager interview was more about d
There were two parts, a technical and a behavioral one. The technical was coding five problems in any language that you want in an hour. They were mostly over string processing and loops. The behavioral was second and had standard questions.
Really clean and easy process. The recruiter was helpful, the coding challenges were complex but relevant to the job I was applying for. The negotiation phase was also clean and easy.
First a technical phone interview with engineering manager. Then an onsite with 4/5 engineers and lunch with manager/director. The engineer interviews were purely technical, white board coding, system designing. The manager interview was more about d
There were two parts, a technical and a behavioral one. The technical was coding five problems in any language that you want in an hour. They were mostly over string processing and loops. The behavioral was second and had standard questions.