My advice is that it is time to interview them. Why do they do what they do, what are their pain points, are they open to trying X to fix pain point Y, and so o

My advice is that it is time to interview them. Why do they do what they do, what are their pain points, are they open to trying X to fix pain point Y, and so on. Interviewing is a two way street, and it may just be how you ended up wording your question, but I don't get the sense that you really know the answers to any of those questions. None of us can really answer that part for you. My other advice is that if you are early in your career, it doesn't hurt to be exposed to different practices. Even if you ultimately decide that they should have used CI and such, you will see another approach which may perfectly apply to some job in the future. (Almost) No job is perfect - there will be a mix of interesting/dull work, great/bad practices, too many meetings or not enough communication, and so on. If it doesn't see like you'd be miserable there, why not go on over, build your UI/Javascript chops, and build it into your next job?