# 1.4 YOE at a service-based company with almost no project work  how should I present my experience when applying for SDE roles? — retained record

> Retained reddit record from reddit:developersIndia.

Canonical: https://highsignal.app/data/records/384a8d141537f01e

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:developersIndia)  published 2026-09-29 17:10 ingested 2026-09-30 02:38

[original source ↗](https://www.reddit.com/r/developersIndia/comments/1wtfwnb/14_yoe_at_a_servicebased_company_with_almost_no/)

## retained text



```
Hey everyone,

Need some candid advice regarding my resume and interview prep.

**Current Situation:**

* **YoE:** \~1.4 years at Cognizant (CTS).
* **Ground Reality:** On paper, I am tagged to a client project, but purely for billing purposes. The official role is support-oriented, and practically there is zero development work.
* **What I'm doing instead:** Grinding DSA for Product-Based Companies (PBCs), Fintech and other tech companies , building full-stack/backend projects on the side so my dev skills don't rust.

**The Problem:** I've been applying to companies but facing direct rejections, and the biggest blocker is my **Work Experience** section.

1. **The "Fake It" Dilemma:** A lot of seniors and peers advised me to mask my support role by writing my self-built projects as actual client project work under CTS. But I'm stuck on how to realistically frame this. If I map a personal project directly into enterprise experience, it still looks like an isolated feature build rather than enterprise software engineering.
2. **Missing Impact Metrics:** Since I didn't actually deploy or monitor these at enterprise scale, I have no metrics like "reduced latency by X%", "handled Y QPS", or "saved Z cloud costs". Without these, the bullet points look weak on ATS and to recruiters.
3. **Fear of Getting Caught:** How do I defend this in technical rounds? If an interviewer starts grilling on production issues—like CI/CD pipelines, prod bug triages, deployment cycles, team sprint dynamics, or legacy codebase integration—I worry my cover will be blown immediately.



**Questions for the community:**

1. How should I translate my self-built projects into believable enterprise bullet points without overstepping into things I can't defend?
2. What are realistic engineering metrics someone with \~1.4 YoE can actually put on a resume if there's no live user data?
3. In interviews, how do you handle deep-dives into team/production processes when your actual day job was just being on billing?
4. Are there specific resume improvements or structural changes that help early-career devs bridge this gap between support and dev roles?

https://preview.redd.it/o2wthlhjrhsh1.png?width=740&format=png&auto=webp&s=7af021393f95d13dc9185657af7290b3982d858c


```



document fetched 2026-09-30 00:25 · canonical https://reddit.com/r/developersIndia/comments/1wtfwnb/14_yoe_at_a_servicebased_company_with_almost_no
