Related Posts
Ericsson IT Solutions & Services Hi folks I have been selected in below companies. Working as a Java backend developer in TCS with 3.5 years of experience. To day is my last working day. Please suggest me in choosing company
Accenture Bangalore
ADP(Automatic Data Processing) Hyderabad Ericsson IT Solutions & Services Bangalore Virtusa (Standard Chartered Bank client project)
ACS Solutions hyderabad
Please help to find the right one in terms of project, learnings and wlb?
1.Tech Mahindra - Microsoft client (onsite) - database/ETL
2.Infosys - they can put in any data project- database /ETL
3. Accolite Digital - Morgan Stanley (onsite) - database developer
Morgan Stanley Microsoft Infosys
Hi Fishes
I would like to know about the client interviews (especially in data science or machine learning roles).
Are these interviews tough?
Are these interviews meant to assess technical knowledge? For example, what is binomial distribution, what are different data structures in python, ml algorithms etc.
I would request each of the nagarrians to share their thoughts irrespective of the technologies you are working.
I am thankful to you for taking time and helping me out.
Nagarro
More Posts
Ahhhh law school
Hello fishes, need help in finding a suitable job change for one of my relative. She is an Associate at Cognizant with 7.5 years of experience. Her experience domain is in functional testing and manual testing. Her preferred job location is Kolkata.
Any leads would be very much helpful. TIA
Tata Consultancy Infosys IBM Accenture EY Wipro
Additional Posts in Robotic Process Automation (RPA)
You two should talk
Worst consulting company to work for ?
New to Fishbowl?
unlock all discussions on Fishbowl.
APIs are a much better approach to obtaining data, compared to UI.
Limitation is availability, both in them existing and IT being willing to provide access.
For Operations groups looking to circumvent their IT counterparts, asking for API access can be a hard no.
Short answer, in most cases leveraging the API is the best strategy.
Thank you both for your answers. However, i wonder what kind of challenges companies could have to set up APIs:
1) effort to set up couple of web-services should't take more than half-day/1 day per web-service. It amount to maybe a week or 2 if a lot of services are needed.
2) you can limit the type of actions of your services to "GET" if allowing "POST" actions is too risky. Knowing that people who would be given access to these web services already have access to the actual data through the app, what kind of additional risk are we talking about?
@M1
When you said that leveraging the API is usually the best strategy, did you mean combining API and RPA? Or simply use RPA if API isn't possible?
My group combines RPA with APIs. A typical process includes: pull data via the API, carryout necessary data manipulation or processing and then upload into another system via API.
Simple example, but using APIs is proving much more stable from a support perspective.
Why would you use RPA in that instance and not simply an ETL tool? I 100% agree that APIs should be leveraged where possible but the criteria for applying RPA should generally include some constraint (technical or organizational) where executing the multi-step process requires interacting with UI.
Performance and robustness as it can the UI dependency. Have you used/suggested APIs in a RPA project before? What are thoughts about this matter?
APIs are great if/ when they exist. Also for an api to work there has to be cross compatibility and that’s where things get murky even the hundreds of different application clients use and not to mention in-house apps