
Pitney Bowes Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 42 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Pitney Bowes.
Software Engineer
It was a 30 minute call with the recruiter. They started by asking what questions I had for them. Then, they asked about my technical experience, what I look for in a company, and what qualities I look for in a manager. Finally, we talked about company goals and what the next steps are.
- What do you look for in a company?
- What qualities do you look for in a manager?
Software Engineer
The interview kicked off with a technical round featuring two interviewers, focusing on data structures and algorithms, particularly data handling post-selection. Next, there was a second round with two managers from the team I'd be joining. This round delved into questions about past projects, architecture, workflow, and fine details, plus more data structure queries. After passing, I was free for the day and HR scheduled a call for the third round the following day (I appreciated the timing flexibility). The next round was with the VP of Engineering & Technology, covering data structures, cronjobs, puzzles, and handling large datasets. Following that success, a fourth round with the Director involved deep listening and evaluating self-explanation skills. I enjoyed this interaction; he asked unconventional, innovative questions, making it a very engaging experience. The fifth and final round was with the Manager HR, who discussed the company's culture and technologies and gathered my feedback. Finally, the Manager HR confirmed my selection and arranged a call with HR the next day for salary discussions. Overall, the interview process was quite smooth and swift.
- DS related(tree,linkedlist,array)
- Hashmap internal implementation
- Algorithm
Software Engineer
It's a very long process. They schedule a call but then don't show up because they are super busy. Then they start asking irrelevant questions. Without assessing the candidate's understanding of concepts, they brag about themselves and their team. I don't understand why they conduct interviews if they are so busy. How will they value your time when you join if they don't respect you and your time during the interview? Interviews are the first impression of a company, its team, process, and members. It's too pathetic. They should behave like a mature company, not a roadside crap company. They should learn to respond to candidates with the outcome, whatever it is. If not, they shouldn't waste our time. Ask the interviewer to be polite, not arrogant.
- Could you explain why the xyz approach was chosen over the abc alternative?
Pitney Bowes Software Engineer Interview Questions
Quoted word for word from Pitney Bowes interview reports.
“What are the differences between Web API and WCF?”
Read reports →“Find the missing word in a sentence, given the complete sentence and the incomplete one.”
Read reports →“Can you explain the implementation of virtual functions in C?”
Read reports →“Can you describe the distinction between the Factory and Abstract Factory design patterns?”
Read reports →“Could you compare and contrast SOAP and RESTful services?”
Read report →“Can you explain the differences between NoSQL and SQL databases?”
Read report →“Can you list the various lifecycle hooks available in Angular?”
Read report →“Explain the mechanisms for communication between parent and child components in Angular.”
Read report →“Can you explain the implementation of a hash map?”
Read report →Formats, difficulty and experience
Across all 42 Pitney Bowes interview reports.