I started my career as an A>I (Ab Initio) developer. Worked on it for 3.5 years before moving to Apache Spark with Scala. A>I as a tool is not as common as Apache Spark, but that is mostly because the licensing cost of A>I is very high. So small or medium sized companies cannot afford it. It's the big traditional multinational companies (Banks, Telecom etc) that uses A>I. And in these companies A>I is used more than Spark. The reason A>I is preferred by these companies is because it is very reliable and performative. You don't need to fine tune jobs based on your cluster configuration (like you do in Apache Spark) to make it work. You just need to write optimised code, but that you need to do with Apache Spark as well. A>I just works and in most cases it will give as good a performance as Apache Spark. Yes, it's that good in performance. A>I support is also one of the best I have seen, which is very important for big companies. If you have any queries related to your A>I job performance or looking for support to some complex issues you are facing, the support team is very helpful. It's easy to learn if you have access to A>I tool. The connectors makes it very easy to visualise how the data will flow and transform. The A>I help file (documentation) is one of the best I have ever seen. That help file is the bible for learning anything you need to know about A>I. Having said all that, the reason I moved from A>I to Apache Spark was because I was interested more in writing code than using a GUI. My educational background is not in coding, and I was interested to get into it. It's not Also like the other comment said, A>I is only used by big companies. So I wanted to learn something new which can open doors to more companies as well. Answer from Low_Cauliflower_3308 on reddit.com
Abinitio
abinitio.com › en › bi-analytics-data-engineering › low-code-development
BI, Analytics & Data Engineering | Ab Initio
This simple process enabled business experts to write, test, and debug the new rules without involving developers. In the first month, a handful of non-technical experts put a dozen new rules into production, a feat that would previously have been impossible. Ab Initio provided significant improvements in data access and performance.
Indeed
indeed.com › q-ab-initio-developer-jobs.html
Ab Initio Developer Jobs, Employment | Indeed
Infosys is seeking an Ab Initio Developer: Participate and contribute to the requirements elicitation process and create requirements documentation. Participate in creating application architecture document to provide deliverables in line with architectural requirements.
Videos
01:02:05
Abinitio Development Overview | AbInitio Online Training | AbInitio ...
50:11
AB Initio Development Tutorials for Beginners | AbInitio ...
Roles and Responsibilities of Abinitio Developer| With Course ...
Master Ab Initio: Become a Data Integration Expert with Our ...
20 Tech Jobs Boolean Search Ab Initio Developer
29:28
"AbInitio Simplified: Online Training Course for Beginners" - YouTube
Allstemconnections
allstemconnections.com › Employers › SCALE › JobDescription › Index › 959
Ab Initio Developer Role Description - SCALE Portal
An AB Initio Developer is a professional who specializes in using the AB Initio software suite for data integration, transformation, and processing. They play a crucial role in designing, developing and implementing ETL solutions to meet an organization's business intelligence and data warehousing ...
AbInitio a yes or no?
I started my career as an A>I (Ab Initio) developer. Worked on it for 3.5 years before moving to Apache Spark with Scala. A>I as a tool is not as common as Apache Spark, but that is mostly because the licensing cost of A>I is very high. So small or medium sized companies cannot afford it. It's the big traditional multinational companies (Banks, Telecom etc) that uses A>I. And in these companies A>I is used more than Spark. The reason A>I is preferred by these companies is because it is very reliable and performative. You don't need to fine tune jobs based on your cluster configuration (like you do in Apache Spark) to make it work. You just need to write optimised code, but that you need to do with Apache Spark as well. A>I just works and in most cases it will give as good a performance as Apache Spark. Yes, it's that good in performance. A>I support is also one of the best I have seen, which is very important for big companies. If you have any queries related to your A>I job performance or looking for support to some complex issues you are facing, the support team is very helpful. It's easy to learn if you have access to A>I tool. The connectors makes it very easy to visualise how the data will flow and transform. The A>I help file (documentation) is one of the best I have ever seen. That help file is the bible for learning anything you need to know about A>I. Having said all that, the reason I moved from A>I to Apache Spark was because I was interested more in writing code than using a GUI. My educational background is not in coding, and I was interested to get into it. It's not Also like the other comment said, A>I is only used by big companies. So I wanted to learn something new which can open doors to more companies as well. More on reddit.com
12
10
July 29, 2023A lament for Ab Initio
It's becoming Ab Finitio now in India More on reddit.com
25
21
December 17, 2023Ab Initio Field Consultant vs Software Developer
I used to work at Ab Initio a few years ago. To answer a few of your questions: Field consultants do travel for work, I think it can vary a lot based on the customers/projects that you get put on, but it's usually about half the time. Another big difference is that field consultants can work remotely when they're not at a customer, whereas (at least when I was there) all of the dev roles were in person. Field consultants also have more pressure around deadlines/project completion, so you'll have more late nights or long weeks than you would as a dev. Imo you should choose which one you interview for based on your career goals. If you are someone who wants to have a career as a software engineer, then you should go down the dev route. If you are interested in moving into a more business-y or customer-facing role in tech (for example, product/project management, implementations, sales/account management, or even starting a company) then I would go for the consultant role. It gets you a lot of customer exposure. Consultants work mostly in ab initio's proprietary language, which is a hurdle for finding your next job if you want to go back to being a software engineer. How much of a hurdle depends on how long you stay there -- if you work in ab initio for 10+ years then it's going to be a more difficult transition than if you stay 2-3 years. Fwiw I knew a handful of field consultants who left to go do more traditional dev things after a few years. More on reddit.com
3
7
September 8, 2021Advice needed on Ab Initio
Ab initio would probably die a slow death in few years. The first most reason why a lot of companies didn’t adopt it even in non cloud era was the licensing cost and second they keep all documentation proprietary. That said, it’s the best ETL tool a developer can have and it’s MPP architecture can easily handle petabytes of data. I would still learn the tool in your case as there’s no harm in learning new things especially when your organization uses it.
More on reddit.com 5
2
July 7, 2019Reddit
reddit.com › r/dataengineering › abinitio a yes or no?
r/dataengineering on Reddit: AbInitio a yes or no?
July 29, 2023 -
At a recent meetup I saw guys punting AbInitio for all ETL and WH processes. Is this the way to go? I know it's got some nuances to the language, but it's got some simple looking connectors and components. Is it worth it? Connections I deal with are the normal SQL, XLS, Kafka, etc. I'm proficient in Python and SQL. Will it be tough to learn? And is it worth the effort?
Top answer 1 of 5
29
No. Barely anyone uses it, it is expensive, and it won’t do anything for your career except for a few companies.
2 of 5
14
I started my career as an A>I (Ab Initio) developer. Worked on it for 3.5 years before moving to Apache Spark with Scala. A>I as a tool is not as common as Apache Spark, but that is mostly because the licensing cost of A>I is very high. So small or medium sized companies cannot afford it. It's the big traditional multinational companies (Banks, Telecom etc) that uses A>I. And in these companies A>I is used more than Spark. The reason A>I is preferred by these companies is because it is very reliable and performative. You don't need to fine tune jobs based on your cluster configuration (like you do in Apache Spark) to make it work. You just need to write optimised code, but that you need to do with Apache Spark as well. A>I just works and in most cases it will give as good a performance as Apache Spark. Yes, it's that good in performance. A>I support is also one of the best I have seen, which is very important for big companies. If you have any queries related to your A>I job performance or looking for support to some complex issues you are facing, the support team is very helpful. It's easy to learn if you have access to A>I tool. The connectors makes it very easy to visualise how the data will flow and transform. The A>I help file (documentation) is one of the best I have ever seen. That help file is the bible for learning anything you need to know about A>I. Having said all that, the reason I moved from A>I to Apache Spark was because I was interested more in writing code than using a GUI. My educational background is not in coding, and I was interested to get into it. It's not Also like the other comment said, A>I is only used by big companies. So I wanted to learn something new which can open doors to more companies as well.
Snaphunt
snaphunt.com › resources › job-descriptions › ab-initio-developer-job-description-template
Ab Initio Developer Job Description Template | Snaphunt
August 6, 2025 - In the Ab Initio ETL environment, an Ab Initio developer is responsible for working on designing, constructing, and testing applications for data management and business intelligence.
LinkedIn
linkedin.com › jobs › ab-initio-developer-jobs
6,000+ Ab Initio Developer jobs in United States (87 new)
Today’s top 6,000+ Ab Initio Developer jobs in United States. Leverage your professional network, and get hired. New Ab Initio Developer jobs added daily.
AllRemote
allremote.jobs › job-description › ab-initio-developer
Ab Initio Developer Job Description | AllRemote
Ab Initio Developer is responsible for giving team status on a variety of projects.
VelvetJobs
velvetjobs.com › job descriptions › ab initio developer
Ab Initio Developer Job Description | Velvet Jobs
August 20, 2024 - Minimum 3 years of experience in design and delivery of ETL process development using Abinitio, Unix shell script · Experience in technologies such as Java, J2EEE, CTL-M, XML, PERL, Messaging, Informatica is a plus ... Our company is growing rapidly and is looking to fill the role of ab initio developer.
ZipRecruiter
ziprecruiter.com › all jobs › ab initio etl developer jobs › what does an ab initio etl developer do
Q: What Does an Ab Initio ETL Developer Do?
The job duties of an Ab Initio ETL developer revolve around working to design, build, and test applications for data management and business intelligence in the Ab Initio ETL environment.
Quora
quora.com › I-am-an-Ab-Initio-developer-with-2-years-of-experience-Will-I-be-having-a-job-10-years-hence-if-I-continue-in-Ab-Initio
I am an Ab Initio developer with 2 years of experience. Will I be having a job 10 years hence if I continue in Ab Initio? - Quora
Answer: Hey.. Thanks for the A2A. Well, 10 yrs for any technology for that matter is a long time. ETL tools like Ab Initio are seeing a changing trend to more versatile technologies like Big Data. That being said, Ab Initio definitely will be there for quite some years from now reason being that ...
Dice.com
dice.com › jobs › q-ab+initio+developer-jobs
ab initio developer jobs | Dice.com
Key Responsibilities Design & maintain scalable ETL pipelines using AbInitio Lead & support large-scale data migration projects Optimize ETL workflows and SQL queries for performance Collaborate with teams to integrate data across multiple platforms Leverage AWS & Databricks for cloud-based ...
Indeed
indeed.com › q-ab-initio-etl-developer-jobs.html
Ab Initio ETL Developer Jobs, Employment | Indeed
Salary Search: Ab Initio Operations Manager salaries in Remote ... Responsible for developing and maintaining ETL processes to extract data from various sources, transform it based on business requirements, and load it into…
LinkedIn
linkedin.com › jobs › ab-initio-developer-jobs-chicago-il
262 Ab Initio Developer jobs in Chicago, IL
Today's top 262 Ab Initio Developer jobs in Chicago, IL. Leverage your professional network, and get hired. New Ab Initio Developer jobs added daily.
ZipRecruiter
ziprecruiter.com › all jobs › ab initio developer jobs
$53-$79/hr Ab Initio Developer Jobs (NOW HIRING) Sep 2025
These developers often collaborate ... Initio Developer is an ETL (Extract, Transform, Load) specialist who designs, develops, and optimizes data processing applications using the Ab Initio software suite....
Glassdoor
glassdoor.com › Job › us-ab-initio-developer-jobs-SRCH_IL.0,2_IN1_KO3,22.htm
34 ab initio developer Jobs in United States, September 2025 | Glassdoor
Experience with Ab Initio EME (Enterprise Meta>Data Environment) and Control Center. Basic understanding of developing web services using Ab Initio Continuous Flows.
ZipRecruiter
ziprecruiter.com › all jobs › ab initio etl developer jobs › what is an ab initio etl developer and how to become one
Ab Initio ETL Developer: What Is It? and How to Become One?
The job duties of an Ab Initio ETL developer revolve around working to design, build, and test applications for data management and business intelligence in the Ab Initio ETL environment.
Naukri
naukri.com › abinitio-developer-jobs
Abinitio Developer Jobs
We cannot provide a description for this page right now