ServiceNow Software Engineer Interview Experience (2025) — Non-Traditional Background

I have a degree in English Literature. I work at ServiceNow now. Here is the unglamorous version of how that happened.

Three years ago, I was working as a retail manager making $42k a year. I'd always been interested in technology but never thought I could "break into tech" without a CS degree. Then I discovered bootcamps, spent six months learning to code, and somehow landed an interview at ServiceNow.

Here's my complete journey.

Quick Stats

• Role: Software Engineer, Workflow Automation Platform
• Location: San Diego, CA (hybrid — 2 days in office)
• Year: 2025
• Timeline: ~6 weeks from application to offer
• Rounds: Online assessment → Technical screen → Virtual onsite (4 interviews)
• Difficulty: Medium — practical coding over algorithms
• Outcome: Offer accepted
• Compensation: $145k base / $175k–$190k total comp

I had 2 years of experience after completing a coding bootcamp. I applied through ServiceNow's careers portal — no referral, no network, just a cold application.

Stage 1: Online Assessment

After applying, I got a HackerRank link within a week. 90 minutes, 3 problems. The mix was actually very reasonable for someone like me who didn't spend years grinding LeetCode.

Problem 1: Implement a function to validate email addresses using regex.

This was straightforward. I used Python's re module to validate against common email patterns. The interviewer later asked about edge cases — subdomains, special characters, international domains. I was honest that my regex wasn't perfect for all edge cases but covered the common cases.

Problem 2: Given a list of tasks with dependencies, determine a valid execution order.

This was a topological sort problem. I'd studied this in my bootcamp but was nervous implementing it from scratch. I used Kahn's algorithm — count incoming edges, process nodes with zero incoming edges, decrement counts as I go. It worked, and I got it right on the second try (first attempt had a bug with detecting cycles).

Problem 3: Design a simple REST API for a ticket management system.

This was more of a design question than coding. I outlined endpoints for creating, reading, updating, and deleting tickets. I also discussed authentication, error handling, and pagination. They wanted to see if I understood REST principles, not just if I could write code.

I passed the assessment, which honestly surprised me. I'd been practicing on HackerRank for months, but I still felt like an imposter compared to candidates with CS degrees.

Stage 2: Technical Screen

This was a 60-minute coding interview on CoderPad. The interviewer was a senior engineer who, I later learned, also didn't have a traditional CS background.

Problem: Implement a rate limiter for an API.

I'd actually implemented something similar in a bootcamp project, so I felt more confident. I used a sliding window approach with a dictionary to track request timestamps per user ID.

The interviewer asked: "What if we have millions of users? Will this scale?"

I admitted I wasn't sure. We discussed using Redis for distributed state, which I'd heard of but never used. He explained how it works and asked me to modify my design to use Redis. I did my best, even though I was making some of it up as I went.

He seemed to appreciate that I was honest about what I didn't know and willing to learn on the spot. This was a turning point for me — I realized ServiceNow might actually value potential over pedigree.

Stage 3: Virtual Onsite (4 Interviews)

The onsite was virtual over Google Meet. Four interviews over two days.

Round 1: Coding — Practical Focus

Problem: Build a simple workflow executor that can run tasks in sequence.

The interviewer gave me a JSON structure representing a workflow with tasks and dependencies. I needed to:

1. Parse the JSON
2. Validate the workflow (no circular dependencies)
3. Execute tasks in the correct order
4. Handle failures gracefully

I used Python for this. I implemented a topological sort for task ordering and added error handling for task failures. The interviewer asked about logging — how to track which tasks succeeded, which failed, and why.

This felt like real work, not a contrived algorithm problem. I actually enjoyed it.

Round 2: System Design

Prompt: Design a notification system that can send emails, SMS, and push notifications.

I broke this down:

• Components: Notification service, message queue, delivery services (email gateway, SMS provider, push service)
• Scalability: Queue for async processing, workers to handle delivery
• Reliability: Retry logic, dead letter queue for failed messages
• Prioritization: High-priority notifications go to the front of the queue

The interviewer asked: "How do you handle rate limits from external providers?" I discussed implementing exponential backoff and queuing strategies. He pushed on monitoring — how to track delivery rates, failures, and latency.

I didn't know all the answers, but I asked good questions and showed I could think through the problem systematically.

Round 3: Behavioral

This was with the hiring manager. Questions were about my journey and how I handle challenges:

• "Tell me about a time you had to learn something completely new."
• "How do you approach debugging when you're stuck?"
• "What's been your biggest challenge transitioning from a non-technical background?"

For the learning question, I talked about learning JavaScript after my bootcamp. I explained how I built small projects, read documentation, and asked for help in online communities. The manager seemed to appreciate that I was self-directed and resourceful.

For the background challenge, I was honest. I said I sometimes feel insecure about not having a CS degree, especially when colleagues discuss advanced topics I don't understand. But I've learned to ask questions without shame and to recognize that my different background gives me a unique perspective.

The manager nodded and said ServiceNow values diverse backgrounds. That meant a lot to hear.

Round 4: Culture Fit

This was with a director. The conversation was more casual — about my interests, what motivates me, what kind of environment I thrive in.

I mentioned that I like collaborative environments where people help each other learn. I said I'm not interested in cutthroat competition or ego-driven engineering cultures. He smiled and said that's exactly the kind of culture they try to foster.

One Thing That Stood Out

ServiceNow didn't ask about my college GPA or my degree. They didn't ask about my lack of CS fundamentals. They focused entirely on what I could do and how I thought about problems. This was different from other companies I'd interviewed at, where I felt judged for my non-traditional background.

Compensation

Offer: $145,000 base salary plus a 15% annual bonus target and RSUs worth approximately $15k–$30k annually (vesting over 4 years). Total first-year comp is around $175k–$190k depending on stock performance.

For San Diego, this is life-changing money for me. Three years ago, I was making $42k. Now I'm making over four times that. The cost of living in San Diego is high, but it's manageable compared to the Bay Area.

What Makes ServiceNow Different

ServiceNow builds workflow automation software for enterprises. It's not flashy consumer tech, but it's meaningful work — their software helps companies run more efficiently. I like that I'm building something that has real business impact.

The engineering culture is pragmatic. They care more about building working software than about algorithmic perfection. This is great for someone like me who's still developing deep technical skills.

Advice for Non-Traditional Candidates

• Don't let imposter syndrome stop you: You don't need a CS degree to be a great engineer.
• Focus on practical skills: Build things. Deploy them. Show that you can ship working software.
• Be honest about what you don't know: Companies that are worth working for will appreciate your honesty and willingness to learn.
• Find the right companies: Some companies are gatekeepers. Others, like ServiceNow, value potential and diverse backgrounds.

I've been at ServiceNow for six months now. I'm still learning every day, but I'm no longer the person who felt like an imposter in every interview. If you're on a similar journey, keep going. It's possible.

Feel free to ask questions in the comments!