FIX (financial information exchange) protocol is the global protocol used for Electronic trading of different asset classes e.g Equity, Fixed Income FX (foreign exchange) , Derivatives Futures and Options and its knowledge is essential to understand Electronic trading and FIX messages. I have listed some of the very common but informative questions asked in FIX protocol interview question, this list is by no means complete and only contains questions on top of my mind, I would encourage reader to post any question they have been asked and I will include on this list.
Please feel free to ask any other questions related to FIX (financial information exchange) protocol I would be happy to answer those. FIX messaging is a term used to describe communication using FIX protocol.
If you are a Java developer looking for FIX + Java jobs then having a look at these FIX (financial information exchange) protocol interview snippets can benefit you in an interview. usually for a FIX (financial information exchange) protocol job interviewer tests whether the candidate has actually worked in FIX protocol or not and whether he is familiar with various FIX tags and different FIX protocol versions or not.
8. What is the difference between DMA orders and CARE orders?
These are general concept irrespective of FIX (financial information exchange) protocol. DMA orders are Direct to Market order means it will not touch by any trader or salesperson on broker side while CARE orders also called as Broker Intervention (BI) orders will be touched by Trader or salesperson on broker side.
So if a Trader has any view on Market he can take advantage of that while working with BI order.
9. What is the difference between Application level Reject (MsgType=8 and ExecType=8) and Session level reject (MsgType=3)?
FixEngine will reject any message which doesn't confirm FIX protocol i.e. some mandatory tags missing e.g. MsgType with Session level reject , the application will not get that message for processing , while application e.g. OMS or Execution System will reject message based on Business logic or FIX (financial information exchange) Protocol trade life cycle with application level Reject (MsgType=8 and ExecType=8).
10. What is FIX Messaging?
FIX messaging is a term used to describe communication using FIX protocol. So if two FIX engines are communicating with each other using financial information exchange protocol we call it as they are communicating using FIX messaging.
To read or learn more about FIX (financial information exchange) protocol please sees my FIX protocol tutorial series
Related post:
Top 20 FIX Protocol Interview Questions
Financial Information Exchange (FIX) Protocol Interview Questions Answers
Interview question asked on FINANCIAL INFORMATION EXCHANGE (FIX) Protocol
FIX Protocol Tutorial for beginners
FIX Protocol Session or Admin messages tutorial
Fix Session is not connecting how to diagnose it?
Since FIX (financial information exchange) versions differ significantly from one version to another knowledge of FIX tags and their value for a particular version is very important. There are lots of jobs available for Core Java and FIX (financial information exchange) protocol developers even if you had worked in FIX for 1 year you could be very much sought after in the job market.
1. What is the difference between ClOrdID and OrderID?
In FIX (financial information exchange) protocol ClOrdId is a unique id assigned by buy-side while the later is assigned by sell-side. OrderID normally remains same for a message chain (e.g. on Cancel and mod orders) while ClOrdID changes with Cancel and Modification.
2. What is the difference between TransactTime and Sending Time? (answer)
TransactTime: Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as 'GMT')
SendingTime: Time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as 'GMT')
3. What is TradeBust and Trade Cancel?
Sometimes exchange wants to cancel a trade , if the exchange is using FIX protocol then it sends an execution report (MsgType=8) and ExecType=H(Cancel) , this is called TradeBust , after this earlier trade will not go for settlement and deemed as cancelled. In other times exchange (or execution party) wants to correct either TradePrice or Trade Quantity in that case they send execution report (MsgType=8) and ExecType=G (Correct), this is called Trade Correct.
As per FIX (financial information exchange) protocol
A Cancel on an execution (trade bust, ExecType (150) = Trade Cancel) happening the same day of the trade will result in CumQty (14) and DayCumQty (425) each decreasing by the quantity busted, and LeavesQty (151) increasing by the quantity busted. OrderQty (38) and DayOrderQty (424) will remain unchanged.
FIX Protocol Interview Questions with Answers
1. What is the difference between ClOrdID and OrderID?
In FIX (financial information exchange) protocol ClOrdId is a unique id assigned by buy-side while the later is assigned by sell-side. OrderID normally remains same for a message chain (e.g. on Cancel and mod orders) while ClOrdID changes with Cancel and Modification.
2. What is the difference between TransactTime and Sending Time? (answer)
TransactTime: Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as 'GMT')
SendingTime: Time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as 'GMT')
3. What is TradeBust and Trade Cancel?
Sometimes exchange wants to cancel a trade , if the exchange is using FIX protocol then it sends an execution report (MsgType=8) and ExecType=H(Cancel) , this is called TradeBust , after this earlier trade will not go for settlement and deemed as cancelled. In other times exchange (or execution party) wants to correct either TradePrice or Trade Quantity in that case they send execution report (MsgType=8) and ExecType=G (Correct), this is called Trade Correct.
As per FIX (financial information exchange) protocol
A Cancel on an execution (trade bust, ExecType (150) = Trade Cancel) happening the same day of the trade will result in CumQty (14) and DayCumQty (425) each decreasing by the quantity busted, and LeavesQty (151) increasing by the quantity busted. OrderQty (38) and DayOrderQty (424) will remain unchanged.
If the business rules allow for a trade bust to be reported on a later date than the trade being busted, the OrderQty (38) and DayCumQty (425) will remain unchanged, the LeavesQty (151) and DayOrderQty (424) will increase by the quantity busted, and the CumQty (14) will decrease by the quantity busted.
4. What do you mean by Funari OrderType?
Funari is a special order type normally used in a Japanese and Korean exchange where the unexecuted quantity of a limit order turned as Market order during Market close, it is denoted as OrdType=I in FIX (financial information exchange) protocol.
5. What are the differences between FIX 4.0 and FIX 4.2? (answer)
In FIX 4.0 we had a tag called ExecTranType which describes Execution type in FIX 4.2 this tag is merged with ExecType (tag 150) and now OrdStatus will show the status of order instead of Execution type. Later versions of FIX (financial information exchange) protocol is now 5.0 or even higher.
6. What do you mean by Sashinari & Hikenari order types?
These are again special order types available in Japanese exchanges added on FIX (financial information exchange) protocol later.
Sashinari (Limit market order) = First, this is treated as a limit order. However, if all or part of the order is still unexecuted, then the remaining quantity is changed to a market order at "day's" closing (O-hike).
Hikenari (Market order on close) = this order type can be placed either for the closing of the morning session or closing of the afternoon session. However, if an order is placed for the closing of the morning session and there are still unexecuted quantities, then the remaining quantity (not expired at morning close) is treated as a market order for "the opening of afternoon session".
If an order is placed during the afternoon session, it is treated as a market order on afternoon close
Sashinari and Hikenari are available in the TOCOM exchange.
7. What are header tags in FIX (financial information exchange) Protocol?
Header tags are certain special tags in FIX protocol that comes at the beginning of a FIX Message.
Only the first few fields of the header must be in sequence, see FIX (financial information exchange) Spec Volume 1. "The first three fields in the standard header are BeginString (tag #8) followed by BodyLength (tag #9) followed by MsgType (tag #35)."
Also "General message format is composed of the standard header followed by the body followed by the standard trailer."
Fields of the header thus must not appear in the body, if they then the FIX engine will not be able to parse and understand the message and will complain about it.
4. What do you mean by Funari OrderType?
Funari is a special order type normally used in a Japanese and Korean exchange where the unexecuted quantity of a limit order turned as Market order during Market close, it is denoted as OrdType=I in FIX (financial information exchange) protocol.
5. What are the differences between FIX 4.0 and FIX 4.2? (answer)
In FIX 4.0 we had a tag called ExecTranType which describes Execution type in FIX 4.2 this tag is merged with ExecType (tag 150) and now OrdStatus will show the status of order instead of Execution type. Later versions of FIX (financial information exchange) protocol is now 5.0 or even higher.
6. What do you mean by Sashinari & Hikenari order types?
These are again special order types available in Japanese exchanges added on FIX (financial information exchange) protocol later.
Sashinari (Limit market order) = First, this is treated as a limit order. However, if all or part of the order is still unexecuted, then the remaining quantity is changed to a market order at "day's" closing (O-hike).
Hikenari (Market order on close) = this order type can be placed either for the closing of the morning session or closing of the afternoon session. However, if an order is placed for the closing of the morning session and there are still unexecuted quantities, then the remaining quantity (not expired at morning close) is treated as a market order for "the opening of afternoon session".
If an order is placed during the afternoon session, it is treated as a market order on afternoon close
Sashinari and Hikenari are available in the TOCOM exchange.
7. What are header tags in FIX (financial information exchange) Protocol?
Header tags are certain special tags in FIX protocol that comes at the beginning of a FIX Message.
Only the first few fields of the header must be in sequence, see FIX (financial information exchange) Spec Volume 1. "The first three fields in the standard header are BeginString (tag #8) followed by BodyLength (tag #9) followed by MsgType (tag #35)."
Also "General message format is composed of the standard header followed by the body followed by the standard trailer."
Fields of the header thus must not appear in the body, if they then the FIX engine will not be able to parse and understand the message and will complain about it.
8. What is the difference between DMA orders and CARE orders?
These are general concept irrespective of FIX (financial information exchange) protocol. DMA orders are Direct to Market order means it will not touch by any trader or salesperson on broker side while CARE orders also called as Broker Intervention (BI) orders will be touched by Trader or salesperson on broker side.
So if a Trader has any view on Market he can take advantage of that while working with BI order.
9. What is the difference between Application level Reject (MsgType=8 and ExecType=8) and Session level reject (MsgType=3)?
FixEngine will reject any message which doesn't confirm FIX protocol i.e. some mandatory tags missing e.g. MsgType with Session level reject , the application will not get that message for processing , while application e.g. OMS or Execution System will reject message based on Business logic or FIX (financial information exchange) Protocol trade life cycle with application level Reject (MsgType=8 and ExecType=8).
10. What is FIX Messaging?
FIX messaging is a term used to describe communication using FIX protocol. So if two FIX engines are communicating with each other using financial information exchange protocol we call it as they are communicating using FIX messaging.
To read or learn more about FIX (financial information exchange) protocol please sees my FIX protocol tutorial series
Related post:
Top 20 FIX Protocol Interview Questions
Financial Information Exchange (FIX) Protocol Interview Questions Answers
Interview question asked on FINANCIAL INFORMATION EXCHANGE (FIX) Protocol
FIX Protocol Tutorial for beginners
FIX Protocol Session or Admin messages tutorial
Fix Session is not connecting how to diagnose it?
4 comments :
Since fix tag 20 ExecTransType has not there in FIX4.4 but it exits in FIX4.2, do you know how to port a Fix Engine from FIX4.2 to FIX4.4 , what is the equivalent of tag 20 in FIX4.4 ?
is there any fix protocol wiki exists ?
from where can I download FIX specification for FIX4.2 and FIX4.4 ?
What are the steps we need to follow to establish FIX connectivity and what are testing required for those ?
Post a Comment