
Worksoft Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Which role are you interviewing for?
4 roles · 7 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Worksoft.
Disorganized
I had a really disappointing interview experience that made me wonder about how organized this company is. The first interview, the interviewer was 15 mins late and I didn't have much time to ask my own questions. They said they couldn't see me in the virtual waiting room and someone had to manually add them to the meeting. For the second round, they changed the interview time without checking if it worked for me, and I just got an updated invite. I was told this would be with the Director of a department, so I prepared for that. But then, when the interview started, someone else joined unexpectedly without introducing themselves, which was awkward and confusing. I had no idea who this person was or why they were there, and the director never even showed up, and no one explained why. After that, I asked for their contact info to send a thank you note. I followed up after a week with no reply and only got a LinkedIn profile, not direct contact details. All in all, it felt super disorganized and made me worried about how they handle internal communication and processes.
- Can you tell me a bit about yourself and what you know about worksoft?
Senior Software Engineer
There were a total of 4 interview rounds: L1, L2, and 2 managerial rounds. They were all purely about the tech skills I applied for. Since I applied for Dot net Full stack developer, the interview focused on Dot net technical stuff, including C#, Asp.Net MVC, .Net Core, SQL Server, and Angular 12.
- Can you explain how delegates and events work in C#?
- What are Extension Methods, Properties, and Static classes in C#?
- How does dependency injection work in .Net core?
Technical Writer
I went through a few rounds of interviews. It started with HR, then the Director of Engineering Operations, followed by a Sr Tech Writer, and then the Director of Special Projects, and finally the CTO. I made it to the second round. The first interview was great, really flowed well. The second interview was supposed to be an hour but only lasted 30 minutes. I didn't feel great about it afterwards; it felt rushed and the interviewer seemed to have already made up his mind even though he was polite. I followed up twice and heard nothing, then got the official rejection about 12 hours after I posted this. The whole thing from offer to rejection took over 5 weeks.
- Can you tell me about yourself?
- What are your position-related questions?
- Tell me about a time you dealt with disagreeable coworkers.
.NET Developer
They conducted 3 rounds: HR, Tech 1, and Tech 2. The first 2 rounds were pretty straightforward if you knew your stuff. The 3rd round was intense, lasting about 1.5 hours. It felt tough because they were looking for a fresher but expected them to know everything from front-end to programming languages and APIs.
- Can you answer some theoretical questions about Java?
- Could you write a program to explain exception handling?
Worksoft Interview Questions
Quoted word for word from Worksoft interview reports.
“How does dependency injection work in .Net core?”
Read reports →“What are Extension Methods, Properties, and Static classes in C#?”
Read reports →“Can you explain how delegates and events work in C#?”
Read reports →“Could you describe the life cycle of a .Net core application?”
Read reports →“Could you write a program to explain exception handling?”
Read report →“How would you implement security in the application?”
Read report →“How do you go about handling exceptions?”
Read report →“Can you answer some theoretical questions about Java?”
Read report →“Describe a project of yours that failed spectacularly.”
Read report →Formats, difficulty and experience
Across all 7 Worksoft interview reports.