resume question

[enigmatic]

meeru resume raasinappudu bullet point lo 

did x to save 50% cost 
built something that improved efficiency by 90% 
reduced build time by 60%  ...

ee type lo raasatara prati project ki? how do you come up with these numbers? do you make them up? or is there a method to that?

 also interview chesetappudu how do you justify that? 

TIA

[Vaaaampire]

Resume helping services untayi konni. Vallu rayamantaru ila saved millions bongu ani. Nenu aithey rayanu. Correct interviewer thagilithey aadukuntaru aa okka point meedha.

Reduced build time by x%, efficiency, latency rasukovachu. Product meedha full knowledge untey raasukovachu.  Latency reduction ni konni api calls prefetch lo add chesa ani cheppochu. Ledha materialization chesam ani. 
 

build time by X% anedhi tricky. Every company has its own build system. So u may issues communicating what u did

[Jatka Bandi]

30 minutes ago, enigmatic said:

meeru resume raasinappudu bullet point lo 

did x to save 50% cost 
built something that improved efficiency by 90% 
reduced build time by 60%  ...

ee type lo raasatara prati project ki? how do you come up with these numbers? do you make them up? or is there a method to that?

 also interview chesetappudu how do you justify that? 

TIA

Not made up. You will know those numbers when you truly worked on them. Most fake these numbers though. For example, nenu kotha product testunte, previous generation product performance entha vundo telusu. Kothadi entha vundo telusu. Based on those koncham guardband ichi percentages calculate chesta. Software engineer ki avute, code rasaaka, execution time before and after calculate chesukuni percentage raasukovachu. No one will blindly do some work. They have a target in mind and they assess how they performed against that target. Deliver chesina daanini quote chestaru. Confidentiality and proprietary are the reasons people don't quote absolute numbers. Legal cases kooda padochu. So, relative percentages are the way to go. 

 

Interview lo kooda adigaadu ante, interviewer gaadu chethakaanodu ani. You vaguely talk about them. They should never ask you the absolute numbers used in the calculation. Just say that you cannot divulge but it is their lack of skill, not yours. They may ask you how did you achieve those improvements to assess whether your skill is innovation or continuous improvement related. Be prepared to answer such questions. How did you achieve it ane daaniki gurinchi matladu, have 2,3,4 examples ready, not just one. Remember all these improvements need not be technical skill alone. It can also be collaborative or people skills as well. Have well rounded examples.

[Jatka Bandi]

5 minutes ago, Vaaaampire said:

Resume helping services untayi konni. Vallu rayamantaru ila saved millions bongu ani. Nenu aithey rayanu. Correct interviewer thagilithey aadukuntaru aa okka point meedha.

 

Fake cheyakunda nijanga achieve chesindi raaste, ee interviewer emi peekaledu.

[Jatka Bandi]

6 minutes ago, Vaaaampire said:

build time by X% anedhi tricky. Every company has its own build system. So u may issues communicating what u did

Writing a resume is also a skill. Ilanti cases lo relative improvement advertise chesukovaali. That should help us to support our work.

[Vaaaampire]

20 minutes ago, Jatka Bandi said:

Fake cheyakunda nijanga achieve chesindi raaste, ee interviewer emi peekaledu.

Agreed. But sometimes its tough to convince interviewers even if u really did. Nee mundu vallu enduku cheyyaledhu lanti tingari questions chaala vinna. Recent interviews exp tho chepthunna. Sinki gallu interview chesaru antey sukkaley. Narrow minded

[zamoora_rules]

24 minutes ago, Vaaaampire said:

Recent

My 2 cents.. Most of us lack that skill on justifying the savings on the projects in the interviews. Besides, it would be foolish to assume that a single person is responsible for it instead of generalizing.Even though many Interviewers look for numbers in the resumes ..but we should somehow learn to divert or downplay it and not make it the focus of the interview discussion.

[Vaaaampire]

15 minutes ago, zamoora_rules said:

