-Good WLB -Nice office -Vehicle lease program
I was willing to accept a significantly lower SWE salary for the first couple years, but every year there is some organizational restructure and they have intentionally moved into a "horizontal" structure aka no promos any time soon. This is problematic because people at levels 14/15 (entry to mid) should be expected to grow their skills while promos should be more difficult to achieve from 16 and above. Instead I was hired as an entry level and 4 years later I'm expected to still hold an entry level position while I'm driving team initiative and development? It doesn't make sense.
In CT there is an overabundance of processes. The amount of non-development work that is done just to deploy changes to production is WILD. Documentation formatting and expectations frequently change. The Jira tracking is of epics and program milestones is often chaotic/duplicated and with no clear or org wide standardization. So from a processes standpoint there is almost intense micromanagement significantly decreasing productivity and quick iteration from developers. And yet team managers are often very absent from calls leaving developers to have to respond to higher managers or other stakeholders about why certain things are they way they are, etc. My experience has been that senior developers try to present themselves as tech leads/managers and pass the responsibility down the line. I've never seen so much finger pointing before. Lots of CT people have visa sponsorship so it prevents them from leaving.
If you are looking for stability, this may be for you. If you are looking for guidance/support in larger objectives and initiatives, strong development opportunities, or growth, this won't be a good fit.
Stop trying to solve problems by introducing new processes. Developer efficiency is significantly inhibited by arbitrary processes.
Having more ICs report to senior managers and have tech leads responsible for multiple teams, leaves individuals spread way too thin which ultimately means lower level developers are responsible for representing and advocating for their teams which feels very unfair. The continuous lack of clarity and "we need a couple months to figure things out" has gone on for quite a while.
The process took about a month. First was a typical phone screen with a recruiter, followed by a video call with the project manager where he asked about my skills and work history. Then I was invited for an onsite interview where I had to give a p
The interview process consisted of an HR round followed by one or two technical rounds. The technical discussion focused on my past project experience, especially around Spring Boot, microservices architecture, and API Gateway. I was also asked about
There were 4 rounds of interview, but after 2 rounds HR was unresponsive, and so their 1st round was HR, and the 2nd was a coding challenge where they gave me an API integration to do.
The process took about a month. First was a typical phone screen with a recruiter, followed by a video call with the project manager where he asked about my skills and work history. Then I was invited for an onsite interview where I had to give a p
The interview process consisted of an HR round followed by one or two technical rounds. The technical discussion focused on my past project experience, especially around Spring Boot, microservices architecture, and API Gateway. I was also asked about
There were 4 rounds of interview, but after 2 rounds HR was unresponsive, and so their 1st round was HR, and the 2nd was a coding challenge where they gave me an API integration to do.