My 2 cents.. Most of us lack that skill on justifying the savings on the projects in the interviews. Besides, it would be foolish to assume that a single person is responsible for it instead of generalizing.Even though many Interviewers look for numbers in the resumes ..but we should somehow learn to divert or downplay it and not make it the focus of the interview discussion.

Mgr/director roles ki divert cheyyadam impossibile bro.

[zamoora_rules]

5 minutes ago, Vaaaampire said:

Mgr/director roles ki divert cheyyadam impossibile bro.

True. When we relate/project savings towards resource reduction; many mid-west folks don't like it at all. 

[Spartan]

ilanti cases lo I use word "optimization" not actual numbers.

• optimize deployment/maintenance times
• drive cost-efficiency, etc...

@Vaaaampire

[Konebhar6]

2 hours ago, enigmatic said:

meeru resume raasinappudu bullet point lo 

did x to save 50% cost 
built something that improved efficiency by 90% 
reduced build time by 60%  ...

ee type lo raasatara prati project ki? how do you come up with these numbers? do you make them up? or is there a method to that?

 also interview chesetappudu how do you justify that? 

TIA

Def helps but always prepared to be asked these questions. You need to justify how you achieved each metric with a clear explanation. Be prepared for those questions

[Konebhar6]

did x to save 50% cost 
 - Automated some processes. There used to be around 100+ tickets /week in this space. We analyzed the most occurances of the issues and did RCA on each, collaborated with all stake holders, put together a solution that now reduced these tickets to 5-10/week. We were able to reduce our L2 team from 3 to 1. Saves $30/hr for each offshore resource. 

built something that improved efficiency by 90% 
 - Year end Pricing processes used to take 36 hours for the prices to be sent form ERP to downstream systems. We changed the design in the process and used bulk processing capability within the tool and reduced the processing time from 36 hours to 6 hours. 

reduced build time by 60%  

 - (for reduction in Development time) We have come up with a robust, reusable architecture where we dont need to build things from scratch. A lot of components are already available. For e.g. Error Handling Framework, Integration with Service Now for automatic Incident creation, Alert notifications, etc. 

 - (build time) I am not an expert on it, but you can say things like - removed unwanted dependencies and make build process less complex. 

[Vaaaampire]

18 minutes ago, Spartan said:

ilanti cases lo I use word "optimization" not actual numbers.

• optimize deployment/maintenance times
• drive cost-efficiency, etc...

@Vaaaampire

Yupe. We can go with x% but never actual nos

[Shameless]

17 minutes ago, enigmatic said:

meeru resume raasinappudu bullet point lo 

did x to save 50% cost 
built something that improved efficiency by 90% 
reduced build time by 60%  ...

ee type lo raasatara prati project ki? how do you come up with these numbers? do you make them up? or is there a method to that?

 also interview chesetappudu how do you justify that? 

TIA

 

7 minutes ago, Vaaaampire said:

Resume helping services untayi konni. Vallu rayamantaru ila saved millions bongu ani. Nenu aithey rayanu. Correct interviewer thagilithey aadukuntaru aa okka point meedha.

Reduced build time by x%, efficiency, latency rasukovachu. Product meedha full knowledge untey raasukovachu.  Latency reduction ni konni api calls prefetch lo add chesa ani cheppochu. Ledha materialization chesam ani. 
 

build time by X% anedhi tricky. Every company has its own build system. So u may issues communicating what u did

IT lo etluntadho naku thelvadhu but naadhi genuine experience and key accomplishments including cost savings, etc kuda genuine bro

[Rojaa]

6 hours ago, Vaaaampire said:

Resume helping services untayi konni. Vallu rayamantaru ila saved millions bongu ani. Nenu aithey rayanu. Correct interviewer thagilithey aadukuntaru aa okka point meedha.

Reduced build time by x%, efficiency, latency rasukovachu. Product meedha full knowledge untey raasukovachu.  Latency reduction ni konni api calls prefetch lo add chesa ani cheppochu. Ledha materialization chesam ani. 
 

build time by X% anedhi tricky. Every company has its own build system. So u may issues communicating what u did

Where you working now anna?